A recruitment agency holds more personal data than most companies its size: CVs, contact details, salary expectations, interview notes, sometimes information about health or family situations that candidates share in confidence. Under GDPR your agency is responsible for that data, and the applicant tracking system you choose decides how hard or easy it is to handle it properly.
This checklist covers the questions to ask any ATS vendor before you sign, including us. It is practical guidance, not legal advice. If your situation is unusual, talk to your data protection officer or a lawyer.
Where the data lives
1. In which country is the data stored?
Ask where the servers are, including backups. Data stored inside the European Economic Area is the simplest case. If data goes elsewhere, the vendor needs a valid transfer mechanism, such as an adequacy decision or standard contractual clauses, and you need to know about it to inform candidates.
2. Which sub-processors have access?
Hosting providers, email services, AI model providers and support tools can all process candidate data. Ask for the full list of sub-processors, where each one is based, and how the vendor will tell you when the list changes.
3. Will they sign a data processing agreement?
When you put candidate data in an ATS, the vendor processes it on your behalf. Article 28 of GDPR requires a written contract between you and that processor. A serious vendor has a data processing agreement (DPA) ready and will send it before you sign up. If they hesitate, treat it as a warning sign.
Security basics
4. How is the data protected?
At a minimum: encryption in transit and at rest, role-based access so each recruiter sees what they need, and multi-factor authentication for administrators. Ask whether the hosting infrastructure holds recognised certifications such as ISO 27001 or SOC 2.
5. Is access logged?
If a candidate asks who has seen their data, or if you suspect a problem, you need an audit trail. Check that the ATS logs access and administrative actions, and that you can see those logs.
6. What happens in a breach?
GDPR requires you to notify your supervisory authority within 72 hours of becoming aware of a personal data breach, unless it is unlikely to result in a risk to people. You can only do that if your vendor tells you quickly. Ask how and how fast they will notify you, and whether they have a documented incident response plan.
Candidates’ rights
7. Can you answer an access request in minutes?
Candidates have the right to know what data you hold about them and to receive a copy. In an ATS that keeps everything on the candidate record (CV, notes, emails, messages, applications), this is an export. In a setup where emails live in personal inboxes and notes in spreadsheets, it can take days.
8. Can you delete a candidate completely?
When a candidate asks to be forgotten, and you have no legal reason to keep their data, you need to delete it everywhere: the profile, attached files, notes and message history. Ask the vendor what deletion actually removes, and how long it takes to disappear from backups.
9. Does the ATS help with retention?
GDPR does not set a fixed retention period for candidate data, but it requires you to keep data no longer than necessary and to be able to justify the period you choose. Decide on a policy (for example, how long you keep candidates you have not been in contact with), document it, and check that the ATS lets you find and clean up records that have passed it.
Sourcing and consent
10. How do you inform sourced candidates?
When you add someone to your database from LinkedIn or a referral rather than from an application, Article 14 requires you to inform them, at the latest within one month and at the first contact if you contact them sooner. Your first outreach message is a natural place to do it, with a link to your privacy notice. Check that the ATS records where each profile came from, so you can show what you told whom.
11. Is consent recorded where you need it?
Most recruitment processing relies on legitimate interest or steps prior to a contract rather than consent. Where you do rely on consent, for example to keep a candidate in your pool for future roles, you need to be able to show when and how it was given. A field on the candidate record beats a folder of old emails.
AI matching
12. Can a person explain and override every AI decision?
Article 22 gives people the right not to be subject to decisions based solely on automated processing that significantly affect them. Rejecting a candidate qualifies. In practice, an AI score should inform a recruiter’s decision, never make it alone. That only works if the recruiter can read why the tool scored a candidate the way it did.
The EU AI Act goes further and classifies AI systems used to screen, rank or evaluate candidates as high-risk, with obligations for both the vendors who build them and the companies that use them, including human oversight and transparency. The application dates have been subject to change, so check the current timeline. Either way, ask any vendor how their matching works, what data it uses, whether it explains its scores and how you can correct it.
How Digger answers these questions
Since we are asking you to hold every vendor to this list, here are our answers. All Digger data is stored in EU data centres and never leaves the European Union, on infrastructure certified ISO 27001 and SOC 2. Data is encrypted at rest with AES-256 and in transit with TLS 1.3, access is role-based and logged, and administrative actions require multi-factor authentication. We provide a data processing agreement, our sub-processor list and a security overview on request. Candidates can request export or deletion of their data at any time, and every match score comes with a written explanation that a recruiter can read, question and override.
The details are on our security page. If you are reviewing tools now and have a questionnaire, send it to us and a founder will answer.