Data protection

Suppliers storing data outside the UK: what to check

What a practice must check when a supplier stores or accesses patient data outside the UK: approved countries, safeguards and the data protection test.

Ava research teamPublished 6 min read

On this page
  1. When your data leaves the UK
  2. The routes a transfer can use
  3. The data protection test
  4. Transfers to the United States
  5. Common scenarios
  6. What to ask a supplier
  7. Red flags in supplier answers
  8. Telling patients
  9. Example: a transcription tool for a dental group
  10. Keep the paperwork light but complete
  11. Frequently asked questions
  12. References

Key takeaways

  • A transfer happens whenever patient data is stored in, or accessed from, another country, including remote support from abroad.
  • Transfers can rely on a country approved by UK regulations, or on appropriate safeguards such as standard data protection clauses.
  • Since February 2026, safeguards must pass a data protection test: protection after transfer must not be materially lower than in the UK.
  • The UK-US data bridge only covers US organisations certified to the UK Extension of the Data Privacy Framework, so check the certification.

When your data leaves the UK

Practices rarely decide to send patient data abroad. It happens because a supplier hosts in another country, uses a cloud region outside the UK, has a support team in another time zone, or relies on a sub-processor elsewhere. Each of these is a restricted transfer under UK GDPR if personal data is made available to a person in another country, and health data is special category data with the highest level of protection[1].

Clinicians are wary of this for good reason. Among GPs who do not yet use AI tools, 89% were concerned about professional liability and medico-legal issues and 88% about a lack of regulatory oversight[2], while 82% were worried about patient privacy and data security[3]. Where a supplier processes data, and under whose law, is part of that worry.

Concerns among GPs not using AI tools, 2025Nuffield Trust and RCGP survey
Concerns among GPs not using AI tools, 2025Bar chart. Professional liability and medico-legal issues: 89%; Lack of regulatory oversight: 88%; Patient privacy and data security: 82%.Professional liability and medico-legal issuesProfessional liability and medico-legal issues: 89%89%Lack of regulatory oversightLack of regulatory oversight: 88%88%Patient privacy and data securityPatient privacy and data security: 82%82%Concerns among GPs not using AI tools, 2025Bar chart. Professional liability and medico-legal issues: 89%; Lack of regulatory oversight: 88%; Patient privacy and data security: 82%.Professional liability and medico-legalissuesProfessional liability and medico-legal issues: 89%89%Lack of regulatory oversightLack of regulatory oversight: 88%88%Patient privacy and data securityPatient privacy and data security: 82%82%

Source: Nuffield Trust, 2025[2]

Show the data
ItemValue
Professional liability and medico-legal issues89%
Lack of regulatory oversight88%
Patient privacy and data security82%

The routes a transfer can use

Before a transfer, you need a lawful route. In practice there are three for practices and their suppliers.

  1. Approved countries: the UK government can approve a country, territory or sector by regulations, after which transfers there need no further safeguards. The European Economic Area is approved, which covers many cloud regions.
  2. Appropriate safeguards: a transfer can rely on safeguards such as standard data protection clauses specified in regulations or issued by the regulator, binding corporate rules, or an approved certification mechanism with binding commitments[4]. In practice the International Data Transfer Agreement, or the UK Addendum to the EU's standard clauses, are the tools most suppliers use.
  3. Exceptions: narrow derogations, such as explicit consent for a particular transfer, exist for occasional cases but are not a basis for routine supplier processing.

Rule of thumb: if a supplier says data is ‘GDPR compliant’ but cannot tell you which route it uses for each country, keep asking.

The data protection test

The Data (Use and Access) Act 2025 rewrote the safeguards rule from 5 February 2026. A transfer made under safeguards is only lawful if the controller or processor, acting reasonably and proportionately, considers that the data protection test is met[4]. The test is met if, after the transfer, the protection for the individual would not be materially lower than the standard under UK data protection law, and what is reasonable and proportionate depends on all the circumstances, including the nature and volume of the data[4].

For a practice, that means the supplier's transfer assessment should consider the kind of data involved. Appointment metadata for a booking tool is very different from call recordings, transcripts or clinical images. Ask the supplier for its assessment, read it, and record your own conclusion.

Transfers to the United States

Many software and AI suppliers are American or use American cloud providers. The UK-US data bridge came into effect on 12 October 2023 and covers transfers only to US organisations that participate in the UK Extension to the EU-US Data Privacy Framework[5]. A US company that has not certified, or has certified without the UK Extension, is not covered and needs another route, usually standard data protection clauses.

Check certification on the official Data Privacy Framework list, confirm the UK Extension is included, and check that the certification covers the type of data concerned, including health data where relevant. Recheck at renewal, because certifications lapse.

Common scenarios

Typical supplier arrangements and the transfer route each is likely to rely on.
ScenarioLikely routeWhat to check
Cloud hosting in an EU regionApproved country (EEA)Region locked in the contract; support access locations
US software company, UK Extension certifiedUK-US data bridgeCertification current and covers the data
US company without UK ExtensionStandard data protection clauses plus assessmentSigned clauses and transfer assessment
Support team in a non-approved country with remote accessStandard clauses plus assessmentAccess controls, logging, what support staff can see
Transcription or AI engine operated by a sub-processor abroadDepends on countrySub-processor list, data retention, use for model training
Backups replicated to another countryDepends on countryBackup location in the contract

What to ask a supplier

  1. Where is the data?

    Ask for every country where data is stored, processed or backed up, and every country from which staff or sub-processors can access it.

  2. Which route, for each country?

    Approved country, data bridge, standard clauses or another safeguard. Get the documents for each.

  3. What is in the transfer assessment?

    Ask for the supplier's assessment of the data protection test, covering the data types you will send.

  4. How are instructions limited?

    The processing contract must require the processor to act only on your documented instructions, including on transfers[6]. Check the clause exists and covers sub-processors.

  5. What changes will you be told about?

    New sub-processors or new countries should trigger notice and a right to object.

  6. What can you lock down?

    Ask whether data can be kept in UK or EEA regions only, and whether that is a contractual commitment.

Red flags in supplier answers

  • ‘Our data centres are in the UK’, with no mention of where support staff or sub-processors sit.
  • A sub-processor list that the supplier can change at any time without telling you.
  • Terms that allow the supplier or its partners to use recordings, transcripts or images to train their own models.
  • A reference to the data bridge from a US company that cannot show certification to the UK Extension.
  • Standard clauses offered with no transfer assessment, or an assessment that ignores the type of data involved.
  • No commitment to tell you if a government authority requests access to your data, where the law allows it.

None of these automatically rules a supplier out, but each needs a clear written answer before you rely on the service for patient data.

Telling patients

Your privacy notice should say, in plain words, that some suppliers may store or process data outside the UK, how that data is protected, and how patients can find out more. You do not need to list every sub-processor, but you should be able to answer a patient who asks where their call recording or online form is held. Patients increasingly ask that question about AI tools in particular, and a confident, specific answer builds trust far better than a generic line about compliance. Keep a short internal note of the main suppliers, countries and routes so reception and managers can answer consistently, and update the notice when a new supplier or a new country is added.

Example: a transcription tool for a dental group

Example: a fictional group of three dental practices wants to trial an AI note-taking tool. The supplier is a UK company, but its transcription runs through a sub-processor in the United States and support is provided from another country. The operations manager asks for the sub-processor list, finds the US sub-processor certified to the Data Privacy Framework with the UK Extension, and confirms the support team's access is covered by standard clauses with a transfer assessment.

Example: the assessment does not say whether recordings are kept after transcription. The supplier confirms deletion after processing and puts it in the contract. The group records the routes, the assessment and the retention commitment in its impact assessment and supplier register before the trial starts.

Keep the paperwork light but complete

Most practices do not need a legal team for this. They need a consistent set of questions, the supplier's answers in writing, and a short record of the decision. Add a line to your supplier register for data locations and transfer routes, and revisit it whenever the supplier changes sub-processors or you add a new type of data, such as recordings or images.

  • Supplier name and service.
  • Countries where data is stored, processed, backed up or accessed.
  • Route for each country and the document that evidences it.
  • Whether the data protection test has been assessed, by whom and when.
  • Any restrictions agreed, such as UK-only storage or deletion after processing.

See also data processing agreements, AI tools and patient data, clinical photographs stored in cloud imaging, choosing private clinic software and identity checks on calls, which matter more when phones are answered by a supplier's service.

Frequently asked questions

Is cloud storage in the EU a problem?

Usually not. The EEA is approved for transfers from the UK, so the main checks are that the region is fixed in the contract and where support staff access the data from.

Can we use a US supplier?

Yes, if the transfer has a lawful route: the UK-US data bridge for organisations certified to the UK Extension[5], or safeguards such as standard data protection clauses that pass the data protection test[4].

What is the data protection test?

A check, made reasonably and proportionately, that protection after the transfer would not be materially lower than under UK data protection law[4].

Does remote IT support from abroad count as a transfer?

Yes, if support staff can access personal data from outside the UK. It needs a route and should be covered in the processing contract.

References

  1. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑

  2. Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑

  3. Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑

  4. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 46: Transfers subject to appropriate safeguards (opens in a new tab) ↑

  5. GOV.UK (Department for Science, Innovation and Technology) (2023). UK-US data bridge: supporting documents (opens in a new tab) ↑

  6. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 28: Processor (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo