ER Case Export De-Identification with anonym.plus

De-identify a case-management export so it no longer points to people.

ER case export de-identification is the removal of personal identifiers from a case-management extract, guided by GDPR Recital 26. That recital sets when data is truly anonymous. anonym.plus marks names and contacts on your device, so the dataset stays useful while people are shielded.

When this applies

An export lists cases with names, dates, and outcomes for analytics. You strip those identifiers under Recital 26 before the dataset is shared.

How anonym.plus handles it

  1. Open the export in anonym.plus on your device.
  2. The tool flags names, emails, and IDs in each row.
  3. Local OCR reads any scanned attachment.
  4. Turn off the name map for true anonymity.
  5. Swap or black out the confirmed items.
  6. Save the clean dataset locally.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONcase subject → [SUBJECT]
ContactEMAIL_ADDRESSuser@corp.eu → [EMAIL]
DatesDATE_TIMEopened 2025 → [DATE]
IdentifiersUS_SSN330-77-1209 → [SSN]
LocationLOCATIONLyon office → [LOCATION]
OrganizationORGANIZATIONAcme SAS → [EMPLOYER]

Compliance achieved

Anonymize ER case exports offline — see plans & start free →

Limitations & cautions

Recital 26 treats data as anonymous only if no one can re-identify a person. A rare combination of date, role, and outcome can still single someone out. Review the rows, and keep the name map off for genuine anonymity.

Frequently asked questions

How do I anonymise an export under Recital 26?

Turn the reversible map OFF and use Redact across the rows. Then check that no rare combination of fields singles out a person.

Can I keep a pseudonym for trend analysis?

Yes, with the name map on. That is pseudonymisation, still personal data, not the full anonymisation Recital 26 describes.

Is the export uploaded?

No. The app runs locally, so the dataset never reaches a cloud server.