DataTerminology.comNEW
Also known as: Pseudonymisation
Replacing direct identifiers with consistent placeholders, reducing identifiability while retaining linkage through separately kept additional information.
DESCRIPTION
Pseudonymization transforms personal data by replacing identifiers with pseudonyms, reducing privacy risks while preserving analytic utility. Additional information that enables re-identification is kept separately under strict controls. It is explicitly defined in the GDPR and is a key privacy-enhancing technique for analytics, testing, and model training. Unlike anonymization, it still constitutes personal data because re-identification remains possible. Effective implementations combine cryptographic methods, robust key management, and governance. Re-identification risk must be assessed considering indirect identifiers. Pseudonymization supports data sharing under controlled conditions.
ALTERNATIVE DEFINITIONS
GDPR Article 4(5)
‘pseudonymisation’ means the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person.
Legal definition emphasizing separation and technical/organizational measures.
UK ICO
Pseudonymisation is a technique that replaces or removes information in a data set that identifies an individual, so that the data can no longer be attributed to a specific person without additional information.
Practical guidance highlighting technique and dependency on separate information.
ENISA
Pseudonymisation is a process that replaces private identifiers with pseudonyms to reduce the linkability of a dataset with the original identity of a data subject.
Security-focused view emphasizing linkability reduction and best practices.
RELATED TERMS
Data De-identification Data Encryption Data Masking Differential Privacy Re-identification GDPR Data Minimization K-anonymity
COMPETING TERMS
RELATIONS
- Narrower: Data Pseudonymization
KNOWLEDGE AREAS
Data Privacy & Compliance Data Security Data Management AI Governance
TARGET AUDIENCE
Data Governance Manager Data Steward Data Engineer Data Scientist MLOps Engineer AI Engineer Chief Data Officer
EXTERNAL SOURCES
- Wikipedia - Pseudonymization
- European Union - Official GDPR definition
- UK ICO - Regulatory guidance and examples
- ENISA - Techniques and best practices
- NISTIR 8053 - De-identification background and taxonomy
TOP QUESTIONS
How does Pseudonymization differ from Anonymization?
Pseudonymized data can be linked back to individuals using separately held information, while anonymized data cannot reasonably be re-identified. Thus, pseudonymized data remains personal data under GDPR.
Category: Misunderstanding
When should Pseudonymization be used?
Use it for analytics, testing, and sharing when utility and linkage are needed but direct identifiers must be concealed. It reduces risk without destroying data relationships.
Category: Requirements
What are common Pseudonymization techniques?
Deterministic hashing with salts, keyed HMACs, tokenization, and format-preserving encryption are common. Choice depends on linkage needs, reversibility rules, and threat models.
Category: Example
What risks remain after Pseudonymization?
Re-identification via indirect identifiers or data linkage is possible. Poor key management or weak algorithms also undermine protection. Governance and controls are essential.
Category: Risks
Is Pseudonymization required by GDPR?
It is not mandatory in all cases but is encouraged as a safeguard and risk-reduction measure. It can enable lawful processing through data protection by design.
Category: Compliance
How does Pseudonymization support machine learning?
It preserves relationships and labels while masking identities, enabling training and evaluation. Combined with differential privacy, it strengthens privacy in model development.
Category: Application
What is a hot topic around Pseudonymization today?
Cryptographic tokenization services and privacy-preserving record linkage are advancing, enabling cross-organization analytics without exposing raw identifiers.
Category: Topic
What are implementation prerequisites for Pseudonymization?
Define linkage requirements, choose cryptographic approaches, establish key management, segregate additional information, and monitor re-identification risk continuously.
Category: Requirements
What’s a common mistake with Pseudonymization in practice?
Treating it as anonymization. Teams often ignore quasi-identifiers, leaving datasets vulnerable to linkage attacks. Perform proper risk assessments.
Category: Mistakes