A London SaaS company should map people, legal entities, systems, access and subprocessors before selecting any transfer clause. The first question is not whether the servers are in Europe or America. It is which organisation controls or processes which personal data, which separate overseas organisation can access it, who initiates that access and which law applies.
- OverviewA London SaaS company should map people, legal entities, systems, access and subprocessors before selecting any transfer clause.
- Draw the service as legal entities and access pathsCreate one row for every system used to deliver, support, secure, analyse and sell the service.
- Separate UK, EEA and customer rolesA UK SaaS provider may act as controller for account, billing, marketing and employment data while acting as processor for customer content.
- Test US recipients against the actual mechanismThe UK Extension to the EU-US Data Privacy Framework is a partial UK adequacy arrangement for eligible US organisations.
- Complete the data protection test and technical controlsWhen relying on appropriate safeguards, the business must assess whether protection after transfer is not materially lower.
A London SaaS company should map people, legal entities, systems, access and subprocessors before selecting any transfer clause. The first question is not whether the servers are in Europe or America. It is which organisation controls or processes which personal data, which separate overseas organisation can access it, who initiates that access and which law applies.
After the map is accurate, classify each restricted transfer. Use applicable adequacy regulations where they cover the recipient and data, or put an appropriate safeguard and required assessment in place. Keep controller and processor contracts, security measures, subprocessor approvals and privacy information aligned with the same map.
Draw the service as legal entities and access paths
Create one row for every system used to deliver, support, secure, analyse and sell the service. Record the contracting entity, hosting region, support locations, administrators, subprocessors, data categories, people affected, retention and deletion route. Include ticketing, product analytics, email, identity, logging, backups, customer success and payment systems, not only the core database.
The ICO's international-transfer test treats making data accessible to a separate overseas organisation as potentially relevant. Remote support from the United States can therefore matter even when production data is stored in London. A group company is also a separate legal entity.
For each arrow on the map, name the sender, receiver and organisation that initiates the transfer. Record whether the receiving party is a controller, processor or subprocessor. A diagram labelled simply "cloud" or "EU" is not sufficient for contract review.
Separate UK, EEA and customer roles
A UK SaaS provider may act as controller for account, billing, marketing and employment data while acting as processor for customer content. Its EEA customer may be the controller, and the SaaS provider may appoint UK, EEA and US subprocessors. Each relationship needs its own role analysis.
The European Commission renewed the EU adequacy decisions for the United Kingdom in December 2025. That supports covered EEA-to-UK flows, but it does not automatically cover the UK provider's onward transfer to a US subprocessor. The EU customer still needs accurate subprocessor information and the contractual chain required by the EU GDPR.
Do not assume the customer initiates every transfer because it uploads data. ICO guidance on who makes a restricted transfer explains how responsibility can sit with a processor that designs and appoints its own overseas subprocessor network.
Test US recipients against the actual mechanism
The UK Extension to the EU-US Data Privacy Framework is a partial UK adequacy arrangement for eligible US organisations. The ICO says a UK exporter relying on it must check that the recipient has active status, participates in the UK Extension and covers the relevant data type. The ICO's UK Extension guidance also identifies limits and extra steps for certain sensitive data.
Verify the organisation on the official Data Privacy Framework list, not a sales page or old certificate. Record the check date and the exact US legal entity. A global supplier may contract through one entity while support or analytics is supplied by another.
If the UK Extension does not cover the recipient or data, assess an appropriate safeguard. The ICO guidance on the UK IDTA and Addendum explains that EU standard contractual clauses alone are not valid for a UK restricted transfer, while the UK Addendum can be used with those clauses. Use the current approved text and complete the parties, modules and annex information accurately.
Complete the data protection test and technical controls
When relying on appropriate safeguards, the business must assess whether protection after transfer is not materially lower. The ICO continues to call this a transfer risk assessment in its guidance, although UK legislation now uses the term data protection test. Its 2026 assessment guidance describes a reasonable and proportionate analysis of the recipient, destination and transfer circumstances.
Contract wording is only one control. Assess encryption in transit and at rest, key control, access approval, logging, support tooling, data minimisation, pseudonymisation, deletion, government-request handling and the ability to challenge access. Match extra measures to the mapped data and threat rather than copying a generic security schedule.
If the assessment finds the safeguard cannot provide sufficient protection and no effective extra measure is available, do not proceed on that safeguard. An exceptional derogation should not become the default architecture for a routine SaaS service.
Govern subprocessors as a living register
Maintain a register with legal name, location, function, data, transfer role, mechanism, assessment date, contract owner and exit plan. Link it to procurement so that a team cannot add a tool processing customer data without review. Link it to engineering so that changes in hosting, support or telemetry update the map.
Controller customers often expect prior notice and an objection process for new subprocessors. The SaaS company needs a release process that can meet those promises. It should also confirm that processor-to-subprocessor contracts carry the required data-protection obligations and authorisation.
The planned article on AI adoption in London professional services is relevant because AI tools often introduce new access, retention and subprocessor paths. The transfer review belongs before a production upload, not after a customer asks about it.
Turn the map into enterprise-sales evidence
Enterprise customers need consistent answers. Prepare a controlled pack containing the architecture diagram, roles, data locations, subprocessor list, transfer mechanisms, assessment summary, security controls, retention schedule, incident route and signed data-processing terms. State the evidence date and owner.
Do not promise that data "never leaves the UK" if overseas support, security monitoring or group access remains possible. Distinguish storage location from remote access and onward processing. Accurate limitations build more trust than an absolute claim the technical design cannot support.
The guide to how London professional-services firms sell expertise overseas addresses market entry. For SaaS, the transfer map is part of that commercial readiness because it can shorten security and legal review only when it matches reality.
Maintain a decision register
For every transfer, record:
- Sender, receiver and initiator.
- Controller, processor and subprocessor roles.
- Data categories, people and purpose.
- Storage, access and support locations.
- Adequacy or safeguard relied on.
- Assessment and extra measures where required.
- Contract and subprocessor approval.
- Review trigger and owner.
- Customer notice obligations.
- Termination and deletion route.
The evidence should also support supplier sustainability and governance questionnaires discussed in the 2026 UK sustainability-reporting guide, without mixing environmental data with privacy compliance.
Limitations
International-transfer analysis depends on the legal entities, roles, data and architecture in a specific service. UK, EU and US rules and adequacy findings can change. This article is an operational framework, not legal advice, and it does not approve a transfer. Sources were checked on 13 October 2026. A qualified adviser should review the actual map and contracts before restricted transfers begin.
Reporting by Shoreditch Talk




