Cross-border transfers in 2026: adequacy, clauses, impact assessments and localization

Most transfers are not decisions. They are a support tool with a log viewer, an analytics vendor, a developer in another country or a cloud region someone picked by default. The law then asks what mechanism covers each one.

Key points

  • A cross-border transfer is personal data sent to, or made accessible from, another country, and under the UK GDPR the rules apply even to small or infrequent transfers and are the responsibility of the organization that starts the transfer.
  • The usual order of questions is adequacy first, then a safeguard such as the standard contractual clauses with an assessment of the destination’s law, and only if neither fits, one of the narrow exceptions.
  • As of November 2026 the European Commission’s adequacy page includes the United Kingdom, whose decisions it renewed in December 2025, Brazil, with mutual decisions adopted in January 2026, and the United States for commercial organizations participating in the EU-US Data Privacy Framework, adopted on 10 July 2023.
  • Localization is a different rule from transfer restriction: it requires certain data to be stored or first recorded in the country, so no transfer mechanism can substitute for the local database.

Adequacy lists and transfer rules change. This page is a map, dated November 2026, and your counsel confirms the current position before a contract or a configuration is fixed to it.

Step one: find the transfers

A cross-border transfer is personal data sent to, or made accessible from, another country, and under the UK GDPR the rules apply even to small or infrequent transfers and are the responsibility of the organization that starts the transfer. The ICO’s international transfers guide, published in January 2026, sets out a three-step test for whether a transfer is a restricted one, and notes that the organization starting the transfer is responsible for complying whatever its place in the processing chain.

Practically, a transfer is wherever a person or system outside the country can read the data: the vendor’s hosting region, its support staff, its sub-processors, and your own staff abroad with remote access. Data mapping finds the first group; the vendor questionnaire finds the rest. The result is a transfer register: flow, destination, vendor and mechanism.

Step two: pick the mechanism, in order

The usual order of questions is adequacy first, then a safeguard such as the standard contractual clauses with an assessment of the destination’s law, and only if neither fits, one of the narrow exceptions.

  1. Adequacy. The destination, or the specific scheme, has been found adequate. The ICO describes adequacy as the most efficient route, and no further safeguard is needed, though other checks continue to apply. The current list is on the Commission’s adequacy decisions page, which is the only reliable place to check it.
  2. An appropriate safeguard. For the EU GDPR, the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 of 4 June 2021, published on EUR-Lex. For the UK, the International Data Transfer Agreement or the Addendum to the EU clauses, in force since 21 March 2022, or binding corporate rules.
  3. An exception. Narrow derogations apply only where neither of the above covers the transfer. The ICO’s words are that if you cannot identify an appropriate exception, you must not make the transfer.

What the adequacy list says now

As of November 2026 the European Commission’s adequacy page includes the United Kingdom, whose decisions it renewed in December 2025, Brazil, with mutual decisions adopted in January 2026, and the United States for commercial organizations participating in the EU-US Data Privacy Framework, adopted on 10 July 2023.

Two qualifiers matter. The Commission’s list marks Canada as covering commercial organizations only, and the United States as covering organizations that participate in the Data Privacy Framework. A US vendor that is not on the framework’s list is not covered by that decision, and then the clauses are the usual route. Ask each vendor which route it relies on, in writing, and keep the answer in the register. For the Canadian side, see Canadian data residency for SaaS.

Step three: assess the destination, then record it

A transfer impact assessment records the transfer facts, the destination’s law and practice that bear on it, and any extra measures, so you can show the protection is not materially lower after the transfer. The ICO calls its version a transfer risk assessment and requires it when you rely on a safeguard; the EU clauses ask the parties to assess whether the destination’s law allows the clauses to be followed. The European Data Protection Board’s Recommendations 01/2020 on measures that supplement transfer tools, final version adopted on 18 June 2021, are the usual reference when extra measures are considered.

A workable assessment is short. It states what data goes, to whom and for what, which law in the destination might reach it, what the vendor commits to if that happens, what technical measures reduce exposure (for example, encryption with keys the vendor does not hold), and who accepted the residual risk. The legal conclusions are your counsel’s; we draft from the facts.

Localization is a separate question

Localization is a different rule from transfer restriction: it requires certain data to be stored or first recorded in the country, so no transfer mechanism can substitute for the local database.

China’s Personal Information Protection Law, for example, requires critical information infrastructure operators, and handlers processing personal information in volumes set by the national cyberspace authority, to store personal information collected and produced in China within China (Article 40). The same law sets several routes for transfers abroad, including a security assessment and a standard contract; an English translation is held by DigiChina. India’s Digital Personal Data Protection Act, 2023 may also apply to your data. We do not summarize these regimes’ detailed duties here, because they are amended often.

Transfer rules and localization rules A comparison of two kinds of rule. Transfer rules restrict sending data out and are met with a mechanism per transfer. Localization rules require data to be stored in the country and are met by where the data sits. Transfer rules Localizationrules Limit sending dataout Require data storedin-country Met by a mechanism Met by where datasits Adequacy, clauses,UK agreement Local database, perthe law Checked per transfer Checked per system
A transfer mechanism cannot replace a local database where localization applies.

A short checklist for 2026

  • Is every vendor’s hosting region and support location in the register?
  • For each flow, is the mechanism named, and is it still current?
  • For each safeguard, is there a written assessment, and who accepted the residual risk?
  • Does any law require data to stay in-country, and where does that data actually sit?
  • Does the vendor contract tell you when the vendor changes sub-processors or hosting region?

The vendor side is in vendor privacy reviews that scale. The service is described on cross-border transfers and data localization.

How the work is bounded

The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.

SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.

Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.

Questions we are asked

What counts as a cross-border transfer?

A cross-border transfer is personal data sent to, or made accessible from, another country, and under the UK GDPR the rules apply even to small or infrequent transfers and are the responsibility of the organization that starts the transfer.

In what order are the options considered?

The usual order of questions is adequacy first, then a safeguard such as the standard contractual clauses with an assessment of the destination’s law, and only if neither fits, one of the narrow exceptions.

What is the state of adequacy decisions?

As of November 2026 the European Commission’s adequacy page includes the United Kingdom, whose decisions it renewed in December 2025, Brazil, with mutual decisions adopted in January 2026, and the United States for commercial organizations participating in the EU-US Data Privacy Framework, adopted on 10 July 2023.

What is a transfer impact assessment?

A transfer impact assessment records the transfer facts, the destination’s law and practice that bear on it, and any extra measures, so you can show the protection is not materially lower after the transfer.

How is localization different?

Localization is a different rule from transfer restriction: it requires certain data to be stored or first recorded in the country, so no transfer mechanism can substitute for the local database.

Map your transfers

List the countries your customers are in and where your vendors host. The reply says what a transfer review would cover. The service is cross-border transfers and data localization.

Discuss a scope