)
Last updated: November 11, 2026
Does a UK data residency AI gateway keep personal data in the United Kingdom just because a vendor names a region? Not by itself. UK GDPR looks at who you contract with and who can access prompts, logs, and embeddings, not only where the servers sit.
TL;DR: Key Takeaways
- The ICO's three-step test, updated on 15 January 2026, decides whether a transfer is restricted. UK GDPR must apply, you initiate a transfer to an organisation outside the UK, and that organisation is a separate legal entity.
- According to the ICO (2026), transfer status is not based on the geographical location of the servers. A contract with a non-UK entity can still be a restricted transfer even if the servers are in the UK.
- The data protection test arrived with the Data (Use and Access) Act 2025. In force from 5 February 2026, it requires that protection after a transfer is "not materially lower" than in the UK.
- The European Commission, on 19 December 2025, renewed UK adequacy decisions, with a sunset until 27 December 2031.
- The NCSC (2023) advises you to know where AI assets reside, including models, prompts, logs, and assessments, and to treat logs as sensitive data.
At a glance: UK data residency AI gateway questions
Quick Answer
What should you ask about a UK data residency AI gateway?
Ask who the contracting entity is, which countries store and process each data type, who can remotely access the system, and what safeguard covers any restricted transfer. Server location alone does not answer the ICO's three-step test. Map prompts, logs, embeddings, and tool payloads separately.
| Buyer question | Why it matters | What "good" looks like |
|---|---|---|
| Which legal entity do we contract with? | The ICO test follows the entity, not the rack. | A named entity, plus sub-processors. |
| Where is each data type stored and processed? | Prompts, logs, embeddings, and backups often live apart. | A country list. |
| Who can access the data, including support staff? | Making data accessible is a transfer, even without a copy leaving the UK. | Named regions, approval, and time-bound access. |
| What safeguard covers any restricted transfer? | Adequacy, Article 46 plus the data protection test, or a narrow Article 49 exception. | A written basis, plus the test for Article 46. |
How we compared
We reviewed ICO transfer guidance (15 January 2026), the ICO statement of 5 February 2026, and the Commission renewal of 19 December 2025.
What UK GDPR tests, and what it does not
UK GDPR regulates restricted transfers of personal data, not a blanket duty to keep every byte on UK soil. According to ICO (2026), if all three steps of the test are yes, the transfer rules apply and you need a lawful basis.
A transfer includes sending personal data and making it accessible, including by remote access. Transit through another country is not, by itself, a restricted transfer, but you still need security in transit. The ICO is explicit on hosting: location inside the same legal entity is not a restricted transfer if you own the servers. A UK provider is not a restricted transfer just because its servers sit abroad; a non-UK provider is, even if the servers are in the UK.
A "UK region" in a marketing deck does not settle the test if the contracting entity is overseas. For the definitions, see Data Sovereignty vs Data Residency vs Data Localization.
)
Questions to ask about prompts, logs, and embeddings
An AI gateway can inspect prompts, completions, tool calls, embeddings, caches, and traces, and any of those may hold personal data or secrets. According to ICO (2026), you should record where personal data moves and delete intermediate files when they are no longer required.
| Data type | Stored where? | Processed where? | Retention | Training use? | Who can read it? |
|---|---|---|---|---|---|
| Prompts and completions | Country or customer premises | Country or in-memory only | Hours, days, or term | Yes, no, or written opt-out | Support, ops, subprocessors |
| Gateway logs and traces | Same or another region | Same or a SIEM | Default and maximum | Usually no; confirm | SOC, vendor engineering |
| Embeddings and caches | Same or a vector store | Same | Time-to-live | Confirm | Same |
| Tool payloads and files | Same | Same, plus tools | Same | Confirm | Same, plus owners |
If the vendor cannot fill the row, treat that as a finding. Also ask whether caches can be rebuilt without holding raw prompts. Article 5(1)(c) of UK GDPR still requires data minimisation when you use AI.
Contracts, access, and your UK data residency AI gateway risk
Ask which legal entity you will sign with, and whether it is in the UK. Ask how the provider moves data to its "global network of processors", the ICO's phrase for large cloud groups, and which subsidiary sits on your order form.
If a restricted transfer is not covered by UK adequacy regulations, you need Article 46 safeguards, such as the IDTA or the UK Addendum, and a transfer risk assessment. The ICO (2026) states that this is now the "data protection test". You must decide, acting reasonably and proportionately, that protection is not materially lower than in the UK. According to ICO statement (2026), those provisions came into force on 5 February 2026.
For UK-to-US flows, the UK Extension to the EU-US Data Privacy Framework (the UK-US data bridge) can provide adequacy if the provider is DPF-certified for it. The regulations were made on 20 September 2023 and came into force on 12 October 2023. Supporting documents are published by DSIT.
Adequacy is not a substitute for knowing your own flows. According to European Commission (2025), UK adequacy was renewed on 19 December 2025, with a sunset on 27 December 2031 and a review after four years. That decision covers EEA-to-UK flows, not other third-country flows unless a separate route, such as the UK Extension, applies.
Support access, subprocessors, and failover
Ask who can open a ticket and see a prompt. Remote support from outside the UK can be a restricted transfer, because the ICO treats making data accessible as a transfer. Require named support regions, approved access, and an exportable log.
Ask for a current sub-processor list, including model and storage vendors, and notice before a new one is added. A UK-preferred region that silently fails over to another country is a change of processing, not a footnote.
According to NCSC Guidelines (2023), you should know where assets reside and accept the associated risks. The NCSC Principle 2 guidance (2018, reviewed 2023) asks for the countries where data is stored, processed, and managed, including support locations.
Security and governance: residency gaps that leak data
Prompt injection, data leakage, and tool misuse do not wait for a transfer opinion. A gateway that stores prompts in a UK region but lets an injected instruction send them out through a tool is still a confidentiality failure. Logs and embeddings can extend the same risk.
You need one enforcement point, redaction before storage, scoped identities, and audit evidence a DPO can use. Agent Gateway (TrustGate) runs traffic to models and tools through one control layer. Public pages state US and EU data residency for SaaS, with split-plane, privately hosted, and on-premises options so data can stay in your perimeter. There is no advertised UK-hosted managed region. Teams that need UK-held data should assess those options, then complete the ICO's entity and access questions.
Which should you choose?
Pick the pattern you can evidence in a contract and in a proof of concept, not the label closest to "UK". Residency, the contracting entity, and model-provider flows are three different questions. A good buy answers all three in writing.
| Situation | Residency pattern to test | Transfer work still needed | Fit |
|---|---|---|---|
| You can accept EU-hosted data | EU region or data plane, with a country list | Confirm the entity and onward transfers | Fastest managed path |
| You want UK-held data | Customer-hosted data plane or UK on-premises | Still test support and model-provider flows | Stronger location control |
| You send data to a US model API | The model call may still be a restricted transfer | Adequacy via the UK Extension if the provider is DPF-certified for it; otherwise Article 46 safeguards plus the data protection test, or do not send the data | Minimise or redact first |
| Dual UK and EU group | Separate routing and records | UK rules one way, EU adequacy the other | One memo does not cover both |
Conclusion
A UK data residency AI gateway is only as strong as the answers you get. Who is the contracting entity? Where are prompts, logs, embeddings, and tool payloads stored and processed? Who can access them, including support staff? What safeguard and data protection test cover any restricted transfer? Server location is only part of the UK GDPR test. Get those answers in writing and test them in a PoC.
Secure AI Gateway Data Flows for UK Buyers in Production with NeuralTrust
Book a demo to review deployment options and the evidence your DPO will ask for.
)
Related Comparisons
- Data Sovereignty vs Data Residency vs Data Localization
- UK Data Residency: Which AI Security Vendors Offer It?
- What Is an AI Gateway?
- GDPR and AI: A UK CISO Guide
FAQs about UK Data Residency AI Gateway
1. Does UK GDPR require a UK data residency AI gateway?
No. UK GDPR does not impose a general duty to store all personal data in the United Kingdom. It regulates restricted transfers. You may still choose UK residency for policy or contracts, but that adds to the transfer test and does not replace it.
2. If the servers are in the UK, is the transfer question closed?
No. According to ICO (2026), a contract with a provider established outside the UK is a restricted transfer even if the servers are in the UK. A UK provider is not a restricted transfer solely because its servers are abroad. Always identify the contracting entity.
3. Does EU adequacy for the UK solve UK-to-US gateway traffic?
No. According to European Commission (2025), EEA-to-UK adequacy runs until 27 December 2031 and covers flows into the UK from the EEA. It does not, by itself, authorise UK-to-US transfers through a model API. For those flows, use the UK Extension if the provider is DPF-certified for it; otherwise Article 46 safeguards plus the data protection test, or do not send the data.
4. What is the data protection test for gateway transfers?
If you rely on Article 46 safeguards, such as the IDTA or the UK Addendum, you must complete a transfer risk assessment. The ICO now calls this a data protection test. Protection must not be materially lower than in the UK. Those Act provisions came into force on 5 February 2026.
5. Are gateway logs in scope for residency talks?
Yes. The NCSC (2023) tells you to treat logs as sensitive data and to know where AI assets reside. Logs often hold prompts and identifiers. Ask where they are stored, who can query them, how long they are kept, and whether they leave your region.
6. Can a vendor's "UK office" stand in for UK data residency?
No. An office address is not a hosting region and is not the contracting entity. Ask for the legal entity on the order form, the countries used for storage, processing, and support, and written notice of changes. Then check those answers in a PoC.
About the Author
Roger Howroyd is Head of Global SEO and AI at NeuralTrust, where he leads the company's search strategy across SEO, AEO, GEO, and LLM optimisation. He specialises in AI-powered search, content strategy, and SEM. Connect on LinkedIn.
NeuralTrust is the leading platform for securing and scaling AI agents. Named a Pioneer in the Gartner Emerging Market Quadrant for AI Application Security 2026, recognised across four Gartner Hype Cycle reports in 2026, and featured in the Gartner Market Guide for Guardian Agents 2026, the Gartner Market Guide for AI Gateways 2025 and the KuppingerCole Leadership Compass for Generative AI Defense 2025. Headquartered in Barcelona with offices in London and New York. ISO 27001 certified.
Sources
- ICO, A guide to international transfers, 15 January 2026.
- ICO, Are we making a restricted transfer?, three-step test, 2026.
- ICO, What's a transfer risk assessment (TRA)?, 15 January 2026, updated November 2026.
- ICO, Statement on DUAA commencement, 5 February 2026.
- The Data (Use and Access) Act 2025 (Commencement No. 6 and Transitional and Saving Provisions) Regulations 2026, legislation.gov.uk, made 29 January 2026; s. 85 and Sch. 7 in force 5 February 2026.
- European Commission, UK adequacy renewal, 19 December 2025, sunset 27 December 2031.
- NCSC, Guidelines for secure AI system development, 27 November 2023; Cloud Security Principle 2, 2018, reviewed 2023.
- ICO, How should we assess security and data minimisation in AI?, Article 5(1)(c), 11 November 2026.
- UK-US data bridge: The Data Protection (Adequacy) (United States of America) Regulations 2023, made 20 September 2023, in force 12 October 2023. ICO, How does the UK Extension to the EU-US Data Privacy Framework work?, 11 November 2026. DSIT, UK-US data bridge: supporting documents, 21 September 2023.
- NeuralTrust, AI Gateway and Pricing, 11 November 2026.
)
)
)
)