Applicant Tracking Export De-Identification with anonym.plus

Strip personal columns from an applicant-tracking export before analytics.

ATS export de-identification is the removal of personal data from a tracking dump. GDPR Recital 26 places truly anonymous data outside the rules. anonym.plus marks names, emails, and IDs across rows on your device, so funnel analytics stay safe and no one is singled out.

When this applies

A pipeline export holds names, emails, and stages for thousands of people. You strip the direct columns before the data feeds a dashboard.

How anonym.plus handles it

  1. Open the export in anonym.plus on your device.
  2. The tool scans each row for direct identifiers.
  3. It flags names, emails, phones, and IDs.
  4. Confirm the flags and keep stage and source columns.
  5. Turn the name map OFF for irreversible removal.
  6. Save the cleaned dataset locally.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONrow name → [APPLICANT]
ContactEMAIL_ADDRESSemails → [EMAIL]
ContactPHONE_NUMBERphones → [PHONE]
IdentifiersUS_SSNid column → [SSN]
LocationLOCATIONcity column → [LOCATION]
DatesDATE_TIMEapplied date → [DATE]

Compliance achieved

Anonymize applicant tracking exports offline — see plans & start free →

Limitations & cautions

A combination of city, role, and date can still single out a rare person. Recital 26 weighs that risk. Aggregate or bucket small groups before you share the dataset.

Frequently asked questions

Can I keep funnel metrics after stripping names?

Yes. Stage, source, and outcome columns stay, so conversion analytics still work without direct identifiers.

Is a stable pseudonym safe to publish?

Only if it cannot be reversed. Turn the name map OFF and bucket rare combinations to meet the Recital 26 bar.

Is the export uploaded?

No. The app runs locally, so the dataset stays on your device.