
Claude Code operates globally in countries supported by Anthropic (Supported Countries and Regions list). Key markets: US, Canada, UK, EU (all member states), Japan, South Korea, Australia, New Zealand, India, most of Latin America. NOT available in mainland China, Russia, Belarus, Iran, Cuba, Syria, North Korea, or other OFAC-sanctioned regions. EU data residency is available exclusively on Enterprise plans (Anthropic API EU region + Bedrock Frankfurt/Ireland + Vertex AI europe-west1/europe-west4).
Claude Code is included in Claude subscription plans: Pro (USD 17/mo with annual billing, USD 20/mo monthly), Max 5x (USD 100/mo), Max 20x (USD 200/mo), and in Team and Enterprise premium seats. With an Anthropic Console account, Claude Code consumes API tokens at standard API pricing. Fast mode for Opus 4.8 on consumption-based plans: USD 30 / USD 150 per 1M tokens (input/output).
Claude Code runs locally in the terminal and talks directly to the model APIs, with no backend server or remote code index. It asks permission before changing files or running commands. Team and Enterprise plans (premium seats) and Claude Code Enterprise are available.
Claude Code runs locally in the user's terminal and communicates directly with the Anthropic API (Claude API), Amazon Bedrock, or Google Vertex AI - with no intermediary backends or remote code index. Zero Data Retention (ZDR): default 30-day retention of prompts/responses for all plans; Enterprise customers can negotiate ZDR with retention limited to 24h (for abuse detection only). Training on data: user code is NOT used to train Anthropic models by default (opt-in only). Tool permissions: every shell command execution, file edit, or MCP call requires user consent (permission prompt) - --allowlist / --deny-list modes exist along with auto-approve for whitelisted commands. Authentication: OAuth 2.0 (Claude Console) or API key. SSO/SAML + SCIM available only on Team/Enterprise plans. Compliance: SOC 2 Type II, ISO 27001, ISO 42001, HIPAA BAA (Enterprise), GDPR-ready, CCPA. Sub-agents run in isolated subprocesses with their own context window - they have no access to the main context or session.
