Where Subprocessors Process Data: Locations and Transfers

Data residency subprocessors are the location cells on a vendor's list. What a named country, a transfer and a 'Various' row each require, and how to check.

By The ClauseTrail team 9 min read

Data residency subprocessors are a location question: where a vendor says each subprocessor processes personal data. The location cell on the subprocessor list is the vendor’s answer. A hosting-region control in the product is a different promise, and it does not name the companies on the list or the countries those rows give.

What the location cell is, and is not

Data residency is the other phrase people reach for. It means where data is physically stored and processed, as chosen by a customer or promised by a vendor, such as EU-only hosting. A row on a subprocessor list is narrower and more useful. It is one company, one purpose, and the place or places the vendor states for that processing.

Those are different facts, and teams mix them up. EU hosting for the application can sit next to a support subprocessor in Colombia and a cloud row in the United States. The hosting promise never mentioned either row. If the only record you keep is “EU region”, the list will surprise you.

Article 28 of the GDPR does not require the list to name a country. It requires prior authorisation before a processor engages another processor and, where that authorisation is general, information about intended additions or replacements “thereby giving the controller the opportunity to object”. The country matters for a different chapter. Chapter V restricts transfers of personal data to a third country or an international organisation. A new name on the list is an Article 28 event. A place outside the EEA is a transfer question on top of it. What controllers have to do with that chain is the subject of our note on GDPR subprocessors. What the word subprocessor covers is in the guide to what a subprocessor is.

The list is still the vendor’s statement, not a map of every server. Read it as a claim you can check against the data processing agreement, not as a traceroute.

What data residency subprocessors show on a real list

Stripe’s list is a clear worked example because it uses several kinds of location cell at once. As of our check on 15 November 2026, Stripe’s subprocessor list (the page Stripe publishes at stripe.com/legal/service-providers) includes:

  • Amazon Web Services, Inc., purpose “Cloud service provider”, location United States.
  • Support rows with countries attached: TELUS International (Cda) in Ireland, Teleperformance Colombia S.A.S. in Colombia, TDCX (MY) SDN. BHD. in Malaysia, and Cognizant Worldwide Limited in the Philippines and India.
  • Two rows that name a function rather than a company, “User and Sales support service providers” and “Verification service providers”, each with the location “Various”.

“Various” is not a country. It does not tell you whether the transfer stays inside the EEA, whether an adequacy decision applies, or which safeguard the data processing agreement would have to carry. Treat it as not stated, and ask the vendor which entities and which countries sit behind it. The same goes for “Global”, for “Customer Selectable” with no menu attached, and for a blank cell.

One Stripe row is a different kind of location fact. The purpose text for Stripe India Private Limited says that, in order to meet regulatory data localization requirements for Indian payment transactions, Stripe India Private Limited stores certain data on servers located in India. That is a legal requirement the vendor is describing, not a region you picked in a settings page. Data residency (the promise or the choice) and data localization (a rule that data stay in a country) answer different questions. The list can contain both, and only the words in the row tell you which one you are looking at.

A city is not always a new country. “San Francisco, CA” and “United States” can be the same claim written twice. “Ireland” and “Dublin, Ireland” likewise. When you compare two versions of a list, read the words before you treat a location edit as a move.

When the place is a transfer

A location inside the EEA is not a Chapter V transfer. A location outside it might be, and the mechanism depends on the country, not on a single clause you can paste into every file.

An adequacy decision, under Article 45, lets the transfer proceed without the extra safeguard in Article 46. The Commission’s list of adequacy decisions, as we read it on 16 November 2026, includes the United Kingdom and Switzerland, and it does not include the United States as a country. For the UK, the finding in force is the decision of 19 December 2025 amending Implementing Decision (EU) 2021/1772. The Commission renewed the 2021 finding until 27 December 2031. The text is the renewal decision (C(2025) 8771). A UK row is still a transfer out of the EEA. It is not, on that decision, a transfer that needs standard contractual clauses.

The United States is the case people under-read. Adequacy there covers organisations that certify to the EU–US Data Privacy Framework, under Implementing Decision (EU) 2023/1795, not every company with a US address. Where there is no adequacy decision to rely on, Article 46 requires appropriate safeguards. For a SaaS vendor that usually means standard contractual clauses (Implementing Decision (EU) 2021/914) and the transfer impact assessment that goes with them. How the clauses differ from the framework is set out in our guide to standard contractual clauses and the EU–US Data Privacy Framework. What to do on the day a row leaves the EEA is the transfer impact assessment note, which this one does not repeat.

Two checks follow from that, and neither is optional just because the vendor is well known.

First, the country in the cell has to match a mechanism in the DPA on file. A US row with only a UK adequacy recital in the DPA is a gap. A UK row does not become an SCC problem because the country is outside the EEA. Open the DPA and see which tool it actually names for that destination.

Second, a cell you cannot place is not a cell you can bless. “Various”, “Global”, a region nickname the list does not decode, or no location at all: write “not stated”, and do not invent the country from the company’s headquarters. A company’s registered office is not the processing location unless the row says so.

Your record of processing activities has to be able to name recipients in third countries. When the list adds a place, the record is part of the same check. That bookkeeping is covered from the controller’s side in the GDPR subprocessors note. Do not keep a second, vaguer list of “regions we use” that drifts away from the vendor’s rows.

What to do, by the person who has to do it

The data protection officer owns the transfer tool and the record. For each non-EEA country, name the mechanism (adequacy, including the UK renewal, the Data Privacy Framework for a certified US organisation, or standard contractual clauses) and the date you last matched it to the row. If the cell does not state a country, the record should say that, not a guess.

Security review owns the entity and the purpose. A new country for the same support purpose is a different question from a new purpose that sends customer content to a model provider. The location cell will not tell you which. Read the purpose beside it.

Procurement owns the clock in the DPA on file. Article 28 gives the opportunity to object. It does not give a number of days. The days, the grounds, and whether notice is an email you have to subscribe to, are contract terms. If the DPA on file is silent, that is a negotiation point, not a hidden GDPR default. Vendor privacy monitoring is the daily read of those documents. It does not object for you, and it does not decide that a country is acceptable.

The one check worth making this week

Pick one vendor whose product you have set to an EU region. Open its current subprocessor list and find three cells: a named country outside the EEA, a cell that says “Various”, “Global” or nothing, and the matching wording in the DPA on file. Write down, for each, the country or “not stated”, and the transfer tool the DPA actually names. If the region setting and the list disagree, the list is the one that names the subprocessors. Fix the record before you add another vendor to the same habit.

Data residency subprocessors are checked one row at a time. A dashboard that says “EU” has not done that check.

We re-read the subprocessor list and the DPA of each vendor you track, and keep the previous version beside the new one, so a location edit is a diff rather than a rumour. The current lists we publish are in the vendor directory. Which documents that covers is on vendor privacy monitoring.

Frequently Asked Questions

What are data residency subprocessors?

They are the subprocessors on a vendor’s list, read for where the vendor says they process personal data. The location cell is the vendor’s statement. It is not the same fact as a hosting region you selected, and it is not a legal finding that the country is adequate.

Does the GDPR require a subprocessor list to name a country?

No. Article 28 requires authorisation and, for general authorisation, notice of intended changes so the controller can object. It does not set the fields of a public list. The country becomes your problem under Chapter V when the processing is a transfer to a third country, and under Article 30 when your records have to name recipients in third countries.

Is a United States subprocessor always an SCC transfer?

No. A transfer to a US organisation certified under the EU–US Data Privacy Framework can rely on the Commission’s adequacy decision (Implementing Decision (EU) 2023/1795). A US organisation that is not covered needs another mechanism, usually standard contractual clauses. The row’s country does not tell you which applies: the DPA on file, and the certification, do.

What should I do if the location says Global, Various, or nothing?

Treat the place as not stated. Do not substitute the vendor’s headquarters or the region in your admin settings. Ask which legal entities process the data and in which countries, and until you have that, record the gap. A transfer tool cannot be matched to a country the list does not give.

If our tenant is hosted in the EU, can subprocessors still be elsewhere?

Yes. EU hosting describes where that vendor keeps the service you configured. Subprocessors are other companies, with their own locations, and the list is where those locations are stated. Support, email, analytics and model providers on the same list are often outside the EEA even when the application region is not.

Written from the primary sources as they stood on 17 November 2026. General information, not legal advice.

ClauseTrail watches vendors' subprocessor lists, DPAs, privacy policies, terms and AI terms, and tells your team what changed and by when to object.