Nov 17, live webinar: ECS to EKS without freezing the roadmap for a quarter

8 best GDPR-compliant cloud hosting providers for European companies in 2026

A buyer's guide to GDPR-compliant cloud hosting in Europe: OVHcloud, Scaleway, STACKIT, IONOS, Hetzner, AWS, Google Cloud and Microsoft Azure compared on EU headquarters, EU regions, DPA and SCCs, sub-processors, CLOUD Act exposure and certifications.

Mélanie Dallé
Senior Marketing Manager
NOV 17, 2026 · 19 MIN
8 best GDPR-compliant cloud hosting providers for European companies in 2026

Key points:

  • No cloud provider is "GDPR certified", and no region makes you compliant on its own. GDPR regulates processing. You need an Article 28 processor contract, a sub-processor list you can track, Article 32 security measures, and a Chapter V transfer mechanism whenever anyone outside the EEA can access the data, including support staff (EDPB Guidelines 05/2021).
  • My shortlist for European companies: OVHcloud, Scaleway, STACKIT, IONOS and Hetzner if you want an EU-headquartered provider with no US parent, and AWS, Google Cloud and Microsoft Azure if you need the deepest managed services and accept a documented transfer assessment.
  • The real dividing line is the parent company's jurisdiction. A US parent falls under the CLOUD Act wherever the server sits. Microsoft France told the French Senate in June 2025 it could not guarantee that French data would never be handed to US authorities (Senate record).
  • EU headquarters are not a magic shield either. OVHcloud is contesting Canadian criminal charges over a production order for data hosted in France, the UK and Australia (OVHcloud). Any group with subsidiaries abroad can receive foreign orders.
  • Qovery is not a hosting provider and is not ranked here. It deploys your apps into your own account at whichever provider you choose, which keeps the deployment layer off your list of data processors for workload data.

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

The question I hear most from European founders and DPOs is "which cloud is GDPR compliant?" It sounds like a yes or no question. Every major cloud will sign a data processing agreement, offer EU regions and publish a sub-processor list. The differences sit in who owns the provider, which law can reach it, how much notice you get before a new sub-processor touches your data, and how much paperwork you will write to justify the choice.

So this guide ranks providers on the things a GDPR review checks. If your main concern is sovereignty for Kubernetes workloads, read our 10 best sovereign cloud providers in Europe for Kubernetes instead. If you host patient data, our ranked shortlist for EU healthcare data adds HDS and C5. This one is for the general case: a European company processing customer and employee personal data that wants a defensible hosting choice.

How did we pick the best GDPR-compliant cloud hosting providers?

We judged every provider on six criteria a DPO or an enterprise customer's privacy team will check, in this order: jurisdiction of the parent company, EU regions, the DPA and its transfer clauses, sub-processor transparency, adherence to a GDPR code of conduct, and security certifications. We left price and raw performance out on purpose because they are not GDPR questions.

First, a reminder of what GDPR asks of a hosting provider, because "GDPR compliant hosting" is a marketing phrase:

  • Article 28 requires a written contract with your processor, sufficient guarantees, and your prior authorisation for sub-processors. The EDPB's Opinion 22/2024 adds that controllers should be able to identify every sub-processor in the chain, not only the first one.
  • Article 32 requires security appropriate to the risk. Certifications help you show it. They do not replace your own measures.
  • Chapter V applies to any transfer outside the EEA. The EDPB's Guidelines 05/2021 treat remote access from a third country, for example by a support engineer, as a transfer even when the data is stored in the EU.
  • Article 48 says a third-country court order is only recognised if based on an international agreement such as a mutual legal assistance treaty. The EDPB's Guidelines 02/2024 explain how that interacts with requests served on a parent company abroad.

The biggest GDPR fines so far are for transfers: €1.2 billion against Meta in 2023 for EU-US transfers on SCCs (EDPB), and €290 million against Uber in 2024 for sending European drivers' data to the US without a transfer tool (Autoriteit Persoonsgegevens).

The six criteria, in practice:

  1. Jurisdiction. Is the provider and its ultimate parent established in the EU, with no US parent that the CLOUD Act can compel?
  2. EU regions. Can you keep data, backups and replicas in EEA regions, ideally with more than one location for disaster recovery?
  3. DPA and SCCs. Is the Article 28 DPA standard and public, and are the 2021 Standard Contractual Clauses (Decision (EU) 2021/914) built in where a transfer can happen?
  4. Sub-processors. Is there a public list, and how much notice do you get before a new one starts processing your data?
  5. GDPR code of conduct. Does the provider adhere to an approved Article 40 code: the EU Cloud Code of Conduct, approved by the Belgian DPA in May 2021 (Belgian DPA), or the CISPE Data Protection Code of Conduct, approved by the CNIL in June 2021?
  6. Certifications. ISO/IEC 27001 at minimum, plus BSI C5, HDS or SecNumCloud where your sector or customers require them.

Which cloud hosting providers are the best fit for GDPR in 2026?

For most European companies the best GDPR fits are OVHcloud, Scaleway, STACKIT, IONOS and Hetzner when you want to avoid a non-EU parent, and AWS, Google Cloud and Microsoft Azure when you need their managed services and can document a transfer impact assessment. All eight sign a DPA and offer EU regions. They differ on jurisdiction, managed services and evidence.

RankProviderHQ and parent lawEU locations (examples)DPA and transfer clausesSub-processor listGDPR code of conductKey certificationsBest for
1OVHcloudFrance (OVH Groupe SA)France, Germany, Poland and moreDPA in standard contracts (OVHcloud)Published with contractsNot verified hereISO 27001, HDS, C5, SecNumCloud on named offersBroad EU catalogue with a French parent
2ScalewayFrance (Iliad group)Paris, Amsterdam, Warsaw, MilanDPA in contractsPublic listNot verified hereISO 27001, HDS (SecNumCloud in qualification)Developer-led teams wanting managed Kubernetes in the EU
3STACKITGermany (Schwarz Group)Germany, AustriaDPA, EU-only operations (STACKIT)Check contract documentsNot verified hereBSI C5 Type 2, ISO 27001, 27017, 27018German and Austrian companies with C5 requirements
4IONOS CloudGermany (IONOS SE)Germany and other EU sitesDPA in contracts (IONOS)Check contract documentsNot verified hereBSI C5 Type 1 on core services, ISO 27001German jurisdiction with managed Kubernetes on a budget
5HetznerGermany (Hetzner Online GmbH)Nuremberg, Falkenstein, HelsinkiDPA concluded in the customer account (Hetzner)Public PDFNot verified hereISO 27001:2022 for its DE and FI data centresLowest-cost EU compute run by your own team
6AWSUS (Amazon)Frankfurt, Ireland, Paris, Milan, Stockholm, Spain, plus the AWS European Sovereign CloudGDPR DPA in the Service Terms, SCCs apply automatically (AWS)Public, 30 days' noticeCISPE, over 100 services listedISO 27001, SOC 2, C5, HDS and moreDeepest managed services with GDPR paperwork done well
7Google CloudUS (Alphabet)Several EU regions (Google Cloud)Cloud DPA incorporates SCCs (Google Cloud)Public, 30 days' noticeEU Cloud CoCISO 27001, SOC 2, C5, HDS and moreData and AI workloads, sovereign controls, S3NS in France
8Microsoft AzureUS (Microsoft)Many EU regions (Azure)Products and Services DPA (Microsoft)Published with the DPAEU Cloud CoCISO 27001, SOC 2, C5, HDS and moreMicrosoft-centric companies, EU Data Boundary

"Not verified here" means I could not confirm adherence in the public registers I checked on 17 November 2026, not that the provider fails the criterion. The CISPE register in particular lists hundreds of services and is easy to misread, so search it yourself for the exact service you plan to use.

Which EU-headquartered providers are the best GDPR choice?

The five EU-headquartered providers on this list remove the CLOUD Act question for the parent company, which removes the hardest part of a transfer impact assessment. They trade it for a smaller managed service catalogue than the US hyperscalers. Choose one when your customers or your DPO want no US parent in the chain.

1. OVHcloud

Verdict: the best all-round EU-headquartered provider for GDPR, with the widest catalogue and the most certifications among European clouds. Skip it if you need a managed service only a hyperscaler sells, or if your legal team wants a provider with no subsidiaries outside the EU.

OVHcloud is French, listed in Paris, and publishes its data processing agreement and sub-processor list with its standard contracts. It holds HDS for French health data (OVHcloud), a BSI C5 attestation, and SecNumCloud on specific offers such as Bare Metal Pod. Managed Kubernetes and managed databases are available.

One fact belongs in your assessment. In April 2024 the Royal Canadian Mounted Police obtained a production order for subscriber data linked to OVH servers in France, the UK and Australia. An Ontario court refused to revoke it in September 2025 (The Register), and OVHcloud now faces charges in Canada, which it says it will contest, arguing the request should have gone through a mutual legal assistance treaty (OVHcloud, 31 July 2026). OVHcloud refused to hand the data over, citing French law. That is the behaviour a GDPR controller wants, and it is also a reminder that being EU-headquartered limits foreign pressure without removing it. I hope this gets resolved quickly for them, because every provider with a foreign subsidiary faces the same question.

2. Scaleway

Verdict: the best choice for developer-led teams that want managed Kubernetes and managed databases in the EU with a French parent. Skip it if you need regions outside Europe or a SecNumCloud qualification today.

Scaleway belongs to the French Iliad group and runs its regions in Paris, Amsterdam, Warsaw and Milan. It publishes a sub-processor list, holds HDS for French health data, and is in the process of SecNumCloud qualification (Scaleway). Kubernetes Kapsule is the managed Kubernetes product.

For a GDPR review, Scaleway is often the easiest EU option to explain: an EU parent, EU-only regions, and a service catalogue wide enough to run a standard SaaS stack without bolting on US tools.

3. STACKIT

Verdict: the best fit for German and Austrian companies whose customers ask for BSI C5 Type 2 and EU-only operations. Skip it if you need a large regional footprint or a long list of managed services.

STACKIT is the cloud of Schwarz Digits, part of the Schwarz Group (Lidl, Kaufland). Its facts page states development, operation and data processing "exclusively in Germany and Austria", lists data centres in Neckarsulm, Ellhofen and Ostermiething, and claims operation "without being subject to the U.S. CLOUD Act" because there is no US parent. It holds C5 Type 2, ISO 27001, ISO 27017 and ISO 27018 (the cloud privacy standard). STACKIT Kubernetes Engine (SKE) is the managed Kubernetes service.

4. IONOS Cloud

Verdict: a solid German option with managed Kubernetes and a lower price point than STACKIT. Skip it if your buyers require a C5 Type 2 report rather than Type 1.

IONOS is a listed German group headquartered in Montabaur. It announced a BSI C5 Type 1 attestation in November 2023 covering Compute Engine, Cloud Cubes and S3 Object Storage. A Type 1 report assesses the design of controls at a point in time; a Type 2 report tests their operation over a period. Many German enterprise buyers will ask which one you have, so check the current status on the IONOS security page before you put it in a tender.

5. Hetzner

Verdict: the cheapest way to run EU compute under German law, if your team operates the stack itself. Skip it if you need managed Kubernetes, managed databases or a C5 report.

Hetzner Online GmbH and Hetzner Finland Oy hold ISO/IEC 27001:2022 for the Nuremberg, Falkenstein and Helsinki data centres (Hetzner certificates). You conclude the DPA directly in the customer account, and the sub-processor list is public (Hetzner).

Read the location detail. Hetzner also runs cloud locations in Ashburn, Virginia and Hillsboro, Oregon through Hetzner US LLC. Data only goes there if you pick those locations, so pin your projects to EU locations and write that rule down.

When are AWS, Google Cloud or Microsoft Azure the right GDPR choice?

A US hyperscaler is the right choice when you need managed services the EU providers do not offer, and you are willing to document a Chapter V transfer impact assessment that covers the US parent. All three have mature GDPR paperwork, EU regions and code of conduct adherence. None of them can change the nationality of the parent company.

6. AWS

Verdict: the strongest hyperscaler on GDPR paperwork, with CISPE adherence and a separate European Sovereign Cloud. Skip it if your customers or regulator require a provider with no US parent.

The AWS GDPR DPA is part of the AWS Service Terms, and the 2021 SCCs "apply automatically" when customer data is transferred outside the EEA (AWS). AWS commits to update its sub-processor page at least 30 days before engaging a new sub-processor, with email notifications if you subscribe. More than 100 AWS services appear in the CISPE public register, assessed by Ernst & Young CertifyPoint.

The AWS European Sovereign Cloud opened in Brandenburg in January 2026, operated by EU-resident staff under German subsidiaries. It narrows operational access. It does not change Amazon's US parent, so the CLOUD Act question stays in your assessment.

7. Google Cloud

Verdict: a strong pick for data and AI workloads, with clear DPA terms and a French option through S3NS. Skip it if you cannot accept a US parent for your primary platform.

Google's Cloud Data Processing Addendum incorporates the SCCs and says they prevail in a conflict. It also gives you notice "at least 30 days before the New Subprocessor starts processing any Customer Data" and a 90-day window to object by terminating. Read section 10.1 carefully: without a data location selection, customer data "may be processed in any country where Google or its Subprocessors maintain facilities", so set location restrictions explicitly. Google Cloud adheres to the EU Cloud Code of Conduct.

For French buyers, S3NS, the Thales-controlled joint venture running Google technology, obtained SecNumCloud for PREMI3NS. Google also sells sovereign controls on its public regions.

8. Microsoft Azure

Verdict: the natural pick for companies already running on Microsoft 365 and Entra ID, with the EU Data Boundary. Skip it if a buyer asks you to guarantee that a US authority cannot obtain the data.

Microsoft completed the EU Data Boundary in February 2025, covering customer data, pseudonymised personal data and professional services data. In April 2025 it committed to "challenge any government demand for EU public sector or enterprise customer data where we have a legal basis" (Microsoft). Azure adheres to the EU Cloud Code of Conduct, and the Products and Services DPA is public.

The limit was stated under oath. On 10 June 2025, asked by the French Senate whether he could guarantee that French citizens' data would never be transmitted to US authorities without French agreement, Microsoft France's director of public and legal affairs answered: "No, I cannot guarantee it, but, once again, it has never happened" (Senate record, my translation). I appreciate the honesty, and your DPO will quote that sentence.

Pick the cloud your DPO approves. Keep the same deployment workflow.
Qovery deploys your apps on Kubernetes in your own AWS, GCP, Azure or Scaleway account, or on an existing cluster at any EU provider, so the data and the contract stay in your name. Free plan, no credit card.

Is an EU region of a US cloud provider enough for GDPR?

An EU region of AWS, Google Cloud or Azure can be GDPR-compliant if you document it: the provider's DPA and SCCs, a transfer impact assessment that covers access by the US parent, supplementary measures such as encryption with keys you control, and a sub-processor register. An EU region does not take the US parent out of reach of the CLOUD Act, which compels US providers to disclose data in their "possession, custody, or control" regardless of where it is stored (18 U.S.C. 2713).

The EU-US Data Privacy Framework adequacy decision, adopted on 10 July 2023 (European Commission), simplifies transfers to certified US companies. The General Court dismissed the Latombe challenge on 3 September 2025 (IAPP), and the case can still go to the Court of Justice. Treat the DPF as valid, check the case file before you rely on it, and keep SCCs in your contracts as the fallback. The EDPB Recommendations 01/2020 describe the supplementary measures a TIA should consider.

Buyers are moving anyway. In a Gartner survey published in November 2025, 61% of Western European CIOs and IT leaders said geopolitics would increase their reliance on local or regional cloud providers. For a B2B company, that means the hosting question increasingly arrives in a customer's security questionnaire, not only from your own DPO.

Question your DPO will askEU-headquartered providerUS hyperscaler, EU regionUS hyperscaler sovereign offering
Can a US authority compel the parent company?No US parentYes, under the CLOUD ActYes, the parent is unchanged
Is a transfer impact assessment needed for the provider itself?Usually only for non-EU sub-processors and supportYesYes, with stronger operational measures
Who can access data for support?Check the sub-processor listGlobal support unless restricted by contractEU-resident staff
Managed service depthModerateHighestReduced catalogue
ExampleOVHcloud, Scaleway, STACKIT, IONOS, HetznerAWS Frankfurt, Azure West Europe, Google europe-west1AWS European Sovereign Cloud, S3NS

For the full ladder from residency to legal immunity, read our explainer on the four levels of EU cloud sovereignty.

What should you check in the contract before you sign?

Every provider above has a GDPR landing page. The obligations live in the DPA, the sub-processor list and the service terms. Here is the list I would work through with a DPO before signing:

  1. The DPA itself. Is it Article 28-complete (subject matter, duration, instructions, confidentiality, security, sub-processors, assistance, deletion or return, audits)?
  2. Transfer clauses. Are the 2021 SCCs incorporated, in which modules, and do they prevail over the rest of the contract?
  3. Sub-processor notice. How many days before a new sub-processor starts, how you are notified, and what you can do if you object. AWS and Google both give 30 days.
  4. Data location. Is region pinning a contractual commitment for the services you use, including backups, logs and support tooling? Google's DPA, for example, defaults to processing anywhere unless you select a location.
  5. Support access. From which countries can support staff access your environment? Under EDPB Guidelines 05/2021, that access is a transfer.
  6. Government requests. Does the provider commit to challenge requests, notify you where legally allowed, and publish a transparency report?
  7. Breach notification. How fast the provider notifies you, so you can meet the 72-hour deadline of GDPR Article 33.
  8. Certifications in scope. Is the exact service you use inside the ISO 27001, C5 or HDS scope, and is the C5 report Type 1 or Type 2?
  9. Exit. Data export formats and deletion certificates at the end of the contract.

Then trace one real request through your stack and list every tool that sees personal data: CDN, error tracker, log platform, email provider, CI runners and the deployment platform. The hosting provider is rarely where a GDPR review finds the problem. Verizon's 2025 Data Breach Investigations Report found third-party involvement in 30% of breaches, double the year before. Our EU data residency guide for Kubernetes walks through where data typically leaks out of an EU cluster.

Where does Qovery fit when you choose a GDPR-compliant host?

Qovery is the deployment layer on top of the provider you pick. It is an Agentic DevOps platform that deploys your applications on Kubernetes inside your own AWS, GCP, Azure or Scaleway account, or on an existing cluster at OVHcloud, STACKIT, IONOS, Hetzner or anywhere else running Kubernetes 1.31 or later. Your workloads, databases, logs and cloud bill stay in your account, under the DPA you signed with that provider.

The Qovery control plane orchestrates deployments and does not run your applications or store your production data, so for GDPR the hosting provider remains the processor for your workload data. Qovery publishes its own security posture on qovery.com/security, and you would list it as a supplier for the deployment metadata it handles.

In practice this gives you:

  • A provider choice you can change. The same git-push workflow, preview environments per pull request and Terraform provider work whether you run on Scaleway in Paris or AWS in Frankfurt, so moving a workload to a different provider is a cluster change, not a rewrite.
  • Region pinning by design. You create the cluster in the EU region you chose, and Qovery deploys there. Managed cloud databases (for example RDS on AWS) are provisioned in the same account.
  • Evidence for Article 32. Per-environment RBAC (Qovery RBAC) and an audit log of who deployed what, and OPA-scoped tokens for AI agents (OPA in Qovery).

Qovery does not make you GDPR compliant, and no platform can. Your DPA with the provider, your records of processing and your transfer assessment remain yours. If you already run Terraform and Argo CD comfortably on your chosen cloud, you may not need a platform layer at all.

How do I deploy to the provider I picked from Claude Code or Cursor?

Install the Qovery Agent Skills once, then ask your coding agent to deploy to your own account in the EU region you chose. The agent shows its plan and asks you to approve each step.

BASH|Install the Qovery Agent Skills for Claude Code, Cursor, Codex, OpenCode or Gemini CLI
curl -fsSL https://skill.qovery.com/install.sh | bash

# Or scope the install to this repository only
curl -fsSL https://skill.qovery.com/install.sh | bash -s -- --project

# Add the Qovery MCP Server to Claude Code over OAuth, read-only by default
claude mcp add --transport http qovery https://mcp.qovery.com/mcp --callback-port 4242

# Write access, only when you explicitly want it (also enable write access in the Qovery Console)
claude mcp add --transport http qovery "https://mcp.qovery.com/mcp?read_write=true" --callback-port 4242

The install script needs your approval, and the MCP Server opens an OAuth login in your browser. The skills (qovery-onboard, qovery-deploy, qovery-troubleshoot, qovery-optimize, qovery-speedup, qovery-preview, qovery-terraform) do the deployment work; the MCP Server operates what already exists. Then ask, for example, "deploy this app to my Scaleway account in the Paris region with Qovery" or "deploy this to my AWS account in eu-central-1 with Qovery". See the AI agent quickstart and the Claude Code integration.

Frequently asked questions
What are the best GDPR compliant cloud hosting providers for European companies?

The best GDPR-compliant cloud hosting providers for European companies in 2026 are OVHcloud, Scaleway, STACKIT, IONOS and Hetzner if you want an EU-headquartered provider with no US parent, and AWS, Google Cloud and Microsoft Azure if you need their managed services and can document a transfer impact assessment. All eight sign an Article 28 DPA and offer EU regions. Choose based on jurisdiction, sub-processor transparency, certifications your customers ask for, and the managed services you need.

Is AWS, Azure or Google Cloud GDPR compliant if I use an EU region?

You can use AWS, Azure or Google Cloud in an EU region in a GDPR-compliant way, but the region alone is not enough. You need the provider's DPA with SCCs, a sub-processor register, location restrictions set in your configuration, and a transfer impact assessment covering access by the US parent company under the CLOUD Act. Many companies do this successfully; some customers and public buyers still refuse a US parent.

Does the US CLOUD Act apply to data stored in the EU?

Yes, for US providers. The CLOUD Act (18 U.S.C. 2713) requires US service providers to disclose data in their possession, custody or control regardless of where it is stored. GDPR Article 48 says such orders are only recognised under an international agreement, which creates a legal conflict the provider has to manage, not a guarantee for you.

Is there such a thing as a GDPR-certified cloud provider?

No provider is "GDPR certified" in general. GDPR allows approved codes of conduct and certifications under Articles 40 and 42, and cloud providers can adhere to codes such as the EU Cloud Code of Conduct (Microsoft Azure, Google Cloud) or the CISPE Code (over 100 AWS services). Adherence is evidence of processor guarantees, but the controller still needs its own DPA, records of processing and security measures.

Is Hetzner GDPR compliant?

Hetzner offers an Article 28 DPA that you conclude in your customer account, publishes its sub-processor list, and holds ISO/IEC 27001:2022 for its Nuremberg, Falkenstein and Helsinki data centres. It is a German company with no US parent. It also operates US cloud locations, so keep your projects in EU locations, and note that Hetzner offers no managed Kubernetes or managed databases.

Do I need a sovereign cloud to comply with GDPR?

No. GDPR does not require a sovereign cloud or an EU-headquartered provider. It requires lawful processing, a processor contract, appropriate security and a valid mechanism for any transfer outside the EEA. Sovereign clouds reduce the transfer risk from non-EU jurisdictions, which some customers, sectors and public buyers now require on top of GDPR.

Mélanie Dallé
About the author
Mélanie Dallé

Melanie leads content at Qovery. She covers platform engineering trends, Kubernetes operations, FinOps, and the tools that help engineering teams ship faster.

Next step

Pick the cloud your DPO approves. Keep the same deployment workflow.

Qovery deploys your apps on Kubernetes in your own AWS, GCP, Azure or Scaleway account, or on an existing cluster at any EU provider, so the data and the contract stay in your name. Free plan, no credit card.