Nine Background Check Mistakes That Break Privacy Law When You Hire Across Borders
A single screening package bought for every hire can break privacy law in many of the countries you recruit in. Here are nine common failures, the compliant fix for each, and what to ask your vendor.
Why one screening package for every country causes the first mistake
Most employers that start hiring abroad do the same thing. They take the package that works at headquarters (identity, right to work, employment history, education, criminal record, sometimes credit) and switch it on for every new country in the screening provider's dashboard. It's simple, and it's the most common way employee background check compliance falls apart once you hire across borders.
Mistake 1: running the same checks on every role in every country. Privacy laws such as the EU and UK GDPR, Brazil's LGPD, South Africa's POPIA, India's Digital Personal Data Protection Act and the UAE's PDPL all expect you to collect only what you need for a specific purpose. A criminal and credit check on a junior marketing hire in Lyon is very hard to defend under that test. The same checks on a treasury analyst in London may be fine. Regulators judge each check against the role and the country, not against your global policy.
What to do instead: build a screening matrix with role families down one side (general staff, finance and cash handling, access to vulnerable people, regulated roles, executives) and countries across the top. Each cell lists the checks you may run and why you need them. Then document a short proportionality assessment for every check beyond identity, right to work and references. In the EU and UK, higher-risk cells may also call for a data protection impact assessment.
Here's a hypothetical. A 120-person software company hiring in five countries might end up with a matrix where most hires get only identity, right-to-work, employment and education verification, and criminal and credit checks go to finance and security roles only. The narrower package often costs less too, since per-hire price is driven largely by criminal and credit searches.
Criminal and credit checks: where the rules diverge most
Mistake 2: running criminal record checks the law doesn't allow for that role. Under GDPR Article 10, employers can process criminal conviction data only where EU or member-state law authorizes it, and national rules differ a lot. In the UK, a basic check is available for most roles, but standard and enhanced checks are limited to eligible positions such as work with children or certain regulated roles. In Germany and France, the employer usually can't pull the record directly. The candidate obtains their own certificate, and you can ask for it only when the role justifies it. In the US, many states and cities have fair-chance laws that delay criminal history questions until after a conditional offer and require an individualized assessment before you reject someone.
Mistake 3: running credit checks where they're restricted or presumed disproportionate. Several US states and cities limit employment credit checks to specific roles. Data protection authorities in much of Europe and Latin America generally treat them as excessive outside finance and fraud-sensitive positions. Even where they're allowed, the bureau usually requires the candidate's explicit authorization.
The table is a starting point for scoping, not legal advice. Rules change, so confirm each country with local employment counsel.
| Jurisdiction | Criminal record checks | Credit checks |
|---|---|---|
| United Kingdom | Basic check broadly available; standard/enhanced only for legally eligible roles | Permitted where relevant; common in regulated financial roles |
| Germany | Candidate supplies certificate; only where role-relevant | Generally disproportionate outside specific finance roles |
| France | Employer generally cannot obtain directly; candidate asked only where justified | Generally hard to justify for hiring |
| Brazil | Only where the law or the nature of the role justifies it; unjustified requests risk damages claims | Often challenged as discriminatory; take local advice |
| India | Police verification and court-record searches via vendors; DPDP Act consent rules apply | Possible with consent, typically for finance roles |
| UAE | Police clearance certificates commonly requested; PDPL, or DIFC/ADGM rules in those free zones | Less common; justify by role |
| South Africa | Via accredited vendors; criminal data is special personal information under POPIA | Generally allowed with consent where the role involves trust or finances |
| United States | Federal FCRA plus state and city fair-chance laws on timing and assessment | Restricted in several states and cities |
Questions for your screening provider: Can you block specific check types by country and role, or does every package travel everywhere? Who maintains your country-by-country legal guidance, and how often is it reviewed? Where the employer can't obtain the record directly, do you have a candidate-initiated process?
Consent obtained too early, or relied on when it shouldn't be
Mistake 4: collecting criminal check consent at the application stage. Many applicant tracking systems bundle a screening authorization into the application form. That's risky twice over. First, in a growing number of jurisdictions, including US fair-chance cities and states, criminal checks belong after a conditional offer. Second, consent gathered from hundreds of applicants you'll never screen means holding data you have no use for.
Mistake 5: treating consent as the legal basis everywhere. European regulators have long held that consent in an employment relationship is rarely "freely given," because candidates feel they can't refuse. Consent can also be withdrawn partway through. In the EU and UK, the usual basis is legitimate interests or legal obligation, plus an Article 10 authorization for criminal data. Consent-based regimes work differently. India's DPDP Act makes consent central, and the US FCRA requires written authorization on a standalone disclosure document, not buried among other terms.
What to do instead:
- Trigger screening only after a conditional offer, and only for the checks in that role's matrix cell.
- Keep a country-specific candidate notice explaining each check, the legal basis, who processes the data, where it goes and how long it's kept.
- Use a standalone authorization where the law requires one (the US, for example), and don't present it as consent where your basis is legitimate interests.
- Log when the notice was shown and which version, so you can prove it later.
Vendor questions: Can your candidate portal show different notices and legal-basis wording by country? Can initiation be locked until the ATS records an offer? Is the US disclosure delivered as a standalone document?
Data sent abroad, and vendors you can't see
Mistake 6: transferring candidate data across borders without a valid transfer mechanism. Screening across countries nearly always moves data. A candidate in Spain is screened by a vendor whose platform is hosted in the US, with a court search run by a partner in Portugal. Every leg of that route needs a lawful basis. Under the GDPR, that means an adequacy decision (such as the EU-US Data Privacy Framework for certified US companies), standard contractual clauses with a transfer impact assessment, or binding corporate rules. The UK has its own addendum and transfer agreement. China's PIPL, Brazil's LGPD, Saudi Arabia's PDPL and others set their own transfer conditions, some involving regulator filings or standard contracts.
Mistake 7: not knowing who actually runs the check. Large screening firms often cover dozens of countries through local researchers, court runners and credential-verification partners. If you can't name them, you can't assess them, and under most privacy laws you remain accountable for what they do with your candidates' data.
What to do instead: sign a data processing agreement that covers the vendor and its sub-processors. Get a current sub-processor list by country, with the right to object to changes. Map where data is stored, where it's accessed from, and which transfer mechanism covers each route.
Vendor questions:
- Where is candidate data hosted, and can we choose an EU, UK or other regional data residency option?
- Which sub-processors handle checks in each of our hiring countries, and are they your staff or third parties?
- What transfer mechanism covers each international transfer, and will you share your transfer impact assessment?
- Which security certifications do you hold (ISO 27001 or SOC 2 Type II), and do they cover your local partners?
On cost, typical 2026 market ranges put domestic packages at roughly $25 to $120 per hire, and international criminal or credential checks at roughly $40 to $200 or more per country searched, depending on jurisdiction and contract. Vendors with regional hosting and full sub-processor lists don't always charge more. Confirm current pricing with each one.
Keeping results too long and rejecting without a fair process
Mistake 8: keeping screening results indefinitely. Reports often get uploaded to the HRIS and stay as long as the employee does, or forever for rejected candidates. Most privacy laws require deletion once the purpose is fulfilled. UK DBS guidance, for instance, generally expects certificate information to be kept no longer than six months unless there's a specific reason. Reports on unsuccessful candidates usually need to be kept only as long as the local window for a discrimination claim.
What to do instead: set retention by country and outcome. Keep the hiring decision and the fact a check was completed, and delete the full report on a fixed schedule. Make sure the vendor deletes its copy on the same schedule, and ask for a deletion certificate or audit log.
Mistake 9: rejecting candidates on a flag without letting them respond. Vendor databases mismatch names, and records can be outdated or expunged. The US FCRA requires a pre-adverse action notice, a copy of the report and a waiting period before a final decision. GDPR Article 22 restricts decisions based solely on automated processing. Fairness expectations elsewhere point the same way.
What to do instead: require a human to review any adverse finding. Assess its relevance to the role, including how serious it was, how long ago it happened and what the person has done since. Let the candidate dispute or explain before you decide. Ask your vendor whether it automates US adverse-action notices, how it handles disputes, and whether any "auto-adjudication" scoring can be switched off for non-US hires.
Next step: before your next international hire, ask your current provider for three documents: its country-level check catalogue, its sub-processor list with transfer mechanisms, and its default retention periods. If it can't supply all three within a couple of weeks, start a formal provider review, and have local counsel sign off on the screening matrix for each country you hire in.
Frequently asked questions
Can we use one global background screening provider for every country we hire in?
Often, yes. Several large providers claim coverage in well over 100 countries, but much of it runs through local partners rather than their own staff. What matters is whether the platform can restrict checks by country and role, show country-specific notices, and document transfer mechanisms for each route. Ask for a country-by-country breakdown before you sign rather than relying on a headline country count.
Is candidate consent enough to make a criminal record check lawful under GDPR?
Usually not. European regulators consider consent in employment rarely freely given, and criminal data also needs a specific authorization under EU or member-state law. Most employers rely on legitimate interests or a legal obligation, backed by a proportionality assessment and a clear candidate notice. Confirm the right basis for each country with local counsel.
When in the hiring process should background checks start?
For most checks beyond identity and right to work, the safest point is after a conditional offer. Many US fair-chance laws require that timing for criminal history, and it limits data collection to people you actually intend to hire. Right-to-work checks may need to happen earlier where the law requires them before employment starts.
How long should we keep background check reports?
Only as long as you need them: long enough to make the decision and defend it within the local limitation period. Many employers record that a check was done and its outcome, then delete the full report within months. UK DBS guidance, for example, generally points to six months for certificate information. Set periods by country and make sure your vendor deletes its copy on the same schedule.
Written by the Talent Desk Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.