Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Article 9 Special Category Data
Governance, Ownership & Risk

Article 9 Special Category Data

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Governance, Ownership & Risk

Article 9 Special Category Data is a legal term for personal data that needs extra protection because it reveals sensitive attributes such as health, biometrics, religion, politics or sex life. It is defined in UK and EU data protection law, and processing usually needs a specific lawful basis and tighter access control.

What this term captures in law and practice

Article 9 Special Category Data is not just “sensitive” information in a generic sense. It is a legal classification that marks certain personal data as needing an extra layer of justification and handling because the information can reveal highly sensitive attributes about a person. In practice, the term matters most when organisations decide what they may collect, why they may process it, and who should be allowed to see it.

For security teams, the key point is that special category data usually demands tighter handling than ordinary personal data. That means stronger access controls, a sharper need-to-know model, and careful separation of routine operational access from broader business use.

What usually falls inside Article 9

The scope is defined by the kind of attribute the data reveals, rather than by whether the information is stored in a special system. Common examples include health data, biometric data, religious or philosophical beliefs, political opinions, sex life, and sexual orientation. Some categories are obvious at collection time, while others emerge through inference, which is why classification often requires context rather than a simple field label.

That distinction matters because organisations can accidentally mishandle special category data when they treat it as ordinary profile data, employee data, or customer support data. A record may be special category data even when it appears only in a note, a message thread, an attachment, or an analytics output.

How Article 9 changes governance and access decisions

Article 9 changes the governance question from “Can we process this?” to “What specific condition and control set makes this processing lawful and safe?” The answer usually involves a valid Article 9 condition alongside the normal data protection requirements, plus more disciplined access control, retention, and sharing decisions. NHIMG’s Special Category Data Guide is useful here because it shows how to confirm the condition, map the data, and apply stronger controls.

It also helps to distinguish Article 9 data from other privacy-sensitive material. NHIMG’s Personal Data vs Sensitive Personal Data guide explains why the legal and security treatment changes when the data crosses into a higher-risk category. For organisations handling health records or employee files, NHIMG’s Employee Data Privacy Guide is especially relevant because HR data often mixes ordinary personal data with special category information.

Why special category data needs stronger security handling

Special category data is more damaging if exposed, misused, or over-shared because the harm is not limited to inconvenience or identity theft. Disclosure can create discrimination, reputational damage, unfair treatment, or unwanted inference about a person’s private life. That is why access should be more tightly scoped than for ordinary operational records, and why logging, encryption, and retention decisions need closer review.

Biometric and health-related data are two of the clearest examples. NHIMG’s Biometric Data in the Workplace guide shows how Article 9 duties interact with practical controls such as template protection, alternatives, and DPIAs. For sectors where health information is central, NHIMG’s GDPR vs HIPAA guide helps readers separate lawful basis questions from sector-specific compliance rules.

When consent is relied on, it must be handled carefully. Article 9 usually expects a higher standard than casual or bundled permission, so explicit consent needs to be genuine, recorded, and separated from routine service acceptance where possible. NHIMG’s Explicit vs Implied Consent guide is useful for understanding when consent is sufficient and when it is not.

How to recognise and protect special category data in day-to-day operations

The practical challenge is not just classifying obvious fields, but recognising where special category data appears indirectly. That can happen in free text, helpdesk notes, documents, screenshots, call recordings, biometric systems, or derived analytics. If a business process can surface such data, it should be treated as part of the data map, not as an exception that only legal teams understand.

For that reason, the strongest operational pattern is to combine legal classification with data handling discipline: know where the data lives, restrict who can access it, and avoid reusing it for unrelated purposes. Where the data relates to biometrics, HR, religion, health, or workplace monitoring, the controls need to be reviewed together rather than separately, because the risk comes from the combination of sensitivity, context, and broad internal access.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

GDPR and ISO/IEC 27001:2022 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
GDPRArt. 9 — Special categories of personal dataDefines special category data and the extra lawful-basis requirement.
Art. 25 — Data protection by design and by defaultRequires privacy-conscious design for processing sensitive personal data.
Art. 32 — Security of processingSupports stronger protection for sensitive personal data through appropriate security measures.
Recommendation — Map each sensitive dataset to an Article 9 condition before allowing processing. Build minimisation and access restriction into systems that handle special category data. Apply risk-based technical and organisational controls to protect special category data.
ISO/IEC 27001:2022A.5.12 — Classification of informationRequires formal information classification, which is essential for special category data handling.
Recommendation — Classify special category data so handling rules match its sensitivity.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org