Skip to content

What is the difference between pseudonymisation and anonymisation?

Pseudonymisation: replaceable via a key, still personal data. Anonymisation: no longer reidentifiable, falls outside GDPR. The line is stricter than most people think.

Try this first

  1. 1Pseudonymisation: names to tokens, emails to hashes, BSN to internal ID. The mapping still exists somewhere. GDPR still applies.
  2. 2Anonymisation: reidentification is reasonably impossible. All linking removed, including indirect (postcode + age + role).
  3. 3Test: can you, with the remaining data plus realistic public info, identify someone? If yes, it is pseudonymous, not anonymous.
  4. 4For analytics on production datasets, pseudonymisation often suffices but the key must be secured separately.
  5. 5For sharing or public release, only real anonymisation is safe. Often k-anonymity or differential privacy is needed.

When to bring us in

Unsure whether a dataset is truly anonymous? Treat it as pseudonymous. The AP scrutinises large datasets. We have tooling to verify.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.