Data protection
Pseudonymised or anonymous? The difference decides whether the GDPR applies
Pseudonymised data is still personal data, so every GDPR rule still applies to it. Only data that can no longer identify anyone, by any means reasonably likely to be used, falls outside the GDPR.
By FourWindsCurrent as at 4 minute read3 sources
The short answer
Pseudonymisation swaps the details that identify a person for a code, and keeps the key that links them back somewhere separate and secure. The data can be re-identified with that key, so the GDPR treats it as personal data.
Anonymisation removes the link for good. Recital 26 of the GDPR says the data protection principles don't apply to information that no longer relates to an identifiable person. The test is strict: you consider all the means reasonably likely to be used to identify someone, by you or by anyone else.
What the GDPR says pseudonymisation is
Article 4(5) defines it in three parts. The data can no longer be attributed to a specific person without additional information. That additional information is kept separately. And it's protected by technical and organisational measures so the link isn't made.
Recital 26 is just as clear about the result: data that has been pseudonymised, but could be attributed to a person with additional information, should be treated as information about an identifiable person. Pseudonymisation lowers the risk. It doesn't change the category.
| Pseudonymised | Anonymous | |
|---|---|---|
| Can anyone re-identify it? | Yes, with the key or other data | No, by any means reasonably likely to be used |
| Is it personal data? | Yes | No |
| Do the GDPR's rules apply? | All of them | None, once it is truly anonymous |
| Typical use | Analysis, testing, sharing with a processor | Published statistics, benchmarks |
Why pseudonymise if the rules still apply
Because the GDPR rewards it in several places. Article 25(1) names it as a measure for data protection by design. Article 32(1)(a) lists it, with encryption, as a security measure appropriate to the risk. Article 6(4)(e) lets you weigh it when deciding whether a new use of data is compatible with the original one.
It also helps if something goes wrong. A pseudonymised file sent to the wrong person reveals far less than the original, which matters when you assess the risk of a breach under the 72-hour rule.
Why anonymisation is hard to get right
Removing names is rarely enough. A date of birth, a postcode and a job title together can single out one person, and a small dataset makes that easier. The DPC's guidance on the two techniques stresses that anonymisation has to be effective to take data outside the GDPR, and that the assessment has to account for other data that could be combined with yours.
The EDPB published draft guidelines on pseudonymisation for consultation in January 2025. They describe the technique in detail, including how to separate the key and who it should be hidden from.
A useful test
If anyone in your firm could put a name back on a row, by looking it up or by asking a colleague, treat the data as personal data.
An accountancy practice, worked through
Take an accountancy practice that wants an outside analyst to compare fee levels across its client base. The practice exports the data, replaces each client name with a code, drops addresses and PPS numbers, and keeps the code list on its own system.
For the practice this is pseudonymised data, so it's still personal data. The analyst is acting for the practice, which makes them a processor, and that needs a contract under Article 28. Our controller or processor guide covers how to tell which role applies.
If the practice then publishes only totals by fee band, with no band small enough to point to one client, that published table is anonymous and falls outside the GDPR.
Writing it down
Record which datasets you pseudonymise, where the key lives and who can reach it. That note belongs in your record of processing and in any DPIA for the work. Eurus keeps each check result it records with a SHA-256 fingerprint chained to the one before, so the record you show an auditor can be verified at eurus.ie/verify.
Questions
- Is pseudonymised data personal data under the GDPR?
- Yes. Recital 26 says data that could be attributed to a person by using additional information should be treated as information about an identifiable person.
- Is encrypted data pseudonymised?
- They're different measures, and Article 32(1)(a) lists them side by side. Encryption protects data from anyone without the key. Pseudonymisation replaces the identifiers so the data can be used without showing who it's about.
- Does anonymised data need a lawful basis?
- Not once it's truly anonymous, because the GDPR no longer applies. The act of anonymising is still processing of personal data, so that step needs a lawful basis.
- Is hashing an email address enough to anonymise it?
- No. Anyone who has the same email address can hash it and match it. A hashed identifier is a pseudonym at best.
Sources
See where you stand, in Eurus
Connect your systems once, and Eurus does the talking. It works out which laws apply, finds your AI tools, suppliers and people, and keeps the proof itself. If there is a gap you can't close yourself, FourWinds reviews it and sends a fixed quote.
Try Eurus liveWho wrote this
FourWinds · Compliance experts, and the makers of Eurus
FourWinds writes and maintains the legal explainers on this site, and does the compliance work behind them. Every date and article number here is checked against the legislation itself before it is published, and each article shows the date it was last checked.
Questions and corrections go to support@fourwinds.ie.
More about how we work →Read next
- Data protectionSpecial category data: what counts, and what holding it changes
- Data protectionController or processor? How to tell which you are, relationship by relationship
- GDPRDo you need a DPIA? Ireland has its own list, and it is specific
Written on 14 November 2026; it describes the law as FourWinds read it on that date. How we check the law.