Solutions · Privacy

GDPR and candidate data: a practical checklist for small teams

This is a practical overview, not legal advice. GDPR applies to candidate data whatever tool you use — a spreadsheet, an inbox or an ATS. The habits below matter more than the software.

A GDPR checklist for candidate data

  • Know your lawful basis (usually legitimate interest or consent for talent pools)
  • Tell candidates what you store, why and for how long (a privacy notice on your job ad)
  • Collect only what you need for the hiring decision
  • Set a retention period and delete or anonymize rejected candidates after it
  • Be able to find, export and delete one person's data when they ask
  • Limit access to people involved in hiring; avoid emailing CV files around

Why spreadsheets make this harder

Copies of a hiring sheet end up in inboxes and downloads folders, which makes deletion requests and retention hard to honour. Keeping candidates in one shared place — whatever tool that is — makes it much easier to find and remove someone's data.

$149/month flat. Unlimited seats and jobs.

Sign up, verify your email, choose your plan. Import your spreadsheet and have a working pipeline today — card charged after a 3-day trial.

Get started

Questions people ask

How long can I keep candidate data under GDPR?

GDPR doesn't set a fixed number; you must justify it. Many EU employers use 6–12 months after the hiring decision, with consent for longer talent-pool storage. Check with your local data protection authority or a lawyer.

Is a spreadsheet GDPR compliant?

Compliance depends on how you process data, not the tool. Spreadsheets are allowed but copies and sharing make retention and deletion harder to control.

Related

RecruitFlow.io is an independent product, not affiliated with Recruiterflow.com or any other tool named here. Competitor pricing is summarized from public pages and may change.