Recognising Personal Data ยท Lesson 3 of 3

Pseudonymised data is still personal data

Study notesAbout 3 minutes. A full lesson with quick checks is on its way.

In short

Swapping names for codes is pseudonymisation. If anyone can still link the codes back to people, it's still personal data.

In your work

For a client's reporting dashboard you replace member names with random codes, but the lookup table sits in the same database. The dashboard data is still personal data and needs the same care.

What the UK rules say

  • The ICO is clear that pseudonymised personal data is still in scope of data protection law.
  • Pseudonymisation is still worth doing: it lowers risk, as long as the extra information that re-identifies people is kept separately and protected.

What to do

  1. Keep lookup tables and keys apart from the pseudonymised data, with tighter access.
  2. Call it 'pseudonymised', not 'anonymised', in documents and tickets.
  3. Watch for small groups and rare values that point to one person on their own.

Watch out for

  • Removing names but leaving postcodes, dates of birth or job titles that identify people.
  • Sharing 'anonymised' exports outside the team without a check.

In your organisation

Who decides whether a dataset is anonymous enough to share outside your organisation?

Your employer's own policies come first.

Sources

UK law and guidance, explained for learning. Not legal advice.