Manual and automatic anonymisation and how it differs from deletion.
Candidate anonymisation
Anonymisation masks personal data for a candidate in the system without fully removing the profile from the recruitment. Use it when you need to limit identifying information but keep process history.
Anonymisation vs. deletion
- Anonymisation - personal data (name, email, CV, etc.) is masked; the profile still exists in the recruitment.
- Deletion (GDPR module) - permanently removes the candidate from all recruitments in your context (see How to delete a candidate’s data).
Manual anonymisation
- Open the candidate list in a recruitment.
- Select one or many candidates and choose Anonymise (bulk action supported).
- Confirm in the dialog.
Screenshot placeholderCandidate list with single and bulk anonymisation option
Automatic anonymisation
A team administrator can enable auto-anonymisation under Settings → Team → Auto-anonymisation:
- Enable automatic anonymisation.
- Choose a retention period (e.g. 6, 12 or 24 months).
- The system periodically anonymises candidates who exceed the selected storage period.
After anonymisation
- Personal data is no longer visible on the profile.
- An anonymised candidate cannot be saved to the Candidate pool or tagged.
- Choose anonymisation vs. deletion according to your organisation’s data retention policy.
Screenshot placeholderAnonymised candidate profile with masked personal data
Related: Is Hero Parser aligned with GDPR?, How to delete a candidate’s data.
Screenshot placeholderTeam settings - Auto-anonymisation section with retention period selector
Content is updated regularly.
Hero Parser - help materials.