AI vendors and your data

Vendors146Answers427

146 vendors · 427 answers

Data residency changed Anthropic, Oct 26, 2026

Anthropic · Oct 26, 2026 · 8 added, 6 removed · seen by the weekly check

The pageAll Anthropic terms
  1. Added: Workspace geo: Controls where data is stored at rest and where endpoint processing (such as image transcoding and code execution) occurs. Configured at the workspace level in the Claude Console .
  2. Removed: Workspace geo: Controls where data is stored at rest and where endpoint processing (such as image transcoding and code execution) happens. Configured at the workspace level in the Claude Console .
  3. Added: The inference_geo parameter is available on the Claude API (first-party), Claude Platform on AWS , and Claude Models on Google Cloud (Anthropic managed) . On Amazon Bedrock and Claude Models on Google Cloud (Google managed), the inference region is determined by the endpoint URL or inference profile, so inference_geo is not applicable. On Claude in Microsoft Foundry , inference_geo is likewise not applicable: deployments hosted on Azure can instead use the US Data Zone Standard deployment type, which keeps inference within the United States. The inference_geo parameter is also not available through the OpenAI SDK compatibility endpoint .
  4. Removed: The inference_geo parameter is available on the Claude API (first-party) and Claude Platform on AWS . On Amazon Bedrock and Google Cloud, the inference region is determined by the endpoint URL or inference profile, so inference_geo is not applicable. On Claude in Microsoft Foundry , inference_geo is likewise not applicable: deployments hosted on Azure can instead use the US Data Zone Standard deployment type, which keeps inference within the United States. The inference_geo parameter is also not available through the OpenAI SDK compatibility endpoint .
  5. Added: Claude Models on Google Cloud (Anthropic managed): Every workspace allows all inference geos and uses "global" as its default inference geo. The Claude Console shows both settings as read-only. For US-only inference, set inference_geo: "us" on each request.
  6. Added: Go to Workspaces in the Claude Console ( platform.claude.com/settings/workspaces ).
  7. Removed: In the Console, go to the Workspaces page ( platform.claude.com/settings/workspaces ).
  8. Added: Claude Models on Google Cloud (Anthropic managed): Workspace geo is not configurable. Every workspace uses "us" as its workspace geo, and the Workspace geo field doesn't appear in the Claude Console.
  9. Added: Older models: Don't support inference_geo (see Model availability ). Standard pricing applies. Requests that include the parameter return a 400 error.
  10. Added: This pricing applies to the Claude API (first-party), Claude Platform on AWS, and Claude Models on Google Cloud (Anthropic managed). On Claude in Microsoft Foundry, the same 1.1x multiplier applies to deployments hosted on Azure that use the US Data Zone Standard deployment type. Partner-operated platforms, Bedrock and Claude Models on Google Cloud (Google managed), have their own regional pricing. See Data residency pricing for details.
  11. Removed: Older models: Don't support inference_geo (see Model availability ); standard pricing applies. Requests that include the parameter return a 400 error.
  12. Removed: This pricing applies to the Claude API (first-party) and Claude Platform on AWS. On Claude in Microsoft Foundry, the same 1.1x multiplier applies to deployments hosted on Azure that use the US Data Zone Standard deployment type. Partner-operated platforms (Bedrock and Google Cloud) have their own regional pricing. See Data residency pricing for details.
  13. Added: If your organization previously opted out of global routing to keep inference in the US, your workspace has been automatically configured with allowed_inference_geos: ["us"] and default_inference_geo: "us" . No code changes are needed. Your existing data residency requirements continue to be enforced through the new geo controls.
  14. Removed: If your organization previously opted out of global routing to keep inference in the US, your workspace has been automatically configured with allowed_inference_geos: ["us"] and default_inference_geo: "us" . No code changes are required. Your existing data residency requirements continue to be enforced through the new geo controls.
About this change
Page
platform.claude.com/docs/en/manage-claude/data-residency
Kind
Documentation
Text hash
3e84747784d5 to ed12e2e41091
Dated by
the weekly check that first read the new text