Glossary
Anonymisation
Definition
Changing information so that people are no longer identifiable, taking account of the means reasonably likely to be used to identify them.
Anonymisation removes identifiability, including identification through combinations of details. In the UK GDPR context, effectively anonymous information falls outside personal-data rules, but producing it still involves handling personal data.
A customer may include “Anonymisation” 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.
Anonymisation changes information so that it no longer relates to an identifiable person. In the UK GDPR context, the assessment considers the means reasonably likely to be used to identify someone, including other information available to the business or a recipient. Effectively anonymous information falls outside personal-data rules.
Imagine a small employer wants to publish staff survey results. Removing names may leave a single employee identifiable from a job title, age bracket and distinctive written comment. Grouping responses, removing revealing details or withholding very small groups may reduce that risk.
Anonymisation differs from pseudonymisation, where separate information can reconnect records to people. Replacing names with staff numbers does not establish anonymity if a directory links those numbers to employees. Nor does labelling an export “anonymous” change its contents.
Before sharing, assess the actual dataset, its recipients and other information they could use. Document the reasoning and reassess when circumstances change. The work of creating an anonymous dataset still involves processing the original personal data, so its handling needs an appropriate basis and safeguards.