Benefits-record anonymisation is the removal of claimant PII from a welfare or benefits file. Section 123 of the Social Security Administration Act 1992 makes it a criminal offence for anyone holding social-security information to disclose it without lawful authority, which is exactly why raw claimant data cannot simply be handed to a researcher or oversight body. Once the file is truly anonymous, UK GDPR Recital 26 takes it out of scope instead. anonym.plus does the anonymisation on your own device, so the data stays useful for reporting.
When this applies
An oversight body or a researcher asks for benefits data. The file names claimants and holds their IDs, addresses, and award amounts.
How anonym.plus handles it
- Open the benefits file in anonym.plus on your device.
- The tool flags claimant names, IDs, and contacts.
- Swap each one for a non-reversible label.
- Keep no re-link key if you want it outside scope.
- Confirm the award figures still read clearly.
- Save the anonymous file on your machine.
What you need to provide
- The benefits file (CSV, XLSX, PDF, or DOCX).
- Replace, with the reversible map turned off.
- Optional language setting for the records.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | claimant name → [CLAIMANT] |
| Identifiers | UK_NINO | QQ 12 34 56 C → [NINO] |
| Location | LOCATION | home address → [ADDRESS] |
| Contact | PHONE_NUMBER | contact phone → [PHONE] |
| Dates | DATE_TIME | claim date → [DATE] |
| Identifiers | NATIONAL_ID | benefit no. → [ID] |
Compliance achieved
- True anonymity puts the data outside scope by UK GDPR Recital 26.
- Reduces the risk of an unlawful-disclosure offence under Social Security Administration Act 1992 s.123 by working locally, before any wider sharing.
- Hides claimant PII while award figures stay for analysis.
- On-device work supports UK data residency.
- Reads CSV and spreadsheet files as well as documents.
Anonymise benefits records offline — see plans & start free →
Limitations & cautions
True anonymity is a high bar. If you keep a reversible map, the file is pseudonymous, not anonymous, and stays in scope for both UK GDPR and the s.123 offence, which applies to identifiable social-security information, not just formally 'personal data'. A rare award plus a small area can still re-identify. Weigh the residual risk before you treat the data as anonymous.
Frequently asked questions
Anonymous or pseudonymous — what is the difference?
Pseudonymous output keeps a key that can re-link it, so it stays personal data. Anonymous output drops that key for good. Only then does Recital 26 take it out of scope, and only then is a claimant no longer identifiable in the file at all.
Why does the Social Security Administration Act 1992 matter here?
Section 123 makes unauthorised disclosure of social-security information a criminal offence for anyone who holds it in that capacity, not just an administrative slip-up. That is a real reason to anonymise a benefits extract on your own device before it goes anywhere near a researcher, auditor, or third-party system, rather than share the raw claimant file first and clean it up later.
Can I keep the award amounts?
Yes. The figures stay for reporting. Only personal IDs are removed, so trends and totals are still analysable once the claimant identity is gone.
Does it read a benefits spreadsheet?
Yes. CSV and XLSX files are scanned column by column, and free-text fields get the same review as documents.