Pseudonymisation
Processing personal data so it can no longer be attributed to a specific person without additional information kept separately (for example replacing names with codes). Pseudonymised data is still personal data and still fully regulated; it is not the same as anonymisation.
Defined in 3 GAGE programs, which carry 4 distinct definitions of it. The wording above is taught in Certified AI Governance Professional (CAIGP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
Processing personal data so it can no longer be attributed to a specific person without additional information kept separately (for example replacing names with codes). Pseudonymised data is still personal data and still fully regulated; it is not the same as anonymisation.
Replacing identifying details with a consistent stand-in code so a record can still be linked back to the original if genuinely needed, unlike anonymisation, which removes that link entirely; a practical middle option when drafting a prompt.
Processing so that data can no longer be attributed to a person without additional information held separately. The data remains personal data in full.
Replacing direct identifiers with a key or token that can re-identify the data. It reduces risk but does not remove data from scope; pseudonymised data is still personal data and still needs a retention clock.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Your Regulator Probably Isn't Brussels · Ethical and Responsible AI and Operational Governance, Certified AI Practitioner: Workplace Foundations
- Consent archaeology: what this data was collected for versus what you want to do · Data Reality, Certified AI Governance Professional (CAIGP)
- The retention decision: what you must keep, what you must destroy, and proving both · Data Reality, Certified AI Governance Professional (CAIGP)
- Personal data, roles, and legal bases · Privacy and Data Governance, Certified Enterprise Governance, Risk and Compliance Professional (CEGP)
Where it shows up at work
A definition is where Pseudonymisation starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Classifies information, applies least privilege, sets retention and acceptable-use rules, and controls what may enter a prompt, a log or an embedding.
3 lessons on this page teach it as a primary outcome.
Applies IMDA's Model AI Governance Framework, AI Verify and the PDPA alongside Western frameworks for organizations operating across Asia.
One lesson on this page teach it as a primary outcome.
Applies GDPR, CCPA and sector rules to training data, inference, automated decisions, lawful basis, individual rights and cross-border transfer.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- AI Privacy Engineerneeds it at depth · 6 open postings this week
- Data Governance Leadneeds it at depth · 2 open postings this week
- Chief Privacy Officer, AI privacy editionneeds it at depth
- Privacy Analystneeds working knowledge
- Chief Data Officer, data leadership editionneeds working knowledge
- Chief Information Officer, technology leadership editionneeds working knowledge
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: ISO/IEC 27001; GDPR Article 5; IMDA Model AI Governance Framework; PDPA.
One interview question about it
How do you decide who may access which data for AI work, and how long it is kept?
Asked of candidates for data classification, access and retention. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Privacy and data protection carries it as a claim to back up: Classification and retention rules are familiar territory.
- Cybersecurity and IT carries it as work you can show: Access governance and classification are implemented, not described.
- Human resources and people operations carries it as a claim to back up: Access restriction and retention for personnel data are routine.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.