Moving Employee Data Across Borders: Eight HR Privacy Mistakes and the Fix for Each
Your HRIS, EOR and payroll vendors move employee data across borders daily. Here are eight privacy gaps that cause the most trouble, how to fix each, and what to ask vendors before you sign.
Your HR stack is already a cross-border data pipeline
Hire a second employee in a second country and payroll files, bank details, ID scans and performance reviews start moving between systems. Your HRIS might be hosted in Frankfurt, your EOR's in-country partner might run payroll from São Paulo, and the support engineer who fixes a sync error could be logging in from Manila. Each hop is a cross-border employee data transfer, and each country you hire in has its own view of whether it's allowed.
Most companies don't treat global HR data privacy compliance as a project of its own. They assume it comes bundled with the vendor contract. Usually it doesn't. The vendor covers its obligations as a processor. You remain the controller (the "data fiduciary" in India's terms), and regulators and employees will come to you first.
The same eight mistakes recur. Each one below comes with a fix. Before any fix works, though, you need a data map: a spreadsheet listing every system that holds employee data, where it's hosted, who can access it and from which countries, and which sub-processors touch it. For a 50-person company in six countries, expect a few days of focused work. Without the map, you can't check anything else in this piece.
Transfer mechanisms: one contract doesn't cover every country
Mistake 1: Assuming the vendor's DPA covers the transfer
A data processing agreement (DPA) sets out how a vendor handles your data. It doesn't make an international transfer lawful. For GDPR HR data leaving the EU or EEA, you need a recognized mechanism: an adequacy decision for the destination, Standard Contractual Clauses (SCCs), Binding Corporate Rules, or a narrow derogation. If you rely on SCCs, you also need a transfer impact assessment (TIA) examining whether authorities in the destination country could access the data. The UK runs a parallel system, with its own International Data Transfer Agreement or an Addendum to the EU SCCs.
Fix: For every flow on your data map, write down the mechanism by name. Confirm the SCCs are signed in the right module (controller-to-processor is usual for HR vendors) and that a TIA exists for any destination without adequacy. If a vendor says it's "GDPR compliant" but can't name its transfer mechanism, treat that as a red flag.
Mistake 2: Treating every country as if it were the EU
SCCs built for the EU don't satisfy China, and they don't automatically satisfy Brazil or Saudi Arabia either. The rules differ widely. This table is a general orientation, and the details change, so verify current requirements locally:
| Jurisdiction | Law | How HR data transfers generally work |
|---|---|---|
| EU / EEA | GDPR | Adequacy, SCCs plus TIA, or BCRs. Transfers to the US can use the EU-US Data Privacy Framework if the recipient is certified. |
| India | DPDP Act 2023 and DPDP Rules | Transfers are generally allowed unless the government restricts a destination. Sector rules, such as payments data localization, can be stricter. Obligations phase in over a transition period. |
| Saudi Arabia | PDPL | Transfers to countries with adequate protection, or under approved safeguards such as standard clauses issued by SDAIA. Risk assessments may be required. |
| UAE | Federal PDPL; DIFC and ADGM have their own regimes | Adequacy-style and contractual routes. Which regime applies depends on where the employing entity is registered. |
| Brazil | LGPD | ANPD's standard contractual clauses, which must be adopted without alteration, or other approved mechanisms. |
| China | PIPL | CAC security assessment, standard contract filing, or certification, with separate consent and an impact assessment. Transfers strictly necessary for HR management under labor rules are generally exempt from the filing routes. |
Fix: Add a column to your data map for each jurisdiction's mechanism. For employee data under India's DPDP Act, follow government notifications on restricted destinations and check whether your payroll provider falls under sector rules. In China, don't assume the HR exemption covers everything. Data that isn't strictly needed for HR management, such as analytics exports or engagement surveys, may still trigger a filing.
Lawful basis and data minimization: the problems start at onboarding
Mistake 3: Relying on employee consent
A broad privacy consent signed at onboarding feels safe. Under GDPR it's usually the weakest basis you can pick. Regulators take the view that employees can't freely refuse their employer, so consent in that setting is suspect, and it can be withdrawn at any time. Better bases for most HR processing are the employment contract, legal obligations and legitimate interests. India's DPDP Act takes a similar line, treating employment purposes as a "legitimate use" that needs no consent. China is the exception: PIPL requires separate consent for some processing, including cross-border transfers that don't fall under an exemption.
Fix: Build a processing register that assigns a lawful basis to each purpose (payroll, benefits, performance, monitoring). Use consent only where local law requires it or where the processing is truly optional, like a voluntary wellness program.
Mistake 4: Collecting everything because the form has a field for it
EOR and HRIS onboarding templates are often built for the strictest country on the vendor's list. So a new hire in Kenya gets asked for marital status, religion and dependants' passport numbers. Some of those fields are legitimate in particular places. Germany's church tax depends on religious affiliation, for example. Collected everywhere by default, they're over-collection, and some are special-category data with tighter rules.
Fix: Ask the vendor for country-specific onboarding field sets and switch off anything local legal or payroll rules don't require. Keep health, biometric and religious data out of the core HRIS where you can, and restrict access with roles.
Vendor contracts: sub-processors and DPA terms that don't hold up
Mistake 5: Not looking at the sub-processor chain
An EOR advertising coverage in 100-plus countries rarely owns an entity in all of them. In many markets it works through in-country partners, and those partners use their own payroll software, banks and accountants. Each is a sub-processor holding your employees' salary and identity data. Many buyers never ask for the list.
Fix: Request the full sub-processor list by country, including in-country partners. Check that the DPA gives advance notice of changes (14 to 30 days is common) and a right to object. For your high-headcount countries, ask whether the vendor owns the entity or uses a partner, and how it audits that partner.
Mistake 6: Signing a DPA nobody negotiated
Standard vendor DPAs tend to favor the vendor. Watch for these:
- Breach notification "without undue delay" with no hour limit. GDPR gives controllers 72 hours to notify the regulator, so you need the vendor to tell you well inside that, ideally within 24 to 48 hours.
- Audit rights limited to a SOC 2 or ISO 27001 report, with no follow-up questions or on-site review after an incident.
- A liability cap for data breaches set at the same low level as the general cap, often 12 months of fees.
- No commitment to help you answer employee access or deletion requests within legal deadlines.
Fix: Negotiate a separate, higher data-protection cap, a fixed notification window, and help with data subject requests. Mid-market buyers often get these terms simply by asking, especially at renewal or once headcount passes roughly 50.
Residency and retention: where data sits and how long it stays
Mistake 7: Thinking data residency settles the transfer question
Many vendors sell HRIS data residency, meaning hosting in the EU, India or the Gulf, often only on enterprise tiers. It's useful, but hosting location and access location aren't the same. If support engineers in another country can see records, most regimes count that remote access as a transfer. Residency also doesn't help when data must leave the region for a real reason, such as payroll for an employee on assignment abroad.
Fix: Ask where data is stored, where backups sit, and which countries support and engineering staff log in from. Ask whether access is controlled per region; "follow-the-sun" support often isn't. Pay for residency where a law or a major customer contract requires it, not to make a slide deck look better.
Mistake 8: Never deleting anything
Leavers' records sit in the HRIS, the EOR portal, the payroll provider and a stack of spreadsheet exports for years. Retention periods vary by country, and payroll and tax records often must be kept for several years, sometimes a decade. Applicant data and performance notes usually have far shorter justifiable periods. Switching vendors makes it worse: the old vendor keeps a full copy unless you get a deletion certificate.
Fix: Write a retention schedule by data category and country and automate deletion where the system allows. Add a clause to every vendor contract requiring return or deletion within a set period after termination (30 to 90 days is common), confirmed in writing.
Questions to ask vendors and what the fixes typically cost
Send these to every HRIS, EOR and payroll vendor during evaluation or at renewal, and insist on written answers:
- What transfer mechanism do you use for each region we operate in, and can we see the signed clauses and your TIA template?
- Can we have your complete sub-processor list by country, including in-country EOR partners?
- Where is data hosted and backed up, and which countries can support staff access it from?
- Do you have country-specific onboarding field sets, and can we turn fields off?
- What's your contractual breach notification window, in hours?
- How do you support China PIPL filings, Brazil's ANPD clauses and Saudi PDPL transfer requirements?
- What happens to our data at contract end, and do you issue a deletion certificate?
On budget, these are typical 2026 market ranges. They vary by contract and region, so confirm with your vendors and advisors:
| Item | Indicative cost (USD) |
|---|---|
| External counsel review of one vendor DPA | $1,500 to $8,000 |
| Transfer impact assessment per destination | $1,000 to $5,000, or internal time using a template |
| China standard contract filing support | $5,000 to $25,000 |
| HRIS data residency add-on or enterprise tier uplift | Often 10% to 30% above standard pricing |
| Privacy management software (data mapping, registers) | $5,000 to $40,000 per year |
This article explains how these regimes generally work. It isn't legal advice. Have licensed privacy counsel in your key jurisdictions sign off on your transfer mechanisms and retention schedule.
Start here: rank your countries by headcount multiplied by data sensitivity, and work through all eight fixes for the top three. If a vendor can't answer questions 1, 2 and 5 in writing within two weeks, mark it down in your scoring, whatever its price.
Quick answers
Do we need Standard Contractual Clauses if our HRIS vendor is based in the US?
Not always. If the vendor is certified under the EU-US Data Privacy Framework, EU transfers to it can rely on that certification. Many companies still sign SCCs as a fallback, and SCCs can also cover the vendor's sub-processors in other countries that the framework doesn't reach. Check the vendor's current certification status and its sub-processor list.
Does India's DPDP Act require employee data to stay in India?
Generally, no. The Act permits transfers unless the government restricts a particular destination, and it treats employment purposes as a legitimate use that needs no consent. Sector regulators can be stricter, for example on payments data, so check with your payroll provider and an Indian privacy advisor. The DPDP Rules phase obligations in over a transition period, so confirm the current dates.
Is employee consent ever the right legal basis for HR data?
Sometimes, though not as the default. Under GDPR, consent works for optional processing such as voluntary wellness programs, but not for payroll or core HR, because employees can't freely refuse. China's PIPL requires separate consent in specific cases, including some cross-border transfers.
Is paying for HRIS data residency worth it?
Only when a law, a regulator or a major customer contract requires local hosting. Residency doesn't stop remote access from counting as a transfer, so you still need transfer mechanisms. For most mid-sized teams, sound SCCs, access controls and a tight DPA protect more per dollar than a residency uplift.
Who is liable if our EOR's in-country partner has a data breach?
In most regimes you stay accountable to employees and regulators as the controller, even when the breach happened at a sub-processor. What you can recover from the EOR depends on the DPA's liability cap and indemnity terms. That's why a separate, higher data-protection cap is worth negotiating.
Written by the Borderless Base Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.