ATS export de-identification is the removal of personal data from a tracking dump. Reusing recruitment data for funnel analytics is a further purpose the UK GDPR Art. 5(1)(b) test allows only where it stays compatible with the original purpose, and Art. 89(1) expects safeguards such as pseudonymisation when data is kept for that kind of reporting. If the same data ever feeds a ranking or scoring step, Art. 22 comes into play too. anonym.plus marks names, emails, and references 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, reused well beyond the original hiring decision it was collected for. You strip the direct columns before the data feeds a dashboard, applying the safeguard Art. 89(1) expects for that further, statistical use.
How anonym.plus handles it
- Open the export in anonym.plus on your device.
- The app scans each row for direct identifiers.
- It marks names, emails, phones, and references.
- Confirm the markings and keep stage and source columns.
- Turn the alias map OFF for irreversible removal.
- Save the cleaned dataset locally.
What you need to provide
- The export (CSV, XLSX, or TXT).
- An operator (Replace with stable pseudonyms, or Redact).
- The alias map turned OFF for true anonymity.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | row name → [APPLICANT] |
| Contact | EMAIL_ADDRESS | emails → [EMAIL] |
| Contact | PHONE_NUMBER | phones → [PHONE] |
| Identifiers | UK_NINO | NINO column → [NINO] |
| Location | LOCATION | town column → [LOCATION] |
| Dates | DATE_TIME | applied date → [DATE] |
Compliance achieved
- Reuses hiring data for analytics compatibly with UK GDPR Art. 5(1)(b).
- Applies the safeguard Art. 89(1) expects when data serves a statistical, not a decision, purpose.
- Keeps stage and source columns for funnel analytics.
- Offline work keeps the dataset off the cloud.
Anonymise applicant tracking exports offline — see plans & start free →
Limitations & cautions
A combination of town, role, and date can still single out a rare person, and Art. 89(1) safeguards do not remove that risk on their own. Aggregate or bucket small groups before you share the dataset.
Frequently asked questions
Can a hiring dataset be reused for a dashboard?
UK GDPR Art. 5(1)(b) allows further use only where it is compatible with the original recruitment purpose, and Art. 89(1) expects safeguards such as removing direct identifiers first. anonym.plus applies that safeguard on export.
Can I keep funnel metrics after stripping names?
Yes. Stage, source, and outcome columns stay, so conversion analytics still work without direct identifiers.
Does ranking candidates change the rules here?
If the export later feeds an automated ranking step, UK GDPR Art. 22 applies to that decision, separate from the analytics safeguard this task addresses.