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.