The boilr Agent is live Read now→

Data residency decides whose law applies.

A straight answer, not a line in a sales deck.

Data residency is where your candidate and client data physically sits, and the law that follows from that location. It stops being a footnote the moment an agency adopts an AI tool.

recruiter-lexikon / data-residency
D
Data residency
Data residency
Defined
Definition

Where a vendor physically stores and processes an agency's data, and consequently which country's law governs it, covering every candidate CV, client record and enrichment an AI tool touches.

At a glance
Term Data residency
Used for Vendor due diligence and GDPR transfer checks
In boilr EU-hosted, zero data retention, documented in writing
b
boilr turns this term into a task
Defined here · operationalised by your AI employee

Data residency, explained for the desk.

What it is, why it matters, and how your AI employee runs it.

What it is

Data residency describes the physical location, the country or region, where a vendor stores and processes a piece of data, and the legal jurisdiction that comes with that location. For a recruitment agency, the data in question is rarely abstract. It is candidate CVs, call notes, email threads, enriched company and contact records, anything an ATS, a CRM or an AI copilot touches. Residency is not only about where that data sits at rest; it covers where it is processed too, since an AI model that reads a CV to score it or draft an email is processing the data on whatever infrastructure it runs on, wherever that happens to be.

Data residency is sometimes used loosely alongside data sovereignty and data localisation, but the terms are not identical. Residency is about location, full stop. Sovereignty is about whose law actually reaches that data, which does not always follow location: a US-incorporated vendor can be compelled to hand over data it stores on EU soil under the US CLOUD Act. Localisation is a legal requirement, imposed by a specific country, that data about its citizens must stay inside its borders. An agency only needs to know its residency facts; working out the legal consequences is what a privacy policy or a legal team does next.

If a vendor cannot say which country your data sits in, the honest answer is that they have not had to care yet.

Why it matters

Two separate pressures have made this question unavoidable for recruitment agencies. The first is AI adoption: every copilot, enrichment tool, scraper or outreach assistant a desk adopts is another vendor processing candidate and client data, often with less visibility than the ATS or CRM an agency already vets carefully. The second is client pressure: enterprise clients and their procurement teams increasingly run security questionnaires before signing a PSL or MSA, and "where does our data live" is now a standard line item, not a niche concern.

GDPR gives the question legal teeth. Chapter V restricts transferring personal data outside the EEA unless the destination has an adequacy decision (Article 45) or the transfer is covered by a safeguard such as Standard Contractual Clauses (Article 46). The 2020 Schrems II ruling invalidated the EU-US Privacy Shield because US surveillance law undercut the protection GDPR requires, and while the EU-US Data Privacy Framework, adopted in 2023, restored an adequacy route, it only covers US organisations that have actively self-certified to it. None of this is abstract for a recruitment agency: as the data controller, the agency carries the exposure if a vendor's transfer has no valid legal basis, not just the vendor.

How boilr handles it

boilr answers the residency question before an agency has to ask it. All boilr infrastructure runs inside the European Union: EU-based cloud providers, EU-based key management, and no third-party sub-processors outside the EU. Data never crosses into a jurisdiction outside EU territory, and that is a stated, documented position, not a default that happens to be true today.

boilr also runs on zero data retention: the candidate, contact and company data processed to generate a signal, a match or a task is not written to a persistent store once that job completes. There is less data sitting anywhere to ask about, less residency exposure to carry, and a straight answer ready for the next security questionnaire a client sends over, rather than a scramble to find out where things actually live.

Questions, answered.

Everything a working consultant asks about data residency, and how boilr puts it to work.

What is the difference between data residency and data sovereignty?

Data residency is about where data physically sits, the country or region hosting it. Data sovereignty is about whose law actually reaches that data, which does not always match the location: a vendor incorporated in the US can be compelled to hand over data it stores on EU servers under US law. An agency should ask about both, not just the server location on a sales deck.

Why do clients ask about data residency before signing with a recruitment tech vendor?

Enterprise clients and their procurement teams run security questionnaires before signing a PSL or MSA, and data residency is a standard line on that list now, not a niche question. If an agency cannot answer it, or has to go and ask its own vendors first, that delay alone can cost a mandate against a competitor who already has the answer in writing.

Does GDPR require candidate data to stay inside the EU?

Not strictly. GDPR allows transfers outside the EEA where the destination has an adequacy decision or the transfer is covered by a safeguard such as Standard Contractual Clauses. What it does not allow is transferring personal data with no valid legal basis at all, which is the position many agencies find themselves in once an AI tool is added without anyone checking where it actually processes data.

What should I ask an AI vendor about data residency before adopting their tool?

Ask which country the data is stored and processed in, whether any of it is used to train the vendor's AI models, how long it is retained, and who the sub-processors are. Ask for it in writing, not as a line in a sales call, because that is the version that actually holds up in a client security questionnaire.

How does boilr handle data residency in practice?

boilr runs entirely on EU infrastructure, with EU-based cloud providers, EU-based key management and no third-party sub-processors outside the EU. On top of that, boilr processes data to generate your signals, matches and tasks on a zero-retention basis, so once a job completes there is no persistent copy sitting on a server anywhere to ask about.

Helen Wright
Boilr gave us the BD structure and follow-up support to sign our first client and secure a job brief in under a month.
Helen Wright
Managing Director, 923 Jobs

Know exactly where your data lives.

boilr runs entirely on EU infrastructure with zero data retention, so the residency question is answered before a client ever asks it. One AI sales employee per consultant, built on a foundation you can actually show a procurement team.