Skip to content
BENIBIX Learn

Pseudonymization vs Data Anonymization

People think pseudonymized data is anonymous. It is not. Names are swapped for a code, and a key that is kept can turn the code back into a person. Anonymized data has no key and no way back. In law, the first is still personal data. The second is not.

Data🔒 Data Privacy

Pseudonymization

Swapping names and emails for a code. The same person always gets the same code.

Pseudonymization swaps the fields that name a person for a code, called a token or pseudonym. The same person always gets the same code, so you can still join and count them. The key that links codes back to names is kept apart, under tight control. With the key, the data can be traced back to the person. So in law it still counts as personal data.

Example
Analysts study what people buy by their code. They never see an email, but they can see that code 7f3a9c bought three times.
Why it matters
The data stays useful for study. If it leaks, far less harm is done.
Full entry
Data🔒 Data Privacy

Data Anonymization

Changing data so no one can ever be traced back from it.

Data anonymization changes data so no one can be identified from it, ever, by anyone. Names and IDs are removed. Details such as an exact age or address are made broad, such as an age band or a region. Rare rows that still stand out are dropped or merged. Done properly, there is no key and no way back. Truly anonymous data falls outside most privacy laws.

Example
A hospital shares visit data for research. It removes names, turns ages into bands and drops any group smaller than 10 people.
Why it matters
It is the only way to share personal data with few legal limits. It is also much harder to do well than it looks.
Full entry

In one line

Pseudonymization
Swapping names and emails for a code. The same person always gets the same code.
Data Anonymization
Changing data so no one can ever be traced back from it.