Learn
Pseudonymising: what it protects, and its limits
In short
- Pseudonymising means replacing a name with a pseudonym while keeping the lookup table aside. You can go back.
- Anonymising means making any identification impossible, irreversibly. It is far more demanding.
- Pseudonymised data remains personal data: the GDPR still applies.
Pseudonymise, anonymise… it’s the same thing, right?
No. Two words that look alike, two different operations. One can be undone, the other cannot.
The difference in one drawing
Still personal data: the GDPR still applies.
No longer personal data.
The CNIL, France’s data protection authority, sums it up: unlike anonymisation, pseudonymisation can be reversed, whereas anonymisation makes identifying anyone impossible (CNIL). Definitions: GDPR, article 4. The European Data Protection Board confirms that pseudonymised data remains personal data (EDPB).
An example
Mrs Martin, born on 3 March 1971, is disputing invoice no. 2024-118.
[PERSON_1], born on [DATE_1], is disputing invoice no. [REF_1].
The table saying “[PERSON_1] = Mrs Martin” is kept elsewhere.
What it protects when you write to an AI
The name, the case number or the IBAN are not sent. If the conversation is kept, read by a person, used for training or exposed in a leak, it is the pseudonymised version that circulates.
That counts: the EDPB notes that pseudonymisation can reduce the risks for the people concerned (EDPB).
Five things it does not protect
- The rest of the message. “[PERSON_1], the town’s only notary, on sick leave since her accident in March” can still be recognised. See cross-referencing.
- The content itself. The diagnosis, the amount in dispute, the strategy are sent as they are.
- What the tool missed. A misspelt name, a nickname. You still need to reread.
- Attached files. A document attached as it is goes out as it is.
- The table. Lost or stolen, the protection falls.
There are no silly questions
- My data is pseudonymised. So the GDPR no longer applies?
- It does. The CNIL states that pseudonymised data is personal data and remains subject to the GDPR’s obligations (CNIL). Pseudonymisation helps meet some obligations, provided all the others are met (EDPB). It helps; it exempts you from nothing.
- Then why not anonymise for good?
- Because it is hard. You have to rule out the three ways of finding someone: singling them out, linking data together, inferring information about them (CNIL). Replacing names is almost never enough.
- And professional secrecy?
- If your profession requires secrecy or follows a code of conduct, the page for your profession sets out the rules that apply.
In practice: four steps, in order
- Needed? Ask whether the information serves the question.
- Remove or generalise the details that allow cross-referencing.
- Pseudonymise what remains: names, organisations, references, identifiers.
- Reread before sending.
Your turn: protected or not?
“[PERSON_1] is disputing invoice [REF_1].” The table is on my computer.
Pseudonymised. The service receives only markers. With the table, you get the original text back: so it is not anonymous.
“[PERSON_1], the town’s only notary, on sick leave since her accident in March.”
Not really. The name is replaced, but the situation still points to one person.
I pseudonymised my question, then attached the contract as it is.
No. Pseudonymising the text of the question changes nothing in the attached file: it needs the same treatment.
Key points
- A pseudonym removes the direct identifier; the rest of the message can still point to the person.
- Pseudonymisation can be reversed by whoever holds the lookup table; anonymisation cannot be reversed by anyone.
- Pseudonymised data remains personal data, subject to the GDPR.
- Pseudonymising before sending to an AI reduces the risk. It does not replace the question: is this data needed?
Sources
- CNIL, Identifier les données personnelles (27 January 2020) (in French), consulted .
- CNIL, Règlement européen sur la protection des données, chapitre 1 (article 4) (in French), consulted .
- European Data Protection Board (EDPB), EDPB adopts pseudonymisation guidelines (guidelines 01/2025, 17 January 2025), consulted .
- CNIL, Le G29 publie un avis sur les techniques d’anonymisation (25 January 2016) (in French), consulted .
This page is for information only. It is not legal advice and does not replace a professional’s view of your situation. Rules change: each source is dated with the day it was consulted.