38 Total
Stay ahead of the changes
Track Anthropic and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Summary
Generated by a model from the captured document; not read by a person

Anthropic's Acceptable Use Policy sets out what users across all product surfaces (Claude.ai, API, cloud integrations) may and may not do with Claude. The policy's most operationally significant provisions establish mandatory qualified human review and AI disclosure requirements before AI-generated recommendations are delivered in high-stakes domains including medical diagnosis, legal advice, credit decisions, employment screening, insurance underwriting, and housing approvals. Additionally, the policy prohibits using model outputs to train other AI models without Anthropic's prior authorization, directly affecting developers who may seek to use API outputs for fine-tuning or distillation purposes.

Analysis

This document is Anthropic's Acceptable Use Policy (AUP), effective November 12, 2026, governing all users who submit inputs to Anthropic's products and services, including Claude.ai, Claude Code, API consumers, cloud provider customers, and end users of third-party integrations. The agreement establishes three tiered categories of restrictions: Universal Usage Standards (absolute prohibitions applicable to all users), High-risk Use Case Requirements (mandating qualified human-in-the-loop review, AI disclosure, and independent safety controls for AI recommendations in legal, medical, financial, credit, insurance, housing, employment, education, healthcare access, public benefits, legal status, and physical action domains), and Additional Use Case Guidelines covering consumer-facing chatbots, products serving minors, agentic deployments, and directory-listed software. Notably, the policy reserves enforcement authority to Anthropic's Safeguards Team, which may warn, throttle, limit, suspend, or terminate access upon suspected violations, and it explicitly prohibits use of model outputs to train competing AI models without prior authorization, a provision with direct implications for developers and enterprise API consumers. The policy engages frameworks including GDPR, CCPA, COPPA, the EU AI Act, FTC Act, HIPAA, and sector-specific regulations governing employment, credit, housing, and financial services, with several High-risk AI Recommendation categories corresponding directly to regulated activities under these frameworks. Compliance obligations vary significantly by jurisdiction, and the policy itself acknowledges that local laws take precedence where they conflict with or add requirements beyond those stated in the AUP.

What this means for you

The agreement establishes that individuals receiving advice or subject to decisions based on High-risk AI Recommendations must be clearly informed that AI was involved in producing the recommendation. Under these terms, operators deploying Claude in high-risk domains are required to maintain qualified human oversight before AI-generated recommendations reach affected individuals, which creates a procedural layer between model output and consequential decisions in areas such as healthcare, credit, employment, and housing. You can report potentially inaccurate, biased, or harmful model outputs by contacting usersafety@anthropic.com or using the in-product feedback mechanism where available.

Institutional Analysis
Stay ahead of the changes

Institutional analysis available with Insight

Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.

1 important change detected

5 versions captured · Latest change detected by ConductAtlas: October 2026

What changed Anthropic updated its Usage Policy effective November 12, 2026, restructuring how it categorizes and enforces acceptable use rules. The policy now explicitly divides requirements into three categories (Universal Standards, High-Risk Use Cases, and Additional Guidelines) and clarifies that prohibitions do not categorically exclude any industry or line of business provided use complies with the policy. The updated language introduces new provisions addressing weapons development, adds a Cyber Verification Program for dual-use research, and modifies enforcement language from 'may throttle, suspend, or terminate' to 'may warn you or throttle, limit, suspend, or terminate' access.
Why this matters The updated policy clarifies that Anthropic's acceptable use rules apply to all users of its products and services, including API developers, cloud customers, and app users. The policy now explicitly prohibits weapons development and related activities, and introduces a Cyber Verification Program allowing researchers to apply for adjusted safeguards for authorized dual-use work. Enforcement procedures now include warnings and throttling in addition to suspension or termination. You can apply for the Cyber Verification Program or Life Sciences Verification Program if your work involves authorized dual-use or high-risk use cases covered by real-time safeguards.
View full change record →
Clauses withheld

We withheld clauses we had published from this document. Each withholding is recorded in our correction log:

Provisions
Generated by a model from the captured document; not read by a person
Stay ahead of the changes

Monitoring

Anthropic has updated this document before. Monitor includes alerts from a daily check, structured change summaries, and monitoring for up to 20 platforms.

Stay ahead of the changes

Governance Intelligence

Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.

Cross-platform context

See how other platforms handle Prohibition on ban circumvention via alternate accounts and similar clauses.

Compare across platforms →

Related Analysis

Privacy · April 14, 2026
Deleted Claude Conversations Aren't Gone for 30 Days

Anthropic is more transparent than most AI companies about data retention. Here's exactly what happens when you delete your data, and how t…

Archival ProvenanceSource & Archival Record
This version captured October 21, 2026 00:10 UTC
Last successful capture October 21, 2026 00:10 UTC
Date stated by the document November 12, 2026 (as printed in this version)
Capture Method Automated scheduled archival capture
Document ID CA-D-000013
Version ID CA-V-007718
SHA-256 (extracted text, extractor v5) 3ab46da61f459a866c57f7576b8dbbf567f5b0d8cd69b2ce0507aec4f3f21256
Archived bytes SHA-256 (anchor) 3f4efd9295fe624bb532af54145fcf3f6ef0ac6919b207aef5ff1f9ea2c4affe
✓ Snapshot stored ✓ Archived bytes anchored (verified Oct. 21, 2026)

Governance Monitoring

Monitor governance changes across the platforms you rely on.

Structured alerts for policy changes, governance events, and provision updates across 343 platforms.

Start monitoring → Compare plans