---
type: "post"
id: "anthropic-s-supported-regions-policy-effective-november-12-fa0e7d"
slug: "anthropic-s-supported-regions-policy-effective-november-12-fa0e7d"
title: "Anthropic’s Supported Regions Policy, effective November 12, 2026, limits access to its apps, API"
description: "Anthropic’s Supported Regions Policy, effective November 12, 2026, limits access to its apps, API, developer platform, and Claude models to listed countries and regions."
retrieval_nugget: "Anthropic’s Supported Regions Policy, effective November 12, 2026, limits access to its apps, API, developer platform, and Claude models to listed countries and regions. Eligibility also depends on where an organization is incorporated, headquartered, owned, or controlled, so a team’s location alone may not settle whether it can use Claude."
published_at: "2026-11-11"
updated_at: "2026-11-11"
record_date: "2026-11-11"
date_kind: "published_at"
topics: ["claude","anthropic","claude-code"]
entities: ["Anthropic","Claude.ai","Claude Code","Cowork","Claude API"]
related_patterns: []
novelty_label: "new_fact"
what_changed: "Anthropic’s new supported-regions policy limits Claude, Claude Code, Cowork and API access to 185 countries and regions, including restrictions based on where organizations are incorporated, headquartered or controlled."
prior_refs: []
source_url: "https://www.anthropic.com/legal/supported-regions"
source_urls: ["https://www.anthropic.com/legal/supported-regions"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:anthropic-s-supported-regions-policy-effective-november-12-fa0e7d"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/anthropic-s-supported-regions-policy-effective-november-12-fa0e7d/","markdown":"https://newruntime.com/posts/anthropic-s-supported-regions-policy-effective-november-12-fa0e7d.md","json":"https://newruntime.com/posts/anthropic-s-supported-regions-policy-effective-november-12-fa0e7d.json"}
markdown_url: "https://newruntime.com/posts/anthropic-s-supported-regions-policy-effective-november-12-fa0e7d.md"
---

# Anthropic’s Supported Regions Policy, effective November 12, 2026, limits access to its apps, API

## Retrieval answer

Anthropic’s Supported Regions Policy, effective November 12, 2026, limits access to its apps, API, developer platform, and Claude models to listed countries and regions. Eligibility also depends on where an organization is incorporated, headquartered, owned, or controlled, so a team’s location alone may not settle whether it can use Claude.

## Summary
Anthropic’s Supported Regions Policy, effective November 12, 2026, limits access to its apps, API, developer platform, and Claude models to listed countries and regions. Eligibility also depends on where an organization is incorporated, headquartered, owned, or controlled, so a team’s location alone may not settle whether it can use Claude.

## What happened
Anthropic’s Supported Regions Policy says its products and services are available only in the countries and regions listed in the policy. It names Claude.ai, Claude Code, Cowork, the API and developer platform, and Claude models offered through cloud platforms and authorized resellers. The policy is marked effective November 12, 2026. It also says territories and dependencies of a listed country are supported, giving Puerto Rico as an example of a United States territory. Any country or region not listed is unsupported.

The restrictions apply to people physically located in an unsupported region, including users and personnel of otherwise supported entities. They also apply to entities incorporated or headquartered in an unsupported region and their users or personnel, regardless of where those individuals are physically located. A third category covers entities majority-owned or controlled, directly or indirectly, by people or entities in unsupported regions; their users and personnel are included regardless of their physical location. The listed ownership threshold is majority ownership, not a general test based only on an employee’s current address.

The policy includes a long country-and-region list. Among the listed locations are the United States, United Kingdom, Canada, India, Japan, South Korea, Taiwan, Ukraine with specified territorial exceptions, and many countries across Europe, Africa, Asia, and the Americas. The policy explicitly excludes Crimea, Donetsk, Kherson, Luhansk, and Zaporizhzhia regions from its Ukraine listing. Its rule is list-based: locations absent from the list are unsupported. The policy page does not state that this list is a sanctions list or explain a country-by-country rationale.

For builders, the consequence is that access eligibility can involve more than an individual’s network location. A person working from a supported country may still fall within a restriction if their employer is incorporated or headquartered in an unsupported region, or if the organization meets the stated ownership or control condition. The policy describes which use is unsupported; it does not, in the text here, specify a technical enforcement mechanism, an account-review process, or an exception procedure.

## What the archive adds
New Runtime’s earlier coverage has discussed Claude Code Projects as coordinated work environments ([October 11, 2026 note](https://newruntime.com/posts/projects-redesigned-from-folder-to-conversation-analysis-2e419b/)), but that is a different product story, not prior coverage of regional eligibility. This policy is a new access-related thread in the archive.

## Trend signal
This does not yet fit a pattern New Runtime tracks. The policy establishes an eligibility boundary for Anthropic services, but it does not materially support one of the tracked patterns about agent architecture, interoperability, runtime security, or work organization.

## Why now
The policy itself gives November 12, 2026 as its effective date. That date makes the access terms operationally relevant for teams preparing deployments or renewals around the change; the policy does not explain why Anthropic selected this timing.

## Why it matters
Teams often treat model access as a property of an account, API key, or network location. Anthropic’s policy makes that assumption unsafe for organizations whose employees, headquarters, incorporation, ownership, or control span multiple jurisdictions. A deployment that works for an individual developer may not be eligible for the organization employing them, and a supported corporate location does not override the stated restriction on personnel of an unsupported entity.

That creates a due-diligence task for engineering and procurement teams before Claude becomes embedded in a workflow. They need to understand which legal entity will use the service, where it is incorporated and headquartered, and whether the ownership or control criteria could apply. The policy does not describe how Anthropic verifies each condition, so teams should not infer that a successful login or API call proves eligibility. For multi-vendor systems, keeping provider access separable can also reduce disruption if eligibility changes or is disputed.

## What happens next
- **Teams using Claude through organizations with cross-border ownership will seek eligibility clarification before expanding deployments.** (3 months, 65%). Watch for: public guidance from Anthropic on how it interprets majority ownership and control.

## Limits and uncertainty
The policy defines unsupported use, but it does not explain in this policy how Anthropic will determine a user’s location, verify incorporation or headquarters, assess indirect ownership or control, or handle disputed cases. It does not give an exception or appeal process, nor does it quantify how many current users or organizations may be affected. The effective date is stated, but the policy does not describe a migration period or the consequences for existing accounts. These points should not be treated as confirmed enforcement details.

## Reader takeaway
Treat Claude eligibility as an organizational question, not just a question of where a developer is connecting from. Before building a workflow around Anthropic services, compare the relevant people and legal entities against the policy’s location, incorporation, headquarters, ownership, and control criteria—and ask Anthropic for clarification where the application is uncertain.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Claude](https://newruntime.com/topics/claude.md): Explore the claude topic hub.
- topic hub: [Anthropic](https://newruntime.com/topics/anthropic.md): Explore the anthropic topic hub.
- topic hub: [Claude Code](https://newruntime.com/topics/claude-code.md): Explore the claude-code topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)