Where Is Claude Hosted? EU Hosting & Data Residency Facts (2026)
Where is Claude hosted?
Nowhere EU-only by default. Direct Anthropic (claude.ai and API) may process commercial data in Europe but stores it in the US by default. EU-region Claude hosting runs through AWS Bedrock (eu-central-1 Frankfurt) or Google Vertex AI EU regions, each with its own contract and region verification.
- Direct Anthropic is transfer-based, not EU-only: processing may touch Europe, but storage defaults to the US.
- Claude Enterprise does not add EU data residency — it strengthens governance, not hosting geography.
- Zero data retention answers retention, not geography; treat the two controls separately.
- Bedrock Frankfurt (eu-central-1) and Vertex AI EU regions are the documentable EU path.
Claude is not hosted EU-only by default. Direct Anthropic (claude.ai and the API) may process commercial data in Europe but stores it in the US by default. EU-region Claude hosting runs through AWS Bedrock (eu-central-1 Frankfurt) or Google Vertex AI EU regions, each with its own contract and region verification. This page answers where Claude is hosted, whether it can run EU-only, and which deployment path German procurement teams can defend. Verbatim, excerpt-ready answers to “Is Claude GDPR compliant?” and “Is Claude European?” follow below.
This page provides general information, not legal advice for a specific deployment; individual situations require counsel.
Where is Claude hosted? The short answer
For procurement purposes, collapse the hosting question into three deployment paths:
| Deployment path | EU-only hosting? | What to verify |
|---|---|---|
Direct Anthropic (claude.ai or Anthropic API) | No — processing may include Europe, but default storage is US-based unless otherwise agreed | DPA, SCCs, transfer impact assessment, retention settings |
| Claude via AWS Bedrock in an EU region | Usually yes for the deployment architecture | Region lock or EU geo profile, logs, support access, contract structure |
| Claude via Google Vertex AI in an EU region | Usually yes for the deployment architecture | Region, connected services, logging, contract path |
The short version for an internal memo: do not describe direct Anthropic Claude as EU-only hosted; describe Bedrock or Vertex AI EU deployments as EU-region hosting only after region and contract verification.
Both extremes you will hear in vendor conversations are too blunt. “Claude has no Europe story at all” ignores documented European processing and the EU-region paths above. “Claude is EU hosted” overstates a US-storage default into a residency commitment. German buyers at this stage usually want the procurement defensible answer, not a slogan — the rest of this page separates the four questions that get collapsed into one search term.
Is Claude GDPR compliant?
Commercial Claude plans ship a Data Processing Addendum (Article 28 terms) with Standard Contractual Clauses for Chapter V GDPR transfers — but no default “GDPR compliant” badge exists. Where data is processed depends on deployment: direct claude.ai or API use means US-based processing under SCCs; contractual EU data residency exists only via AWS Bedrock eu-central-1 (Frankfurt) or Vertex AI EU regions.
For a German controller, that distinction decides the review path. If your workflow can accept a transfer-based model, the review turns on the Claude DPA, a transfer impact assessment, and retention settings. If a customer contract, regulator, or professional-secrecy duty requires EU-only processing, SCCs do not carry it — you need an EU-region deployment. Note that team-plan buyers have narrower questions: our Claude Team GDPR guide covers the Team plan’s DPA scope only, while our Anthropic GDPR compliance guide keeps the full compliance picture.
What a German reviewer documents either way:
- the DPA that actually governs the deployment (Anthropic direct, AWS, or Google Cloud)
- transfer mechanism and TIA where processing or support access touches third countries
- retention settings and whether covered data is persisted after use
- whether a DPIA trigger applies under Article 35 GDPR for the intended workflow
Is Claude European?
Anthropic is a US company headquartered in San Francisco, and Claude is not an EU product — no European Claude is built and hosted in the EU. EU availability comes through hyperscaler EU regions: AWS Bedrock (eu-central-1 Frankfurt and other EU regions) or Google Vertex AI EU regions, each with its own contract and region verification.
For German procurement, the practical consequence is not that Claude is unusable — it is that you document it like a US-headquartered processor: Article 28 terms, Chapter V transfer mechanism, subprocessor review, and, where required, an EU-region deployment. Claude servers located in the EU are a deployment choice, not a property of the product.
That is also the honest answer for employee-facing questions. If a works council or an employee asks whether “the AI” stores data in Germany, the defensible answer for direct Claude is no — and for a Bedrock or Vertex AI deployment it is “in an EU region, under these contract terms, with these remaining review points.” Precision here prevents both overclaiming in vendor decks and unnecessary blocking of useful workflows.
Anthropic EU servers: processing vs storage
For direct Anthropic, the practical answer is: Claude may process commercial customer data in Europe and other regions, but storage is still US-based by default unless otherwise agreed.
If the buyer question is really “where are Claude servers located?”, do not simplify that into “Europe” for the direct product. The safer answer is that Anthropic describes a multi-region processing model with US storage by default, not an EU-only hosting product.
Anthropic’s commercial privacy materials distinguish between processing geography and storage geography. The practical reading as reviewed on October 25, 2026 is:
- customer data may be processed in multiple regions, including Europe
- customer data is stored in the US by default unless otherwise agreed
Anthropic’s developer documentation sharpens the same distinction: the inference_geo control offers only US-only or global inference routing — there is no EU option — and the workspace storage geo is currently US-only, with US-only inference carrying a documented pricing multiplier. In other words, Anthropic sells geography control for the US, not for the EU.
For procurement teams, the wording matters. “May be processed in Europe” is not the same statement as “is EU hosted” or “is stored only in the EU.”
Does Claude Enterprise include EU data residency?
No. Claude Enterprise is mainly the procurement and governance layer. It can improve internal controls, admin oversight, and retention posture, but it does not by itself turn direct Anthropic into an EU-only hosting setup.
Use the adjacent pages for the other questions:
- Claude Enterprise for plan and governance scope
- Claude ZDR for retention controls
- Claude DPA for the Article 28 GDPR contract layer
- Anthropic SCC for transfer analysis
EU hosting vs EU data residency vs ZDR vs Enterprise
| Term | What it answers | What it does not answer |
|---|---|---|
| EU hosting | Where the model stack runs | Whether all storage, logs, and support access stay in the EU |
| EU data residency | Whether data stays within the agreed geography under the real operating model | Whether retention is zero or near-zero |
| Zero data retention | Whether covered prompts and outputs are persisted after use | Whether processing is EU-only |
| Claude Enterprise | Whether you get stronger governance and admin controls | Whether Anthropic direct becomes EU-only |
For German buyers, this is where many reviews go wrong. Someone searching anthropic eu data residency is rarely asking whether Enterprise has better admin controls. They are asking whether they can describe the deployment as EU-only without overstating the facts.
Map your requirement to the path before you compare plans:
| If your requirement is… | Best starting answer | Why |
|---|---|---|
| ”We need the cleanest EU-only hosting story” | Bedrock or Vertex AI in an EU region | The infrastructure story is usually easier to document than on Anthropic direct |
| ”We can accept transfers if the contract path is defensible” | Direct Anthropic may still work | The legal review turns on the DPA, SCCs, retention, and workflow sensitivity |
| ”We need lower storage risk, not necessarily EU-only hosting” | Check ZDR separately | Zero data retention answers retention, not geography |
| ”We need admin and governance controls for rollout” | Check Claude Enterprise separately | Enterprise improves governance, not hosting geography |
When Bedrock or Vertex AI is the cleaner answer
For many procurement teams in Germany, the easiest path is not to argue that Anthropic direct is “close enough” to EU hosting. It is to choose the stack that gives the clearest geography story.
AWS Bedrock
Bedrock is often the cleaner path when your company already runs regulated workloads on AWS. AWS confirms that customer content in a selected region stays at rest in that region, and it explicitly positions its EU geographic (Geo) inference profiles — which keep prompts and outputs within EU regions — for GDPR-scoped data residency requirements.
Verify:
- the exact EU region selected for Claude, and whether your model version runs in-region (for example in
eu-central-1Frankfurt) or only through the EU geo profile, which keeps processing inside EU regions but may move it between them - whether any cross-region routing remains enabled
- where logs and telemetry are stored
- whether support or incident handling introduces a separate transfer path
Google Vertex AI
Vertex AI can offer the same clarity for companies standardized on Google Cloud.
Verify:
- the exact EU region used for the Claude deployment
- whether connected Google services create a non-EU path
- how logging, monitoring, and support are actually handled
- which contract path governs the real processing flow
When direct Anthropic + SCCs is still the answer
Not every company needs strict EU-only architecture. If your company can accept a transfer-based model, the real question may be whether direct Anthropic is acceptable under Article 28 GDPR, Chapter V GDPR, and your internal risk model.
That is often the better framing where:
- the workflow is lower sensitivity
- your legal team is comfortable with a transfer-based setup
- there is no customer or regulator requirement for EU-only storage
- the business wants direct Anthropic features rather than cloud intermediary deployment
The important drafting point is simple: an SCC-based answer is not the same as an EU-only hosting answer.
Microsoft 365 Copilot and the EU Data Boundary
Do not assume that enabling Claude models inside Microsoft 365 Copilot keeps the related model processing inside Microsoft’s EU Data Boundary. Microsoft currently states that Anthropic models used in its Copilot experiences are excluded from the EU Data Boundary and, where applicable, in-country processing commitments.
For an EU tenant, confirm the Anthropic-model admin setting, the Microsoft DPA and subprocessor terms, and the data flow for the specific Copilot experience before approval. A general Microsoft 365 residency commitment should not be treated as proof that Claude processing is EU-only.
What to verify before signing
A practical review memo should cover at least these five points:
- Contract path: Are you buying from Anthropic directly, through AWS, or through Google Cloud?
- Region lock: Is the intended EU region actually fixed, or can routing fail over elsewhere?
- Storage and retention: Where is data stored, and for how long?
- Support and subprocessors: Could support access, telemetry, or subprocessors create a non-EU path?
- Workflow sensitivity: Is this an internal research workflow, or does it involve employee, customer, or regulated data?
If the review surfaces that your workflows need EU-only processing, the deployment section above is the place to start; if it surfaces only retention concerns, Claude ZDR answers a different question and both controls can be combined.
Need a Claude deployment review?
Compound Law advises businesses, founders, and in-house teams in Germany on AI procurement, GDPR, commercial contracts, and AI governance. If you need a deployment-specific review of Claude hosting, data residency, DPA terms, or transfer risk, contact us.
