Export de-identification is the removal of personal data from electronically stored data you prepare for disclosure under CPR Part 31. anonym.plus does this on your own device, so nothing is uploaded.
When this applies
Before disclosure you scope a bulk export of thousands of records. Sending that data to a cloud vendor is a privilege and breach risk.
How anonym.plus handles it
- Point anonym.plus at the export folder on your server.
- It scans both ID columns and free-text fields.
- Steady labels keep links across joined rows intact.
- Review the summary and tune the column rules.
- Replace or mask the confirmed PII.
- Save the clean dataset on your device for review.
What you need to provide
- The export as CSV, JSON, or a bundle of files.
- A column map for known ID fields.
- Replace with a steady label map to keep table joins.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | custodian field → [PERSON_n] |
| Identifiers | UK_NINO | nino column → [NINO] |
| Dates | DATE_TIME | sent_date → [DATE] |
| Contact | EMAIL_ADDRESS | from_email → [EMAIL] |
| Location | LOCATION | address fields → [ADDRESS] |
| Free text | PERSON / LOCATION | inline names → labels |
Compliance achieved
- Scopes the export for disclosure under CPR Part 31.
- Keeps row links steady, so the data stays useful for review.
- Local work keeps privileged data off any cloud vendor.
Anonymise data exports offline — see plans & start free →
Limitations & cautions
Bulk data mixes tidy columns with messy free text. Column rules handle the first well. Free-text fields need the same review as any note. Test a sample before a full run, and confirm joins still hold after the swap.
Frequently asked questions
What counts as electronically stored data here?
It means email, files, chat, and database records subject to disclosure. CPR Part 31 sets the duty to disclose documents, including those held in electronic form.
Can records stay linkable after the swap?
Yes. A steady label map swaps each ID the same way, so rows for one custodian still join while no real identity is left.
Does it handle both CSV and document exports?
Yes. Tidy CSV or JSON columns and bundled files are both supported.