Personal data in recruitment: what's covered
Types of personal data in recruitment
| Category | Examples | Status |
|---|---|---|
| Identity | Name, surname, photo | Collection authorised (necessary) |
| Contact | Email, phone, address | Collection authorised (necessary) |
| Career | CV, diplomas, experience | Collection authorised (necessary) |
| Evaluations | Interview notes, tests, reviews | Collection authorised (necessary) |
| Compensation | Current salary, salary expectations | Collection authorised (if relevant) |
| Ethnic origin | Any belonging information | FORBIDDEN in all circumstances |
| Health | Diseases, disability, medicines | FORBIDDEN (except medical fitness) |
| Religion / politics | Beliefs, union membership | FORBIDDEN |
Legal obligations: the 4 pillars
- 1
Legal basis for processing
To process candidate data, you need a legal basis. Most common: legitimate interest (recruiting is a legitimate company interest). Consent is rarely appropriate due to power imbalance between employer and candidate.
- 2
Informing candidates
Informing candidates is mandatory. Minimum content includes: processing controller identity, purposes, recipients, retention period, candidate rights and DPO contact if applicable.
- –Mention in the job advert
- –Link to privacy policy
- –Mention in application receipt
- 3
Limited retention period
General rule: no longer than necessary. Data of rejected candidates should not be kept indefinitely.
- 4
Respect candidate rights
Any candidate can exercise rights to access, rectify, erase, object, port and limit processing. Response time: 1 month maximum.
Recommended retention periods
| Situation | Recommended period | After that |
|---|---|---|
| Rejected candidate | 2 years max after last contact | Deletion or anonymisation |
| Hired candidate | Contract duration + legal archives | HR file archiving |
| CV database / pool | 2 years with consent renewal | Deletion or re-consent |
Best practices vs mistakes to avoid
- Minimise collected data (only what's necessary)
- Secure data (restricted access, encryption)
- Inform candidates at application
- Document processes (mandatory register > 250 employees)
- Train teams on GDPR rules
- Implement regular purge process
- Collect forbidden data (religion, health, political views)
- Keep CVs indefinitely without purge procedure
- Share applications without prior information
- Make automated decisions without human intervention
- Store on unsecured tools (personal Dropbox, Gmail)
- Ignore rights exercise requests
GDPR information notice model
Sanctions for non-compliance
CNIL sanction levels
| Level | Sanction | Example |
|---|---|---|
| Compliance order | Obligation to comply | Absence of information notice |
| Warning | Possible publication (name and shame) | Non-compliance with retention periods |
| Fine | Up to 20 M€ or 4% of global turnover | Collection of forbidden data |
GDPR compliance checklist recruitment
- Recruitment privacy policy drafted
Before any recruitment
- Information notice in adverts
Systematic from publication
- Retention periods defined
2 years max for rejected candidates
- Deletion process in place
Automatic or periodic manual purge
- Receipt with GDPR mention
For each application received
- Restricted access to candidate data
Only relevant people
- Rights exercise response procedure documented
Max 1 month deadline
GDPR recruitment FAQ
Can you check a candidate's LinkedIn profile?
Is appointing a DPO (Data Protection Officer) mandatory?
Must a recruitment ATS (software) be GDPR compliant?
What to do if a candidate requests data deletion?
Recruit in compliance with Aurelia
Aurelia was designed with GDPR in mind: 100% EU hosting, configurable retention periods, easy deletion, DPA signed with all sub-processors.
