Glossary
Pseudonymisation
Definition
Changing personal data so it cannot identify someone without additional information that is kept separately and protected.
Pseudonymisation separates identifying information from the working dataset. In the UK GDPR context, the data remains personal data and still needs an appropriate legal basis and protection.
A customer may include “Pseudonymisation” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
Pseudonymisation changes personal data so that attributing it to a particular person requires additional information. Under the UK GDPR definition, that additional information is kept separately and protected against unauthorised use. The separation reduces exposure when staff do not need to know whose records they are analysing.
Imagine a small retailer gives an analyst purchase records labelled with random customer codes. A separate, access-controlled table links each code to the customer's account. The analyst can compare purchasing patterns without routinely seeing names, while an authorised customer-service team can still make the connection when needed.
This remains personal data in the UK GDPR context. Sharing both tables with the same unrestricted audience would defeat the intended separation. Other fields can also reveal identities: a distinctive delivery address or free-text note may identify someone without the linking table.
Identify which details are replaced and who can access the separate information that reconnects them. Test whether the remaining data could identify someone; predictable identifiers can sometimes be guessed, and pseudonymised data is not anonymous. Simply hashing predictable email addresses may leave them easy to guess. Pseudonymisation needs a suitable design and access controls; it does not remove the need for lawful processing.