ESI Export De-Identification with anonym.plus

Clean a bulk ESI export — fields and free text — without leaving your network.

ESI export de-identification is the removal of personal data from electronically stored information (ESI) you prepare for FRCP 26(f) planning. anonym.plus does this on your own device, so nothing is uploaded.

When this applies

Before a meet-and-confer 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

  1. Point anonym.plus at the export folder on your server.
  2. It scans both ID columns and free-text fields.
  3. Steady labels keep links across joined rows intact.
  4. Review the summary and tune the column rules.
  5. Replace or mask the confirmed PII.
  6. Save the clean dataset on your device for review.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONcustodian field → [PERSON_n]
IdentifiersUS_SSNssn column → [SSN]
DatesDATE_TIMEsent_date → [DATE]
ContactEMAIL_ADDRESSfrom_email → [EMAIL]
LocationLOCATIONaddress fields → [ADDRESS]
Free textPERSON / LOCATIONinline names → labels

Compliance achieved

Anonymize ESI 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 is ESI in this context?

ESI means electronically stored information — email, files, chat, and database records subject to discovery. FRCP 26(f) asks parties to plan how to handle it early.

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.