Skip to content
Espresso Data Privacy

Share

Pseudonymisation and anonymisation – the difference

In pseudonymisation, identifying details are replaced with substitute values; with a separately kept mapping, the link to the person can be restored. In anonymisation, the link to the person is permanently removed – the data is then no longer personal data.

What is pseudonymisation?

The GDPR defines pseudonymisation as processing in which data can no longer be attributed to a specific person without additional information – provided that this information is kept separately and protected (Art. 4 no. 5 GDPR). A typical approach is to replace names and identifiers with substitute values and keep the mapping separately.

The advantage: you can keep working with the pseudonymised data, and the result can be attributed to the right person again when needed.

What is anonymisation?

Anonymisation removes the link to the person in such a way that the person can no longer be identified with reasonable effort (cf. Recital 26 GDPR). Common methods are removal, generalisation – such as an age group instead of a date of birth – and aggregation into groups.

The catch lies in the combination: date of birth, postcode and gender together can make a person identifiable again, even if the name is missing.

The difference at a glance

Criterion Pseudonymisation Anonymisation
Link to the person can be restored with the mapping permanently removed
Legal classification remains personal data for anyone who has the mapping no longer personal data
Data protection law applies yes – for the controller; for recipients without the mapping, depending on the circumstances no
Typical use Sharing with AI and service providers, analyses that link back Statistics, research, retention without reference to individuals
Route back to the person possible not intended

An example

The same record, three times (all details fictitious):

Field Original Pseudonymised Anonymised
Name Anna Muster Customer K-4711 –
Date of birth 12.03.1984 12.03.1984 Age group 40–49
Place of residence Lucerne Lucerne Central Switzerland
Request Query about the policy Query about the policy Query about the policy

When to use which method?

Pseudonymisation is the right choice when the result must find its way back to the person: for an AI response on a case, for processing by a service provider or for analyses with follow-up questions. Anonymisation is the right choice when the link to the person is no longer needed, for example for statistics or after a retention period has expired.

In Switzerland – and since a 2025 ruling by the CJEU also in the EU – a relative approach applies: what matters is whether the respective recipient can identify the person with reasonable effort. For the organisation that keeps the mapping, pseudonymised data always remains personal data.

How Espresso helps

Privacy Delivery pseudonymises texts and documents before they are shared and puts the original values back into the response.

  • Pseudonymise

    Personal data in texts and documents is replaced with neutral substitute values before it goes to an AI or to third parties.

  • Re-identify

    The response gets the original values back – as long as you keep the mapping. The mapping stays in your environment.

  • Evidence

    The date, type, destination and person of every transfer are recorded – and for exports, the purpose as well.

Frequently asked questions

Is pseudonymised data still personal data?

For anyone who has the mapping, yes. For a recipient without the mapping, this may differ depending on the circumstances – but the controller's obligations remain.

Is encryption the same as pseudonymisation?

No. Encryption makes data unreadable without the key. Pseudonymisation replaces individual details, while the rest remains readable and usable. Both protect data, but for different purposes.

May anonymised data be retained indefinitely?

Data protection law no longer applies to it, provided it is genuinely anonymous. It is worth checking, however, whether new data or links could make a person identifiable again.

Should data be pseudonymised before it is passed to an AI?

This is often the better approach, because the AI then receives no real names or identifiers. The other obligations – purpose, contract, transparency – still apply.

See Espresso in 30 minutes

We will show you the cockpit with sample data – and discuss where you should start.

Request a demo

or write directly to info@espressodataprivacy.com