Anonymization vs pseudonymization: what is the difference?
In the debate on anonymization vs pseudonymization, the line is clear: pseudonymization replaces the identifying elements of data with a pseudonym, so that the data can no longer be attributed to a person without additional information kept separately, while anonymization makes that attribution impossible, irreversibly. The whole difference lies in that additional information. As long as it exists, the person remains identifiable to whoever can access it, and the data remain personal data.
Take meeting minutes in which "Jane Smith" becomes PERSONNE_001. If a table states that PERSONNE_001 means Jane Smith, the document is pseudonymized: it protects Jane Smith from anyone who does not have the table, but its author can go back. If no table exists, and if nothing in the text allows the person to be recognized (a unique role, a date of birth, an anecdote), the document moves towards anonymization.
The two operations are often confused because they start with the same gesture: removing the name. Yet they have neither the same legal status nor the same uses. Pseudonymization is a security measure that keeps the data within the scope of the GDPR. Anonymization takes the data out of that scope, provided it is real.
This article sets out what the texts say, compares the two notions point by point and offers a rule for choosing for your documents. For the detailed definition of anonymization and its techniques, see the article what is anonymization; to know which information to deal with, the article personal data: definition and examples.
What the GDPR and the EDPB say
Article 4(5) of the GDPR defines pseudonymisation as "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" designed to prevent that attribution.
The regulation does not define anonymization in an article, but recital 26 sets out its scope in two sentences. Pseudonymized data, which could be attributed to a person by the use of additional information, should be considered information on an identifiable person. Anonymous information, on the other hand, falls outside the regulation.
The GDPR also encourages pseudonymization. It cites it as a data protection by design measure (article 25) and as a security measure (article 32), and recital 28 notes that it reduces the risks to the people concerned and helps controllers meet their obligations, without exempting them from any other measure.
Supervisory authorities stress reversibility: pseudonymization can be reversed, anonymization cannot. On 16 January 2025 the European Data Protection Board (EDPB) adopted Guidelines 01/2025 on pseudonymisation. They confirm that pseudonymized data remain personal data, and explain how pseudonymization helps to comply with the principles of the regulation, starting with data minimisation and security.
Anonymization vs pseudonymization: the comparison table
The table below sums up the differences that matter in practice, when you prepare a contract, a case file or a spreadsheet before sending it.
| Criterion | Pseudonymization | Anonymization |
|---|---|---|
| Principle | Replace identifiers with pseudonyms, the correspondence being kept separately | Delete or transform any information that allows identification |
| Going back | Possible for whoever holds the table | Impossible by reasonable means |
| Status under the GDPR | Personal data, regulation applies | Outside the scope of the regulation |
| Example | PERSONNE_001 with an encrypted table | [PERSONNE], age as a band, no table |
| Typical uses | Hand a file to a third party or an AI, then put the names back | Publish, archive a template, share a case study |
Two misunderstandings come up often. The first is believing that a pseudonymized document becomes anonymous as soon as it leaves its author. For whoever keeps the table, it remains personal data. For a recipient, the Court of Justice of the European Union ruled on 4 September 2025 (case C-413/23 P) that the answer depends on that recipient's reasonable means of re-identification: the assessment is made case by case.
The second concerns encryption. Encrypting a file makes it unreadable without the key, but anyone who holds the key reads everything, names included. Article 32 of the GDPR lists "the pseudonymisation and encryption of personal data" as two distinct measures. They combine well: a pseudonymized document whose table is itself encrypted gets the benefits of both. The recipient reads a usable text, and only the person who knows the password can restore the names.
Pseudonymize or anonymize a document: how to choose
One question settles it: will you need to recover the real values?
- Yes: you give a contract to an AI for a summary, a file to an expert for an opinion, a spreadsheet to a contractor for analysis, and you need to put the names back into the result. Pseudonymization is the answer, with a table kept separately and protected.
- No: you publish an example, share a training case, archive a template. Aim for anonymization: no table, indirect identifiers generalized or deleted, a review against the three criteria of singling out, linkability and inference.
In the first case, remember that the document you send is still personal data: the recipient must offer appropriate safeguards, and the transfer must have a clear purpose. Pseudonymization greatly reduces the risk; it does not remove the obligations, in particular informing the people concerned.
Biffer offers both approaches for each type of data: pseudonymize with a stable alias (PERSONNE_001), mask with a label ([PERSONNE]) or keep. The mapping table is optional. Encrypted with your password (Argon2id and AES-256-GCM) and kept on your computer, it plays exactly the role of the "additional information kept separately" of article 4. Without a table, the operation is irreversible. The software works offline, on Mac and PC. The settings are described on the page features, the logic of the table on the page anonymize a document, and the texts cited on the page regulations.
Pseudonymize or anonymize, as each document requires
Biffer, published by Opcadia and designed by Romain Rissoan, trainer and consultant, runs on Mac and PC, with no connection during processing. The free plan covers 5 files per month with every feature; unlimited use costs €10 excl. VAT (€12 incl. VAT) per computer, paid once.
Frequently asked questions
What is pseudonymization?
It is the replacement of the data that identify a person (name, number, address) with pseudonyms, the correspondence being kept separately and protected. Article 4(5) of the GDPR defines it. It reduces risks, but pseudonymized data remain personal data.
Are pseudonymized data personal data?
Yes for whoever holds the table: recital 26 of the GDPR says so expressly, and the EDPB confirms it in its Guidelines 01/2025. For a recipient with no reasonable means of re-identification, the Court of Justice of the European Union has accepted since 2025 a case-by-case assessment.
Is encryption a form of pseudonymization?
No. Encryption makes the whole file unreadable without the key, then entirely readable with it. Pseudonymization replaces only the identifiers and leaves the rest usable. Article 32 of the GDPR presents them as two distinct measures, which complement each other.
Your business documents anonymized, ready to be published or handed to an AI tool.
Biffer runs on your computer without sending a single file. Free for five files a month, unlimited for €10 excl. VAT per computer.
100% offline · Free: 5 files a month · No file sent