Nov 28, Paris: AI Health Hack #2 with Alan, Qovery and AWS. Applications close Nov 21

Beyond "hosted in an EU region": the data residency checklist a European fintech should run on any cloud platform

An EU region only answers where your primary data sits. Here are the 12 checks a European fintech should run on a cloud platform's residency claims, from backups, logs, telemetry, support access and AI features to key custody, the CLOUD Act, the DORA register of information and exit, with what AWS, Microsoft and Google actually publish.

Morgan Perry
Co-founder
NOV 19, 2026 · 20 MIN
Beyond "hosted in an EU region": the data residency checklist a European fintech should run on any cloud platform

Key points:

  • An EU region answers one question out of about twelve. It tells you where primary data rests. It says nothing about backups, logs, telemetry, support access, AI features, the provider's control plane, sub-processors, who holds the encryption keys or which law can compel the provider.
  • Every hyperscaler's EU commitment has published exceptions. Microsoft documents transfers for global security operations, remote engineer access and directory data; AWS keeps content in your region except where "necessary to comply with the law or a binding order of a governmental body"; Google's EU package excludes data in transit to its own MCP servers. Read each provider's exceptions page before its landing page.
  • DORA turns residency into a contract clause and a register entry. Article 30(2)(b) requires the regions or countries where data is processed and stored, with advance notice of any change, and Article 28 requires a register of information and a tested exit strategy for critical or important functions.
  • Collect a contractual commitment and a technical control for each check. The contract says what the provider promises; region-blocking policies and customer-held keys decide what can physically happen.
  • Keep the platform layer from becoming the leak. With Qovery, your apps, databases, volumes and backups run in your own cloud account and region. Qovery's control plane runs on AWS and processes deployment metadata (configuration state, resource metrics and deploy events), so it belongs on your sub-processor list, with its region confirmed in your DPA.

Qovery · Infrastructure control plane
Agent actions, policy-checked before they run
Learn more

Every fintech procurement deck I have reviewed in the last two years has the same slide: a map of Europe, a pin on Frankfurt or Paris, and "your data stays in the EU". Then an auditor or a bank partner asks where the backups replicate to, who at the provider can open a support session, and which law applies if a US court sends a warrant. The slide has no answer.

I am Morgan, co-founder of Qovery, and I spend a lot of time with CTOs and compliance leads at European fintechs. This is the checklist we walk through together, with what AWS, Microsoft and Google publish, quoted from their own pages.

Demand for these answers keeps rising. Gartner forecasts worldwide sovereign cloud IaaS spending of $80 billion in 2026, up 35.6% on 2025, and expects Europe to overtake North America in that spending in 2027 (Gartner).

For the GDPR mechanics on Kubernetes, see our EU data residency guide for Kubernetes. For choosing a cloud under DORA, see how EU fintech teams should choose a cloud platform for DORA.

Why is "hosted in an EU region" not enough for a European fintech?

"Hosted in an EU region" only guarantees the location of the primary copy of the data you put into a regional service. A fintech's data also lives in replicas, backups, logs, monitoring pipelines, support tickets, AI prompts and the provider's own control plane, and each of those can sit in a different country under a different legal entity.

Three forces make this a fintech problem rather than a generic privacy one:

  • DORA makes location a contractual term. Article 30(2)(b) of DORA requires every ICT contract to state "the locations, namely the regions or countries, where the contracted or subcontracted functions and ICT services are to be provided and where data is to be processed, including the storage location", plus a duty for the provider "to notify the financial entity in advance if it envisages changing such locations" (Regulation (EU) 2022/2554).
  • Supervisors now oversee the hyperscalers directly. On 18 November 2025 the European Supervisory Authorities designated 19 critical ICT third-party providers, including AWS, Google Cloud and Microsoft (EBA). Your supervisor will compare your register against what those providers declare.
  • Banking partners inherit the EBA outsourcing guidelines. Paragraph 75 of the EBA Guidelines on outsourcing arrangements (EBA/GL/2019/02) asks critical or important outsourcing contracts to state where the service is performed and "where the relevant data will be kept and processed, including the possible storage location" (EBA). The record must name a country or region, not a data center address (Pinsent Masons).

So the question to ask a cloud platform is "where does each category of my data go, who can reach it, and what stops it from moving", and the answer has to fit in your register of information.

What are the 12 checks, and what evidence should you ask for?

Run these 12 checks on every provider in the chain: the hyperscaler, the deployment platform, the observability SaaS and the AI vendor. For each one, collect a contractual commitment and a technical control. A provider can change a control in its next release unless the contract commits to it, and a contract alone cannot stop a misconfigured backup.

#CheckThe question to askContractual evidenceTechnical control you can verify
1Data at restWhich regions hold primary data and every replica?Region list in the DPA or service termsOrg policy that blocks resource creation outside EU regions
2Data in transitCan traffic route outside the EU between EU endpoints?Network transit clausePrivate connectivity, TLS everywhere, EU-only endpoints
3Backups and DRWhere do snapshots, cross-region copies and DR replicas go?Backup location named per serviceBackup vault policies pinned to EU regions
4LogsWhere do audit, access and application logs land?Log storage location per serviceLog sinks and buckets created in EU locations
5Telemetry and metadataDo resource names, tags, metrics and billing data leave the EU?Definition of "customer data" vs "configuration data"Naming rules that keep personal data out of names and tags
6Support accessWho can open a session on your data, from where?Support location and personnel commitmentsAccess approval workflow (Lockbox, Access Approval) with logs
7AI featuresWhere do prompts, embeddings and model outputs get processed?AI-specific residency termsFeature disabled by policy, or EU-pinned endpoints
8Control planeWhere does the provider's management plane store your config and identities?Control plane region in the DPASeparate sovereign partition, or a platform that keeps workloads in your account
9Sub-processorsWho else touches the data, and in which country?Published sub-processor list with notice periodChange notifications wired to your vendor review
10KeysWho generates, holds and can use the encryption keys?Key custody termsCustomer-managed or external keys, with access justification logs
11Foreign law exposureCan a non-EU authority compel the provider?Government request policy, transparency reportKeys outside the provider, or a provider with no non-EU parent
12DORA register and exitIs every location in the register, and can you leave?DORA addendum, exit assistance clauseA dated exit test on a second target

Where do data at rest, data in transit and backups actually go?

Data at rest stays in the EU only if every service you use is regional and pinned by policy, because global and multi-region services can store copies elsewhere by design. Check each service separately.

At rest. Ask for the list of services that are regional, and the list that is global. On Azure, Microsoft says regional services deployed in an EU Data Boundary region are in scope, while non-regional services each need their own configuration (Microsoft Learn). On Google Cloud, the EU Data Boundary with Access Justifications control package sets the gcp.resourceLocations organization policy to EU regions only and warns that "changing this value by making it less restrictive potentially undermines data residency" (Google Cloud). On AWS, the equivalent is a service control policy on aws:RequestedRegion, which you write yourself.

In transit. Ask whether traffic between two EU endpoints can leave the EU. Microsoft is explicit: "Microsoft uses variable network paths that may occasionally result in routing of customer traffic outside of the EU Data Boundary" (Microsoft Learn). Encryption in transit is the control that makes this acceptable.

Backups and DR. Backups break residency most often, because cross-region copies get turned on under incident pressure. Ask for the backup location per managed database, object store and volume, and keep the DR region in the EU: a Frankfurt primary with a Virginia replica is a cross-border transfer the day you enable it.

Do logs, telemetry and resource metadata leave the EU?

Often, yes. Most providers draw a line between "customer data", which they commit to keep in the EU, and configuration or operational data, which they may process globally. Your job is to find that line and keep personal data on the right side of it.

Microsoft's definition is the clearest example. Customer Data "doesn't include information used to configure resources in the Online Services, such as technical settings and resource names" (Microsoft Learn). Microsoft pseudonymizes personal data in system-generated logs, and still transfers some of it: pseudonymized personal data processed for security purposes "is transferred to any Azure region worldwide", and Microsoft "may replicate limited Microsoft Entra directory data from Microsoft Entra (including username and email address) outside the EU Data Boundary" (Microsoft Learn).

AWS addressed the metadata question with a separate partition. For the AWS European Sovereign Cloud, which reached general availability on 15 January 2026 with its first region in Brandenburg, Germany, AWS says customers can "keep all metadata they create (such as the roles, permissions, resource labels, and configurations)" in the EU, with its own IAM, billing and usage metering systems (Amazon). That commitment applies to the sovereign partition, not to the standard Frankfurt or Paris regions.

Never put personal data in names, tags or labels: a bucket called customer-jean-dupont-kyc turns configuration data into personal data that may be processed outside the EU. And trace your own telemetry, because your APM, error tracker and CI runners are often the first non-EU processors in the chain.

Who can access your data through support, and from where?

Support access is a transfer even when no byte leaves an EU data center. Microsoft puts it in writing: when personnel outside the boundary access data stored inside it, this is "considered a transfer of data under European privacy law although the data remains within Microsoft datacenter infrastructure in the EU Data Boundary" (Microsoft Learn).

Ask four questions about support:

  1. Is there default access to customer data, or only per task? Microsoft says "there's no default access to Customer Data" and offers Customer Lockbox so personnel cannot access it without your approval (Microsoft Learn).
  2. Where do support engineers sit? Google's EU Data Boundary with Access Justifications package routes support cases "to EU personnel located in the EU" (Google Cloud). For the AWS European Sovereign Cloud, "only personnel who are EU residents, located in the EU, have control of day-to-day operations, including access to the data centres, technical support and customer service" (AWS FAQ).
  3. Where is the ticket itself stored? Microsoft documents that support case titles "may be stored in datacenters outside the EU Data Boundary", and that cases escalated to product engineers may be too (Microsoft Learn). Train your engineers to keep customer data out of ticket titles and attachments.
  4. Is every access logged where you can read it (Access Transparency, Lockbox logs, CloudTrail)?

Where do AI features process your prompts and data?

AI features are the newest residency gap, and the one most often missing from procurement questionnaires. A model call can be processed in a different country from where your data is stored, under a different sub-processor.

Microsoft's own EU Data Boundary documentation shows the pattern. When customers allow Claude models from Anthropic with Microsoft generative AI services, "Customer Data is processed by Anthropic in the United States. Customer Data continues to be stored in the EU Data Boundary", and Microsoft says those models are coming into the EU Data Boundary starting in December 2026 (Microsoft Learn). Look for that split between storage and processing in every AI feature.

Google documents a similar boundary for agent tooling: its EU Data Boundary with Access Justifications package "doesn't provide data residency controls for in-use data and in-transit data with Google Cloud MCP servers" (Google Cloud).

For each AI feature, including IDE assistants, record where inference runs, whether prompts are retained and which sub-processor runs the model. If you serve your own models, see our guide on EU-resident GPU inference for fintech and healthtech covers the architectures.

Where does the provider's control plane live, and what does it hold?

Every managed service has a control plane: the APIs, identity systems, billing and orchestration the provider runs to manage your resources. If it sits outside the EU, your identities, configuration and sometimes your secrets do too, whatever region your workloads run in.

There are three ways to answer this check:

  • Use a sovereign partition. The AWS European Sovereign Cloud is "separate and independent from our existing AWS Regions, with infrastructure located wholly within the European Union" (AWS FAQ), and is run by a new parent company incorporated in Germany with EU-citizen leadership (Amazon). Google Cloud Dedicated is operated by partners (S3NS with Thales in France, T-Systems in Germany) and designed so Google has no remote access and the partner can keep operating "for up to 12 months" if cut off from Google (Google Cloud); S3NS's PREMI3NS received ANSSI's SecNumCloud qualification on 17 December 2025 (Thales).
  • Use a regional control plane with documented exceptions. That is what the Microsoft EU Data Boundary and Google's Assured Workloads packages give you inside the public cloud.
  • Keep third-party platforms out of the data path. Any PaaS or deployment tool you add brings its own control plane. If it runs your workloads in its account, your data sits wherever that vendor runs. If it deploys into your account, it should only hold metadata, and you need to know exactly which metadata.

Ask every platform vendor where its control plane runs, what it stores (config, variables, secrets, logs, source code, build artifacts) and where builds happen.

Keep your apps and data in your own EU account.
Qovery deploys and runs your apps on Kubernetes inside your own AWS, GCP, Azure or Scaleway account, in the region you choose, with audit logs and RBAC for your DORA evidence. Talk to us about your residency and exit requirements.

Who are the sub-processors, and who holds the encryption keys?

Sub-processors and key custody decide who can read your data, so treat them as one check. A sub-processor list tells you who might touch the data; key custody tells you whether they can read it.

Sub-processors. Ask for the published list with the country of each entry, the notice period before additions and your right to object. Under DORA the subcontracting chain for critical or important functions goes into your register.

Keys. There are four levels, from weakest to strongest:

Key modelWho generates the keyWho can use it to decryptWhat it protects against
Provider-managed keysProviderProvider, automaticallyStolen disks, not the provider
Customer-managed keys in the provider's KMS (CMEK)Customer, inside the provider's KMSProvider services, on your key policyAccidental access; you can revoke
External key manager or own HSMCustomer, outside the providerProvider only on a justified, logged requestSilent access by the provider
Client-side encryptionCustomerOnly your applicationEverything except your own app

Google's External Key Management "enables customers to encrypt their data at rest with keys stored outside our cloud. It requires detailed justifications each time access to their keys is requested" (Google Cloud), and its EU Data Boundary package makes CMEK mandatory for services such as BigQuery, Cloud Storage and Spanner (Google Cloud). Microsoft announced External Key Management for Azure in June 2025, letting customers connect Azure to keys on their own HSM, on-premises or with a trusted third party (Microsoft).

External keys cost latency, availability and some managed features (Google's package disables suspending and resuming VMs, for example), so use them for the data that would hurt most if compelled.

How exposed is your data to the US CLOUD Act if it stays in an EU region?

Region does not change jurisdiction. The CLOUD Act requires a US provider to disclose data "within such provider's possession, custody, or control, regardless of whether such communication, record, or other information is located within or outside of the United States" (18 U.S.C. § 2713).

The providers say this themselves, in their own words. AWS commits that it "will not move or replicate your content outside of your chosen AWS Region(s) without your agreement, except in each case as necessary to comply with the law or a binding order of a governmental body" (AWS FAQ). On 10 June 2025, Microsoft France's legal director, asked under oath by the French Senate whether he could guarantee French citizens' data would never be transmitted to US authorities without French authorization, answered "No, I cannot guarantee it" (The Register).

The transfer framework is also still in court. The EU General Court upheld the EU-US Data Privacy Framework on 3 September 2025 in Latombe v Commission (T-553/23) (Hunton), and Philippe Latombe appealed to the Court of Justice on 31 October 2025 (C-703/25 P) (Digital Policy Alert). The Court of Justice struck down the two previous frameworks, Safe Harbor in 2015 and Privacy Shield in 2020.

My reading for a fintech: most workloads can live with a US hyperscaler in an EU region, with customer-managed or external keys for sensitive stores, a transfer impact assessment and a tested exit plan. Data where compelled disclosure is unacceptable needs a partner-operated offer, an EU-owned provider or client-side encryption. Our explainer on the four levels of EU cloud sovereignty maps which option reaches which level. Supervisors expect a documented decision for each class of data.

What do AWS, Microsoft and Google publish about their EU residency guarantees?

All three publish real commitments and real exceptions. The table below summarizes what each one states on its own pages, as of November 2026. These are published commitments that we have not audited, and the terms change often, so recheck before you sign.

CheckAWS (European Sovereign Cloud)Microsoft Azure (EU Data Boundary)Google Cloud (Data Boundary, Dedicated)
ScopeSeparate partition, first region in Brandenburg, GA 15 January 2026, more than 90 services at launchCommitment across Azure, Microsoft 365, Dynamics 365 and Power Platform in EU and EFTA countriesAssured Workloads control packages in the public cloud, plus partner-operated Dedicated and Air-Gapped offers
Metadata and control planeRoles, permissions, labels, configurations, IAM, billing and metering stay in the EUConfiguration data such as resource names is outside the "Customer Data" definitionResource location policy pinned to EU regions; Dedicated runs a separate instance
Personnel and supportEU residents located in the EU run operations and supportRemote access from outside the boundary possible under Lockbox and SAW controls; Data Guardian announced for EU-resident approvalSupport cases routed to EU personnel; Dedicated operated by the partner
KeysKMS and HSM options inside the partitionExternal Key Management announced June 2025CMEK required by the EU package; External Key Manager with Key Access Justifications
Documented exceptionsMoves content when "necessary to comply with the law or a binding order"Security operations, Entra directory data, network transit, support case titles, some AI modelsNo residency for in-use and in-transit data with Google Cloud MCP servers; several features disabled
SourceAWS FAQ, Amazon press releaseEU Data Boundary, transfersControl package, Google Cloud blog

Microsoft's exceptions page is the most useful of the three documents because it is long and specific, and a listed transfer is something you can put in a register. For a deeper look at the sovereign tiers and their price premiums, see our sovereign EU cloud region checklist.

How do residency guarantees map to the DORA register of information and exit plan?

Every answer from the 11 previous checks ends up in two DORA artefacts: the register of information and the exit strategy. If an answer cannot be written into one of them, you do not have it yet.

The register. Article 28(3) requires financial entities to "maintain and update at entity level, and at sub-consolidated and consolidated levels, a register of information in relation to all contractual arrangements on the use of ICT services provided by ICT third-party service providers" (Regulation (EU) 2022/2554). The templates are fixed by Commission Implementing Regulation (EU) 2024/2956, applicable since 17 January 2025 (EUR-Lex). Data storage and processing locations, the subcontracting chain and the criticality of each function go in there. The sub-processors behind your deployment platform, observability SaaS and AI vendor belong in it too.

The contract. For ICT services that support critical or important functions, Article 30(3)(e) requires "unrestricted rights of access, inspection and audit" for you and your competent authority, and Article 30(3)(f) requires "a mandatory adequate transition period" during which the provider keeps running the service while you migrate (Regulation (EU) 2022/2554).

The exit. Article 28(8) states: "For ICT services supporting critical or important functions, financial entities shall put in place exit strategies." Data you cannot locate is data you cannot move, and an auditor will ask for the date of your last exit test. The cheapest way to make exit credible is a portable delivery layer: the same container images, Helm charts and Terraform, deployable on a second cloud or region, so an exit test is a deployment rather than a re-architecture.

How should you weigh contractual commitments against technical controls?

Use contracts to define what the provider may do and technical controls to prove what it can do. Fintech auditors now ask for both, because a contract clause cannot stop a misconfigured backup and a policy cannot stop a court order.

RiskA contract alone gives youA technical control alone gives youWhat I would do
Data created outside the EUA breach claim after the factA blocked API call before it happensOrg policy on regions plus a region clause
Provider staff accessA promise and an audit rightAn approval log and a refusal buttonLockbox or Access Approval plus support location terms
Compelled disclosureA promise to challenge and notifyCiphertext the provider cannot readExternal keys for the most sensitive stores
Silent sub-processor changeA notice period and objection rightNothingContract, plus a recurring vendor review
Provider failure or exitA transition periodA workload that redeploys elsewhereDORA exit clause plus a tested redeploy

No technical control catches a silent sub-processor change, which is why the notice period and objection right deserve the most attention in the DPA.

How does Qovery fit into a fintech's data residency setup?

Qovery is an agentic DevOps platform that deploys and runs your applications on Kubernetes inside your own AWS, Google Cloud, Azure or Scaleway account, or on any existing Kubernetes cluster. Qovery does not host your applications. Your apps, managed databases, volumes and backups stay in your account, in the region you pick, under your contract with the cloud provider.

Against the 12 checks:

  • At rest, backups, in transit (checks 1 to 3). Data stays in the cloud account and region you choose. Pick an EU region, an Assured Workloads project or Scaleway in Paris, and your data stays where you chose.
  • Control plane (check 8). Qovery's control plane is separate from your data plane. Qovery's security page states that the control plane runs on AWS and processes deployment metadata (configuration state, resource metrics and deploy events), and that communication with your clusters uses mutually authenticated TLS. Ask us for the control plane region and the full list of data categories in writing; both belong in your register.
  • Builds (check 8, again). By default, Qovery builds container images on a build cluster that Qovery operates, which means your source code passes through it during the build. You can build on your own cluster instead, so source code never leaves your account. For most fintechs I would pick that option for production repositories.
  • Sub-processors (check 9). Qovery is a processor to list for the metadata it handles. Your cloud provider stays your processor for workload data, under your own contract.
  • DORA evidence and exit (check 12). Every deployment and configuration change is audit-logged, access is scoped per project and environment with RBAC, and environments are reproducible from Git and from the Qovery Terraform provider. If the Qovery control plane goes down, you lose the ability to deploy through Qovery, and your running apps keep running in your account. Revoke Qovery's access and the workloads are still standard Kubernetes resources in your cluster, which makes an exit test a real exercise.

Qovery does not make you DORA compliant, and neither does any cloud. It keeps the deployment layer from adding a new data location and produces the change and access evidence your compliance team would otherwise collect by hand, including for AI agents, which deploy through scoped, audited OPA policy tokens rather than a kubeconfig.

Frequently asked questions
What should a European fintech check in a cloud platform's data residency guarantees beyond the EU region?

Check where backups, disaster recovery replicas, logs, telemetry, resource metadata, support tickets and AI prompts are stored and processed, not only primary data. Then check who can access the data and from where, who holds the encryption keys, which sub-processors are involved, where the provider's control plane runs, and whether a non-EU law can compel disclosure. Record each answer with a contractual commitment and a technical control, because DORA Article 30 requires processing and storage locations in the contract.

Does the AWS European Sovereign Cloud or the Microsoft EU Data Boundary protect data from the US CLOUD Act?

No published commitment removes a US parent company from US jurisdiction. AWS commits not to move content outside your chosen region except where necessary to comply with the law or a binding governmental order, and Microsoft France's legal director told the French Senate in June 2025 that he could not guarantee data would never be transmitted to US authorities. Customer-held external keys, partner-operated offers such as Google Cloud Dedicated, or an EU-owned provider are the stronger options for data where compelled disclosure is unacceptable.

What does DORA require about data location in cloud contracts?

DORA Article 30(2)(b) requires every ICT contract to state the regions or countries where services are provided and where data is processed and stored, and requires the provider to notify you in advance of any change. Article 28 adds a register of information covering all ICT contracts and an exit strategy for services that support critical or important functions. The register templates are set by Implementing Regulation (EU) 2024/2956, applicable since 17 January 2025.

Are resource names, tags and logs covered by EU data residency commitments?

Often not in full. Microsoft excludes configuration information such as technical settings and resource names from its definition of Customer Data, and transfers some pseudonymized log data globally for security operations. Keep personal data out of resource names, tags and labels, and send your own logs to sinks you create in EU locations.

Does Qovery store fintech application data outside the customer's cloud account?

No. Qovery deploys and runs applications inside the customer's own AWS, Google Cloud, Azure or Scaleway account or existing Kubernetes cluster, so application data, databases and backups stay in the region the customer chooses. Qovery's control plane runs on AWS and processes deployment metadata, and builds run on Qovery's build cluster by default unless you build on your own cluster. List Qovery as a sub-processor for that metadata and confirm the control plane region in the DPA.

Morgan Perry
About the author
Morgan Perry

Morgan co-founded Qovery and leads engineering. He writes about Kubernetes architecture, DevOps best practices, and building resilient infrastructure at scale.

Next step

Keep your apps and data in your own EU account.

Qovery deploys and runs your apps on Kubernetes inside your own AWS, GCP, Azure or Scaleway account, in the region you choose, with audit logs and RBAC for your DORA evidence. Talk to us about your residency and exit requirements.