UK Data Residency: What the Law Requires of Brokers

UK Data Residency: What the Law Requires of Brokers

UK data residency means client data is stored and processed on servers physically located in the United Kingdom. UK law does not impose a general rule that personal data must stay in the UK. It does require that any transfer abroad has a legal gateway. For a mortgage broker, UK-only storage is therefore a risk and trust decision, and a clear way to show clients and lenders where their documents sit.

TL;DR

  • Data residency is where data is physically held. Data sovereignty is about which laws apply to it and who can compel access.
  • UK GDPR and the Data Protection Act 2018 do not require UK-only storage, but they restrict transfers to organisations outside the UK unless a legal gateway applies.
  • A restricted transfer can happen through remote access, not only through storage, so the provider's location and support model matter.
  • A residency claim is only complete if it covers backups, sub-processors and staff access.
  • Brokers collect bank statements, payslips and ID, so UK-only handling shortens due diligence and simplifies client conversations.

Table of Contents

What data residency means, and how it differs from data sovereignty

Data residency is the country or region where an organisation chooses to store its data. Oracle describes it as primarily a location and storage decision. It is not, by itself, a statement that the law demands that location.

Data sovereignty is a different question. It concerns the legal authority of a state over data within its jurisdiction. The governing law can depend on where data is stored or processed, and more than one jurisdiction may be involved. IBM puts the contrast simply: residency is physical location, sovereignty is the legal authority of the country where the data is generated or processed.

The practical consequence is that a UK data centre does not settle everything. If the provider is a company with overseas ownership or overseas support staff, the legal exposure and the access paths can still reach beyond the UK. Brokers should ask about both location and control.

What UK law actually requires

No general UK-only storage rule

There is no general requirement under UK GDPR or the Data Protection Act 2018 to store or process personal data only in the UK. Flosum's guide summarises the position this way: the rules focus on safeguards for international transfers, wherever the infrastructure is located. Government guidance on public sector cloud takes a similar line: there is no universal requirement for OFFICIAL data to sit in the UK, provided legal and security safeguards are satisfactory.

Where UK GDPR applies

The UK GDPR applies to processing in the context of a UK establishment, wherever the processing takes place. It also covers relevant processing by non-UK organisations that offer goods or services to people in the UK. A UK mortgage broker handling UK clients is within scope whichever cloud it uses.

Off-shoring personal data needs a gateway under Article 44 of the UK GDPR: an adequacy decision, the International Data Transfer Agreement (IDTA), or binding corporate rules, as set out in PPN 020. The UK has granted adequacy to several countries, including EU and EEA members, so data can flow to them without extra mechanisms.

The ICO's brief guide to international transfers, updated 15 January 2026, states that every restricted transfer must be covered by adequacy regulations, appropriate safeguards or a legal exception. If none applies, the transfer must not be made.

The two standard safeguards the ICO has issued are the IDTA and the UK Addendum to the EU standard contractual clauses. Where either is used, the parties must also complete a transfer risk assessment, as the ICO explains in its guidance on standard data protection clauses.

Three legal routes for restricted UK data transfers

Why storage location is only half the question

The ICO's guide to international transfers frames the test as whether personal information is sent or made accessible to a separate organisation outside the UK. Two points follow.

  1. Access counts. A restricted transfer arises not only when data is sent but also when it is made accessible, for example by remote administrative access given to an organisation based outside the UK.
  2. Hosting in the UK does not cure an overseas provider. If the UK GDPR applies and the provider is a separate organisation based outside the UK, the ICO says the transfer is restricted even if the data is hosted on UK servers.

For a broker, this means a platform's data centre address is not enough. The location of the provider's support staff, its sub-processors and any offshore data handling all feed into the compliance picture.

Why brokers care about UK-only handling

A mortgage file is dense with personal and financial data: bank statements, payslips, tax forms, identity documents and proof of address. Each is a document type a broker is expected to verify and keep with care. Three things make UK-only handling attractive even where the law does not demand it.

  • Simpler transfer analysis. Fewer overseas parties means fewer IDTAs, addenda and transfer risk assessments to complete and maintain.
  • Clearer answers to clients. Applicants increasingly ask where their payslips and statements are held. "In the UK, handled by UK-based staff" is a short and credible reply.
  • Easier due diligence. Networks, lenders and professional indemnity insurers ask about outsourcing. A single-jurisdiction supply chain shortens the questionnaire.

The same logic applies across wider financial work. Where brokers arrange finance for clients based overseas, the paperwork brings its own tax and anti-money-laundering checks, as this article on nonresident developer finance shows. It is another reason to keep the document trail in one jurisdiction with a clear audit record.

Five checks before you trust a residency claim

A residency claim that ignores backup regions and sub-processors is incomplete, as Workato's buyer's guide observes. Use these five checks with any document platform.

  1. Primary storage. Confirm the country and the hosting arrangement for live data, including uploaded documents and extracted data.
  2. Backups and disaster recovery. Ask where replicas are held and whether failover can move data to another country.
  3. Sub-processors. Request the list. Each one that touches client data needs a place in your transfer analysis.
  4. Staff and support access. Establish who can view or administer data, and from where. Remote access from outside the UK can be a restricted transfer.
  5. Contract. An Article 28 compliant contract with a processor is a mandatory foundation for outsourcing, wherever the processor sits. It should also record the residency commitments in writing.

Before adopting a new tool, a privacy impact assessment is the natural place to record these answers. Pair it with role-based access so that only people who need a file can open it, and keep a clear audit trail for every change through document version control.

Who regulates this

The Information Commissioner's Office is the UK's independent data protection regulator. It advises UK data controllers on compliance, including the legal bases for international transfers. Its transfer guidance is the document to read first when you assess any supplier with a link outside the UK.

Our perspective

We built Casefile on the view that a broker should be able to answer the residency question in one sentence. Documents collected from clients are held in the UK, with no manual or offshore data handling.

The law does not demand UK-only storage, and we do not claim it does. Our reasoning is practical. Every overseas party in a supply chain adds a contract, a risk assessment and a question from a lender or client. Removing them leaves the broker with less to document and less to explain.

Residency alone is not enough, so we pair it with clear audit trails and automatic cross-checks that highlight issues, such as undeclared commitments or mismatched wage deposits, before they become lender queries. The platform carries the brokerage's own branding, so clients see a familiar, straightforward upload experience.

Our advice to any broker: ask every supplier about backups, sub-processors and support access, get the answers in the contract, and prefer a setup that keeps client data in the UK from collection to approval.

Darren

How Casefile keeps client documents in the UK

Casefile is a cloud-based platform for UK mortgage brokers that automates document collection, cross-checks bank statements, payslips, tax forms, ID and utility bills, and flags discrepancies before they reach a lender. It is designed around UK-only data residency and preserves applicant privacy, while giving you an approval queue and your own branding.

See how Casefile handles your documents for the data security detail, or visit Casefile to see the platform.

Gocasefile

The checks that matter most to residency also sit inside everyday verification work: identity document verification, proof of address, income verification and source of funds documents. More guidance is on the Casefile blog.

FAQ

Not as a general rule. UK GDPR and the Data Protection Act 2018 do not require personal data to be stored only in the UK. They do require a legal gateway, such as an adequacy decision or the IDTA, for restricted transfers to organisations outside the UK.

What is the difference between data residency and data sovereignty in the UK?

Residency is the physical location where data is held. Sovereignty is about the legal authority over that data, including which country's laws apply and who can compel access. A UK data centre run by an overseas provider can satisfy the first without fully answering the second.

Does using a UK server avoid international transfer rules?

Not always. The ICO says that if the provider is a separate organisation based outside the UK, the transfer is restricted even when the data sits on UK servers. Remote access from abroad can also count as a transfer.

Who should a broker ask about transfer rules?

Start with the ICO's international transfer guidance, then your compliance lead or data protection adviser. Ask suppliers for their sub-processor list, backup locations and support access arrangements in writing.

Sources

This article was generated with AI, and whilst it is our expectation that the article is accurate, it should not be taken as advice.