A core-system export usually goes somewhere, and the destination is what the law reacts to. UK GDPR Art. 28(3) requires a written contract with any processor that handles it. Art. 30 requires the processing to appear in your records. Chapter V restricts sending it outside the UK unless a transfer mechanism covers it — in practice the ICO's International Data Transfer Agreement, or the UK Addendum to the EU standard clauses, both available since 21 March 2022. Art. 35 requires a DPIA where large-scale processing is likely to be high risk. A file that carries no personal data raises none of those questions. anonym.plus strips each column on your machine, so the structure stays usable while customer details are shielded.
When this applies
A vendor abroad will model attrition on a core dump. As personal data that is a Chapter V transfer with a contract, a records entry and possibly a DPIA behind it. De-identified first, it is a much shorter conversation.
How anonym.plus handles it
- Point anonym.plus at the dump on your machine.
- It scans every column for the identifier set.
- Local OCR reads any imaged rows in the mix.
- Decide whether to keep or drop the name map.
- Apply Replace or Mask across the columns.
- Save the clean file locally.
What you need to provide
- The data dump (CSV, JSON, or PDF).
- An operator: Replace, Redact, or Mask.
- The name map ON to re-link, or OFF for true anonymity.
PII & financial identifiers detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | customer column → [PERSON] |
| Financial | UK_BANK_NUMBER | account column → ****0091 |
| Identifiers | UK_NINO | NINO column → [NINO] |
| Contact | PHONE_NUMBER | phone column → [PHONE] |
| Financial | IBAN_CODE | IBAN column → [IBAN] |
| Location | LOCATION | address column → [ADDRESS] |
Compliance achieved
- Reduces what a processor contract under UK GDPR Art. 28(3) has to cover in the first place.
- Keeps your UK GDPR Art. 30 records honest about what actually leaves the core system.
- Removes the personal data that would make a transfer a UK GDPR Chapter V matter needing the ICO's International Data Transfer Agreement.
- Feeds the risk assessment a UK GDPR Art. 35 DPIA needs for large-scale processing.
- Recognises the re-identification offence in DPA 2018 s.171; nothing is uploaded.
Anonymise retail-banking exports offline — see plans & start free →
Limitations & cautions
Stripping direct identifiers leaves quasi-identifiers — age, branch, tenure, amount — that can re-link a person when combined. If the set is still personal data, Chapter V and Art. 28 still apply. Keep the name map off when the file must be truly anonymous, and test the result against the ICO's motivated-intruder test.
Frequently asked questions
Can the tool de-identify a CSV file?
Yes. It flags every value in the customer, account and contact columns, so you can strip them together in one pass rather than column by column.
Does de-identifying remove the need for a transfer agreement?
Only if the result is genuinely anonymous. UK GDPR Chapter V applies to personal data, so a truly anonymous export falls outside it. A set a recipient could reasonably re-link is still personal data, and the International Data Transfer Agreement or the UK Addendum is still needed.
Should I keep the name map for a data dump?
Keep it on only where you must re-link results later, and guard it as carefully as the source. Turn it off for a one-way result — and remember DPA 2018 s.171 makes re-identifying a de-identified set without consent an offence.