Claude Data Residency: EU Inference 2026

TL;DR

Claude data residency in the EU is not a first-party API setting. inference_geo accepts only global and us. Pin inference with Bedrock eu.anthropic.claude-sonnet-5-5 or the Google host aiplatform.eu.rep.googleapis.com. Foundry stays on Global or US Data Zone. Regional and multi-region routes add 10 percent.

What does Claude data residency actually control?

Claude data residency is three controls, not one toggle. Inference location, storage location and retention can diverge. Anthropic’s data residency page splits inference_geo (where the model runs) from workspace geo (data at rest plus endpoint work such as image transcoding). On Bedrock and Google Cloud the endpoint or profile sets the place. The API parameter does not.

GDPR does not require an EU site. It requires a processor contract, a legal basis and a transfer tool for any flow out of the EEA. Residency removes that transfer question. The provider matrix lives in Claude GDPR compliance in Europe. This is not legal advice.

Ask three questions before you pick a route:

1. Where does inference run? Bedrock EU geo or Google Europe multi-region stay inside the documented geography. The Anthropic API and Foundry do not offer an EU pin.
2. Where do logs and workspace data sit? Claude API workspace geo is us only and cannot change after create.
3. Is anything retained? Residency and zero data retention are separate. Fable 5 and 5.1 keep prompts for 30 days on every route.

Route	EU inference	Storage / workspace	Control
Claude API (first-party)	No, global or us only	Workspace geo us only	inference_geo, allowed_inference_geos
Claude Platform on AWS	No, global or us only	Effective us	inference_geo; the AWS Region does not pin
Amazon Bedrock	Yes, EU geo or in-region Ireland / Stockholm	Processing Region	Profile ID or mantle URL
Google Cloud	Yes, Europe multi-region	At rest in the chosen location	Host aiplatform.eu.rep.googleapis.com
Microsoft Foundry	No, Global or US Data Zone	At rest in the Azure geography	Deployment type, no inference_geo

Why can the Anthropic API not pin the EU?

The Anthropic API has no Claude data residency option for the EU in 2026. inference_geo accepts global (default, any geography) and us (US infrastructure only). Workspace geo is us only. Both limits sit under Current limitations. There is no eu value.

The parameter works on Claude 4.6 and later. Opus 4.5, Sonnet 4.5 (deprecated), Haiku 4.5 and older models return 400. It applies on the Claude API and Claude Platform on AWS. Bedrock and Google take the region from the endpoint. Foundry takes it from the deployment type. The OpenAI-compatible endpoint does not accept the parameter.

US-only inference is priced at 1.1x across input, output, cache writes and cache reads. Global stays on the list price. On Haiku 5.5 the multiplier also applies above 100,000 tokens. Priority Tier burns 1.1 tokens of committed TPM per US token. Each Batch item can set its own inference_geo.

curl https://api.anthropic.com/v1/messages \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{
    "model": "claude-sonnet-5-5",
    "max_tokens": 1024,
    "inference_geo": "us",
    "messages": [{"role": "user", "content": "State the residency limits in two sentences."}]
  }'

The response includes usage.inference_geo. Workspace defaults live in Console or the Admin API under data_residency. allowed_inference_geos rejects values outside the list. default_inference_geo applies when a request omits the field. Workspaces that used the old US opt-out now have allowed_inference_geos: ["us"] and default_inference_geo: "us".

Claude Platform on AWS uses the same rules. The AWS Region scopes the gateway, IAM, CloudTrail and the invoice. It does not pin inference. Workspace geo is not configurable there and is effectively us. A CCU costs 0.01 USD. One hundred CCU equal 1 USD.

Zero data retention is a separate contract. It covers Messages and Token Counting. It does not cover Console, Managed Agents, consumer plans, Team surfaces, or Fable and Mythos without a special grant. HIPAA readiness is not available on Claude Platform on AWS or Foundry. Model choice is in Claude Sonnet vs Opus.

How do you enable EU residency on Bedrock?

Claude data residency on Bedrock is the profile ID or the mantle URL, not inference_geo. The Sonnet 5.5 card lists launch on 28 September 2026, end no sooner than 28 September 2027, 1 million context tokens, 128,000 output tokens, a June 2026 cutoff and geo ID eu.anthropic.claude-sonnet-5-5.

Anthropic’s region table splits three endpoint types. Global routes worldwide with no premium. Regional resolves to the named Region and adds 10 percent. In-region without a profile exists in Europe only in Ireland (eu-west-1) and Stockholm (eu-north-1). Frankfurt, Zurich, Milan, Spain, London and Paris carry Global plus EU.

From Frankfurt (eu-central-1) the card lists Frankfurt, Stockholm, Milan, Spain, Ireland and Paris. London joins only when the source is London. Zurich joins only when the source is Zurich. That is EU residency, not a single Frankfurt hall. If a contract names one country, use mantle in Ireland or Stockholm. Setup detail is in Claude on AWS Bedrock in the EU. The wider catalogue is in the Amazon Bedrock EU guide.

Source	Destinations for eu.anthropic.claude-sonnet-5-5
Frankfurt	Frankfurt, Stockholm, Milan, Spain, Ireland, Paris
Ireland, Stockholm, Milan, Spain, Paris	the same six, no London, no Zurich
London	the six plus London
Zurich	the six plus Zurich

Six steps:

1. Enable Claude Sonnet 5.5 model access in an EU Region.
2. Scope IAM to the eu.anthropic.claude-sonnet-5-5 profile ARN and the foundation model. Deny unspecified so global routing cannot slip through.
3. Call get-inference-profile and read the destination ARNs. Stop if any Region sits outside the EU.
4. Send a test on bedrock-runtime in eu-central-1, or on mantle in eu-west-1 / eu-north-1.
5. Set retention per Region. none is zero retention. Fable 5 and 5.1 require aws_review or they stay unavailable.
6. Keep your own request logs for at least 30 days. Anthropic recommends that window for investigations.

aws bedrock get-inference-profile \
  --region eu-central-1 \
  --inference-profile-identifier eu.anthropic.claude-sonnet-5-5 \
  --query "models[].modelArn" --output table

aws bedrock-runtime converse \
  --region eu-central-1 \
  --model-id eu.anthropic.claude-sonnet-5-5 \
  --messages '[{"role":"user","content":[{"text":"List the EU destinations for this profile."}]}]' \
  --inference-config '{"maxTokens":512}'

from anthropic import AnthropicBedrockMantle

client = AnthropicBedrockMantle(aws_region="eu-west-1")
message = client.messages.create(
    model="anthropic.claude-sonnet-5-5",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Summarise Article 28 GDPR in two sentences."}],
)
print(next(block.text for block in message.content if block.type == "text"))

The mantle URL is https://bedrock-mantle.{region}.api.aws/anthropic/v1/messages. Default quota is 2 million input tokens per minute, raisable to 5 million input and 500,000 output without extra Anthropic approval. AWS still enforces RPM. Cache needs at least 512 tokens and at most 4 checkpoints, with a 5-minute or 1-hour TTL.

Retention is per Region. none writes nothing durable. default follows the model. aws_review lets AWS review inside the AWS boundary, not Anthropic. With cross-region inference, retained data sits in the processing Region, so the EU profile keeps it in the EU. Fable 5 and 5.1 list allowed_modes as aws_review and provider_data_share and retain prompts for up to 30 days. Structured outputs, the Files API, Message Batches and server-side tools are missing on Bedrock.

How do you enable EU residency on Google Cloud?

Claude data residency on Google Cloud is the Europe multi-region endpoint, not inference_geo. The Sonnet 5.5 page lists United States multi-region, Europe multi-region and Global. ML processing: US, Europe, plus asia-southeast1. Release 28 September 2026, retirement no sooner than 28 September 2027. Model ID claude-sonnet-5-5. 1,000,000 input, 128,000 output.

The EU endpoint covers EU member states only. The United Kingdom and Switzerland sit outside that boundary. Data at rest stays in the location you chose, whatever endpoint you call. Global (aiplatform.googleapis.com) gives no residency guarantee. Use constraints/gcp.restrictEndpointUsage to block it.

The partner-model guide sets the EU host to aiplatform.eu.rep.googleapis.com and locations/eu. Multi-region covers Claude 4.7 and later. Prompt caching is on, provisioned throughput is off. Europe quotas: 1,250 QPM, 12,500,000 uncached input TPM, 1,250,000 output TPM. Global: 2,500 QPM, 25,000,000 input, 2,500,000 output. Customer prompts are not shared with third parties. Roles: Consumer Procurement Entitlement Manager plus Agent Platform User. The Vertex walk-through is in Claude on Vertex AI in Europe.

export PROJECT_ID="YOUR_PROJECT_ID"
export LOCATION="eu"
export ENDPOINT="aiplatform.eu.rep.googleapis.com"
export MODEL_ID="claude-sonnet-5-5"

curl -X POST \
  -H "Authorization: Bearer $(gcloud auth application-default print-access-token)" \
  -H "Content-Type: application/json" \
  "https://${ENDPOINT}/v1/projects/${PROJECT_ID}/locations/${LOCATION}/publishers/anthropic/models/${MODEL_ID}:rawPredict" \
  -d '{
    "max_tokens": 300,
    "anthropic_version": "vertex-2023-10-16",
    "messages": [{"role": "user", "content": [{"type": "text", "text": "Why does inference stay in the EU?"}]}]
  }'

1. Enable the model in Model Garden. A blocked reseller cannot accept the terms.
2. Grant the IAM roles and allow cloudcommerceconsumerprocurement.googleapis.com in the org policy.
3. Hard-code location eu and host aiplatform.eu.rep.googleapis.com.
4. Block Global with constraints/gcp.restrictEndpointUsage.
5. Check EuOnlinePrediction* quotas before you put load on the EU line.

Sonnet 5.5 has no thinking: disabled. The closest setting is between_tools.

What can Foundry and Claude Platform on AWS do?

Neither Foundry nor Claude Platform on AWS ships Claude data residency in the EU in 2026. Foundry documents Global Standard and Data Zone Standard (US). The US zone covers Azure-hosted Haiku 4.5, Haiku 5.5, Opus 5.5, Opus 5.5 Fast, Opus 5, Opus 4.8, Sonnet 5 and Sonnet 5.5. An EU data zone is not on that list.

Version 1 runs on Anthropic infrastructure outside Azure. Version 2 runs on Azure and is GA. Anthropic remains seller of record and processor. Billing uses CCU at 0.01 USD. One hundred CCU equal 1 USD. US Data Zone uses the same 1.1x multiplier as inference_geo: "us". top_p must be 0.99. Product context is in Azure AI Foundry in Europe.

Claude Platform on AWS also bills in CCU. The AWS Region does not pin inference. The choices stay us and global. For personal data in prompts, Bedrock and Google Cloud remain the documented EU paths.

What does Claude data residency cost in the EU?

Claude data residency on Bedrock and Google is a 10 percent premium over the global list price, from Sonnet 4.5, Haiku 4.5, Opus 4.5 and every later model. The pricing page states that for regional and multi-region endpoints. The first-party API is global and has no EU geo. Its 1.1x multiplier applies only to US inference.

Route	Input / output per 1M	Cache read	Note
Sonnet 5.5, Claude API global	2.00 / 10.00	0.10	5-minute write 2.50, 1-hour write 4.00
Sonnet 5.5, Bedrock EU or Google Europe	2.20 / 11.00	0.11	10 percent rule
Opus 5.5, Claude API global	4.00 / 20.00	0.20	regional plus 10 percent
Opus 5.5, Bedrock EU or Google Europe	4.40 / 22.00	0.22	10 percent rule
Haiku 5.5 up to 100,000 tokens, global	0.10 / 0.50	0.01	above that 0.50 / 2.50
Haiku 5.5 up to 100,000 tokens, EU	0.11 / 0.55	0.011	10 percent rule
US-only, Claude API or Foundry US zone	1.1x the global row	1.1x	no EU pin
Batch	50 percent of the chosen row	same row	not with Fast mode
Fast mode Opus 5.5	8.00 / 40.00	on the Fast price	not on Bedrock or Google

Example: 10 million input and 2 million output on Sonnet 5.5. Global 40 USD. EU 44 USD. Those 4 USD buy the documented geography. Euro token rates are in Claude API pricing in the EU.

Batch halves input and output. Fast mode for Opus 5.5 is 8 / 40 USD, exists on Foundry hosted on Azure, not on Bedrock, Google or Claude Platform on AWS, and stacks the residency multiplier. Fable 5.1 lists 10 / 50 USD and has regional Bedrock endpoints in us-east-1 only.

We recommend Bedrock or Google in the EU as soon as prompts carry personal data. Ten percent is cheaper than a transfer impact assessment. Keep Foundry and the Claude API for non-personal workloads or for cases with a documented transfer tool.

FAQ

Does the Anthropic API offer Claude data residency in the EU?

No. inference_geo accepts only global and us. Workspace geo is us only and cannot change after create. No eu value is documented. EU inference runs on Bedrock or Google Cloud.

What does Claude data residency cost on Bedrock and Google?

Regional and multi-region endpoints add 10 percent from Sonnet 4.5 onward. Sonnet 5.5 moves from 2 / 10 to 2.20 / 11 USD per million tokens. The same rule applies to Opus 5.5 and Haiku 5.5. The first-party API has no EU tariff, only 1.1x for US inference.

Bedrock vs Google Cloud: which path for the EU?

Google Europe excludes the UK and Switzerland and is the tighter map. Bedrock gives in-region inference in Ireland and Stockholm when a contract names a country. From Frankfurt the EU profile spreads across six EU Regions and skips London. Both exclude training on customer prompts. Pick the cloud that already holds the data.

Is zero data retention a substitute for residency?

No. ZDR governs retention after the response, not where inference ran. The Claude API can be on ZDR and still run globally or in the US. Residency and ZDR are two switches. Fable 5 and 5.1 keep 30 days unless Anthropic grants an exception.

Does the AWS Region on Claude Platform on AWS pin inference?

No. The Region scopes the gateway, IAM, CloudTrail and billing. Inference is pinned by inference_geo with us or global. Workspace geo is not configurable there and is effectively us.

Does Microsoft Foundry have an EU data zone for Claude?

Not in the documentation read on 18 October 2026. Foundry lists Global Standard and Data Zone Standard (US) for selected Azure-hosted models. Anthropic remains the processor. For EU inference, use Bedrock or Google Cloud.

Sources

1. Anthropic: Data residency (18 October 2026)
2. Anthropic: Pricing (18 October 2026)
3. Anthropic: Claude in Amazon Bedrock (18 October 2026)
4. Anthropic: API and data retention (18 October 2026)
5. AWS: Claude Sonnet 5.5 Model Card (18 October 2026)
6. AWS: Data retention (18 October 2026)
7. Google Cloud: Data residency (18 October 2026)
8. Google Cloud: Claude Sonnet 5.5 (18 October 2026)
9. Google Cloud: Use partner models (18 October 2026)
10. Microsoft Learn: Claude models in Foundry (18 October 2026)
11. Microsoft Learn: Foundry models from partners (18 October 2026)