Export de-identification is the removal of personal data from electronically stored data before disclosure. Rule 31.4 defines a 'document' broadly enough to reach a database export, and Practice Direction 31B sets how a party searches and exchanges that material electronically. anonym.plus does the clearing pass on your own device, so nothing is uploaded before the parties even agree a search protocol.
When this applies
Before this exercise you scope a bulk export of thousands of records, often as part of an Extended Disclosure discussion in the Business and Property Courts. Sending that raw export to a cloud vendor before the parties settle on a search protocol is itself a privilege and confidentiality risk, and it pre-empts the proportionality assessment the rules ask the parties to make.
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
- Falls within the broad document definition of CPR 31.4, so an export is treated as disclosable material, not exempt from the process.
- Prepares the set for the electronic-exchange format in CPR PD 31B.
- Supports a proportionate search under CPR 31.7, ahead of any Extended Disclosure discussion under CPR PD 57AD in the Business and Property Courts.
- Keeps row links steady, so the data stays useful for review.
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 that fall within the wide definition of a 'document' — anything in which information is recorded, not only paper. A separate rule then sets how that electronic material is searched and exchanged.
Why de-identify before the conference?
Scoping needs counts and field coverage, not identities. A cleared export lets you share volume figures with the other side, or discuss an Extended Disclosure model, without exposing anyone's personal data first.
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, which keeps the proportionality assessment meaningful.
Does it handle both CSV and document exports?
Yes. Tidy CSV or JSON columns and bundled files are both supported, whichever form the export takes as part of the disclosable material.