Anonymization vs. pseudonymization

Pseudonymization vs. anonymization: the difference

Both replace personal data, but only one of them takes data out of the GDPR's scope. A short overview with examples.

  • We anonymize irreversibly
  • No mapping tables
  • Placeholders or fake values
  • Report for review
Microsoft PowerPointCase_Review_October.pptx

Case review: Smith v Acme Construction Ltd

  • Client: John Smith, 3 Linden Road, Manchester
  • Opponent represented by Peter Wolfe KC
  • Amount in dispute £18,450 · expert Dr. Sabine Kraus
  • Next hearing: Case No. 1:26-cv-04412

Notes: call Smith on (212) 555-1234 before the hearing.

The terms under the GDPR

  • Pseudonymization (Art. 4(5) GDPR): data can only be linked back to a person with additional information kept separately. Pseudonymized data is still personal data.
  • Anonymization (Recital 26): the person can no longer be identified by any means reasonably likely to be used. Anonymous data is outside the GDPR.
  • The difference is the key: if a mapping table exists anywhere, it's pseudonymization.

How it works

  1. 1

    Pseudonymize

    “John Smith” → “K-4711”, key table in a vault. Useful when you must re-identify later.

  2. 2

    Anonymize

    “John Smith” → [PERSON_1] or “Paul Rivera”, with no stored mapping. Useful for sharing, AI and training.

  3. 3

    Check the context

    Even without names, context can identify (“the mayor of Springfield”). Always review the result.

Example. Before and after.

Original

Pseudonymized: patient K-4711 (key: K-4711 = John Smith, in a vault)

Anonymized

Anonymized: patient [PERSON_1] (no mapping stored)

FAQ

Questions. Answered briefly.

Try it with your own document

10 pages per month are free. No subscription, no credit card.