This article is stated as at 22 November 2026. The ICO has said it plans to update the IDTA and the Addendum and to publish further guidance on transfer risk assessments and cloud services, and the list of adequacy regulations can change. Take advice on your own circumstances before acting.
Where any part of an AI tool’s supply chain sits outside the UK, the rules on UK GDPR international transfers decide whether client data can go there. The ICO calls this a restricted transfer, and it needs one of three things: UK adequacy regulations covering the destination, a safeguard such as the IDTA or the UK Addendum backed by a transfer risk assessment, or one of a narrow set of exceptions. Since 5 February 2026 the test is whether protection after the transfer is “not materially lower” than in the UK.
When does an AI tool make a UK GDPR international transfer?
The ICO describes transfers of personal information to separate organisations outside the UK as restricted transfers, and it sets a three step test. All three steps must be met:
- the UK GDPR applies to the processing;
- you are initiating the transfer of personal information to an organisation outside the UK; and
- the receiver is a separate legal entity from you.
A set of accounts carries more personal data than people tend to assume: directors’ names and addresses, payroll, directors’ loan account movements and the related party notes. So the first step is usually met as soon as a working file goes into a tool.
A transfer also need not involve sending anything. The ICO says “A transfer isn’t just about sending personal information. It can also mean making personal information accessible.” Its own example is an Indian IT support company reaching UK servers over a VPN, which is a restricted transfer. Your own employees working from abroad do not create one, because they are part of the same legal entity, but a contractor who is a separate sole trader does.
Take a hypothetical practice that contracts with a UK company for an AI drafting tool. The tool calls a model hosted in the United States, and out of hours support is run by a contractor abroad with remote access. Both can be restricted transfers, and the UK contracting entity tells you nothing about either until you ask.
Who initiates the transfer, and who has to comply?
The ICO says “you’re only responsible for complying with the UK GDPR transfer rules if your organisation initiates restricted transfers”. Initiating means making the initial decision that causes the transfer, which is different from authorising it. Its rule of thumb is that “you’re not initiating the transfer if you didn’t design the transfer structure or architecture, nor initially chose the receiver.”
In an AI supply chain that gives two common patterns.
| Arrangement (UK-wide, current ICO guidance) | Who initiates | Who completes the TRA |
|---|---|---|
| Practice uses a UK processor, which passes data to its own subprocessor outside the UK | The UK processor, with the controller’s authorisation | Only the processor |
| Practice chooses its own processor outside the UK, even if a UK processor sends the files | The practice as controller | The practice |
The second row follows the ICO’s own example of a UK controller that instructs its UK processor to send files to a Mexican processor.
Even where the supplier carries the obligation, the practice still authorises the transfer, and a partner should be able to show that the authorisation was informed. In practice that means asking every AI supplier for its subprocessor list, the transfer mechanism it relies on for each subprocessor outside the UK, and confirmation that it has completed a transfer risk assessment. Our list of questions to ask an AI supplier covers these, and the wider picture sits in our guide to client data, UK GDPR and AI tools.
Is the destination covered by UK adequacy regulations?
Adequacy regulations list the countries, territories, sectors and international organisations the UK government has assessed as giving protection “not materially lower” than UK law (the ICO notes this was previously described as “sufficiently similar”). Where a transfer is covered, the ICO says you don’t need a transfer risk assessment or appropriate safeguards.
| Destination (UK adequacy, as listed by the ICO at 22 November 2026) | Coverage |
|---|---|
| EEA countries (EU member states plus Iceland, Norway and Liechtenstein) and EU or EEA institutions, bodies, offices and agencies | Full |
| Andorra, Argentina, Faroe Islands, Gibraltar, Guernsey, Isle of Man, Israel, Jersey, New Zealand, Switzerland, Uruguay | Full, carried over from EU decisions made before 2021 |
| Canada | Partial, PIPEDA only |
| Japan | Partial, APPI PIHBOs only |
| Republic of Korea | Full (SI 2022/1213) |
| United States | Partial, UK Extension to the Data Privacy Framework only (SI 2023/1028) |
The United States entry causes the most trouble, because so many model providers are American. US adequacy only covers personal information transferred under the UK Extension to the EU-US Data Privacy Framework. The recipient must be on the Data Privacy Framework list, must have self-certified to the UK Extension, and its certification must cover the type of data you are sending. A provider on the list that has not opted into the UK Extension is not covered. The ICO adds that the UK Extension is a separate arrangement that would not automatically fall if the EU arrangement were invalidated.
Check the ICO’s adequacy page at the point you rely on it (it was last updated on 5 November 2026) and keep a note of what you saw and when.
The IDTA and the UK Addendum
Where adequacy does not apply, the usual route is an appropriate safeguard. The ICO lists its standard data protection clauses, the International Data Transfer Agreement (IDTA) and the International Data Transfer Addendum (the Addendum), together with binding corporate rules.
The Addendum attaches to the EU standard contractual clauses issued by the European Commission on 4 June 2021. Many suppliers’ data processing agreements are built on those EU clauses, and the ICO is clear that “The EU SCCs are not valid on their own for restricted transfers under the UK GDPR.” If the agreement you have been sent mentions the EU clauses and says nothing about the UK, ask for the Addendum.
Only minor amendments are allowed to the mandatory clauses (Part 4 of the IDTA, Part 2 of the Addendum), in the circumstances set out in Part 4 Section 5 of the IDTA and Sections 16 and 17 of Part 2 of the Addendum, and you must not make any change that reduces the level of protection. A supplier’s lawyers sometimes rework these clauses to fit their standard terms, and a heavily edited version may no longer work as a safeguard. For significant changes, the parties can ask the ICO to approve the amended document specifically.
The ICO said in its guidance that it plans to update the IDTA and the Addendum during 2026 and that you should continue to use the current versions. Both let the parties choose automatic updating when a new version is issued (IDTA Section 5.4 and Addendum Section 18). Selecting that option, or diarising a review, keeps your supplier contracts in step with the new versions.
UK GDPR international transfers and the transfer risk assessment after the DUAA
Section 85 of the Data (Use and Access) Act 2025, with Schedules 7 to 9, came into force on 5 February 2026 under regulation 2 of SI 2026/82. Protection after transfer must now be “not materially lower” than under the UK GDPR and the Data Protection Act 2018, replacing the earlier wording that protection must be “not undermined”. The sender must decide, acting reasonably and proportionately, that the standard is met.
The legislation now calls this assessment a “data protection test”, though the ICO still says transfer risk assessment, or TRA. Two points from the ICO’s TRA guidance matter most for practices. If you plan to use a safeguard, you must complete a TRA first. And a TRA completed under ICO guidance before the transfer provisions came into force on 5 February 2026, which concluded that protection was sufficient, has met the data protection test, so there is no need to redo it for that reason alone.
The ICO accepts three ways of completing a TRA: its own optional TRA tool, the European Data Protection Board’s approach, or the UK government’s published analysis where one exists. The tool works through the circumstances of the transfer, the risk to the information and enforceability in the destination, and its suggested harm scores for categories of data are only a suggestion.
For ongoing transfers the ICO says an annual check of the TRA is proportionate unless the information is particularly high risk. That review sits naturally alongside the ISQM 1 annual evaluation. While you are there, check that your data protection policy and engagement letters use the “not materially lower” wording rather than “not undermined” or “essential equivalence”.
The TRA answers a narrower question than a data protection impact assessment, and a new AI tool may need both. Our note on when a practice needs a DPIA covers the second.
Why consent and the other exceptions rarely fit an AI tool
Article 49 of the UK GDPR lists a set of exceptions, including explicit consent that is specific and informed about the transfer, necessity for a contract with the person, legal claims, and a single transfer necessary for compelling legitimate interests.
The ICO says that where transfers are regular and predictable, or systematic, you are less likely to be able to show an exception is necessary and proportionate, and a tool used on every set of accounts is about as systematic as it gets. The compelling legitimate interests exception is narrower still: the transfer must not be part of a repetitive pattern, you must be unable to use any safeguard, you must inform the ICO and you must record the transfer in full. Consent also brings a practical problem, since the data subjects are often directors and employees of the client who never signed your letter.
Treat the exceptions as a route for the unusual case, and keep your lawful basis for processing as a separate question: having one does not authorise the transfer.
Key dates
| Date | What happened or is expected (UK-wide) |
|---|---|
| 21 March 2022 | IDTA and Addendum come into force |
| 21 March 2024 | Old EU standard clause contracts had to be replaced with the IDTA or the Addendum |
| 5 February 2026 | DUAA section 85 and Schedules 7 to 9 in force, with the “not materially lower” test |
| During 2026 (announced) | ICO plans updated IDTA and Addendum; use current versions until then |
| Spring 2027 (announced) | ICO expects updated guidance on controller and processor contracts and liabilities |
For most practices the work is an annual cycle: get each AI supplier’s subprocessor list, confirm the mechanism for every destination outside the UK, hold the supplier’s confirmation of its TRA (or complete your own where you initiate), and check the position again a year later. The judgement on whether a supplier’s answers are good enough still belongs to the partner who signs off the practice’s approach.
Questions practices ask
Is our AI supplier's data processing agreement enough, or do we also need an IDTA?
A data processing agreement sets the processor terms but does not on its own cover a restricted transfer. If the destination is not covered by UK adequacy regulations, a safeguard such as the IDTA or the UK Addendum is needed. Many agreements already include the EU standard contractual clauses, which the ICO says are not valid alone for UK transfers, so check the UK Addendum is attached.
Our AI tool is run by a UK company but uses a US model provider. Is that an international transfer?
It can be. Passing data to a separate company outside the UK is a restricted transfer even when your contract is with a UK entity. Where the UK supplier chose the US provider as its subprocessor, the ICO treats the supplier as initiating the transfer with your authorisation, so the supplier completes the TRA. Ask which mechanism covers that US provider.
Do we need to sign a new IDTA when the ICO publishes a new version?
The ICO has said it plans to update the IDTA and the Addendum and that you should keep using the current versions until then. Both documents let the parties choose to update automatically when a new version is issued, under IDTA Section 5.4 and Addendum Section 18. If that option was not selected, diarise a review so your contracts follow the new versions.
Does a member of staff working from abroad create a restricted transfer?
Not if they are your employee. The ICO says employees of the same legal entity working abroad do not create a restricted transfer, because the receiver is not a separate organisation. A contractor working as a separate sole trader outside the UK is different: giving them access to client data, even remotely, is a restricted transfer that needs adequacy, a safeguard or an exception.
Should an acquirer check a target practice's international transfers?
Yes, as part of reviewing the target's technology suppliers. Ask for its list of AI and software suppliers, each supplier's subprocessors outside the UK, the transfer mechanism relied on for each, and the TRAs on file with the date each was last reviewed. Gaps are better found before completion than after.
Sources
- The Data (Use and Access) Act 2025 (Commencement No. 6 and Transitional and Saving Provisions) Regulations 2026
- Data (Use and Access) Act 2025, section 85
- Data Use and Access Act 2025: plans for commencement
- Are we making a restricted transfer?
- How do we comply with the transfer rules if we're initiating the restricted transfer?
- Adequacy regulations
- Is the restricted transfer covered by adequacy regulations?
- How does the UK Extension to the EU-US Data Privacy Framework work?
- What are the rules on appropriate safeguards?
- What are standard data protection clauses (the UK IDTA and the Addendum)?
- Standard Data Protection Clauses to be issued by the Commissioner under S119A(1) Data Protection Act 2018: transitional provisions (In force 21 March 2022)
- What's a transfer risk assessment (TRA)?
- Completing a TRA
- The ICO's TRA tool
- Using an exception
- What are the exceptions?
- Updated guidance on international transfers published
- Our plans for new and updated guidance: general data protection