Intercom, a US-based user support platform, is listed as a subprocessor for all Anthropic products except Claude for Government, meaning government product users' support interactions are not routed through Intercom.
This analysis describes what Anthropic's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes a product-specific carve-out that differentiates data handling for government deployments from all other Anthropic products, indicating that user support data for Claude for Government is processed through a different mechanism not identified in this document.
Interpretive note: The document does not identify what support processing mechanism is used for Claude for Government in place of Intercom, leaving the alternative processing arrangement undisclosed in this public document.
This provision establishes that Claude for Government users do not have their support interactions processed by Intercom, while users of all other Anthropic products do, with support data for those users processed in the United States by Intercom.
Cross-platform context
See how other platforms handle Intercom Exclusion from Claude for Government and similar clauses.
Compare across platforms →Monitoring
Anthropic has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Intercom | User support | United States | Products: All Products except Claude for Government.— Excerpt from Anthropic's Anthropic Sub-Processors
1) REGULATORY LANDSCAPE: The exclusion of Intercom from Claude for Government engages federal data handling requirements applicable to government cloud deployments, including FedRAMP authorization standards, FISMA compliance obligations, and potentially ITAR or CUI handling requirements depending on the agency deployment context. The relevant enforcement framework is federal rather than state or EU-based for this specific carve-out. 2) GOVERNANCE EXPOSURE: Medium for government customers. The document discloses the exclusion but does not identify the alternative support processing mechanism used for Claude for Government, creating a documentation gap for agency security officers and ATO reviewers who need to enumerate all data processors in their system security plans. 3) JURISDICTION FLAGS: This carve-out is primarily relevant to US federal government agency customers and contractors operating under FedRAMP, FISMA, or agency-specific data handling mandates. State and local government customers should independently confirm whether their deployments qualify for or are subject to the Claude for Government product tier. 4) CONTRACT AND VENDOR IMPLICATIONS: Government agency procurement and security teams should request documentation from Anthropic identifying the alternative support processing mechanism used in place of Intercom for Claude for Government. The absence of this information in the public subprocessor list represents a gap that should be resolved through contractual or pre-authorization inquiry. 5) COMPLIANCE CONSIDERATIONS: Agency system security plan (SSP) authors should note that Intercom is explicitly excluded from Claude for Government and should request the complete subprocessor list for that product tier from Anthropic through appropriate procurement channels. ATO reviewers should confirm that no Intercom data flows exist in the government deployment architecture.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 3 platforms + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision establishes a product-specific carve-out that differentiates data handling for government deployments from all other Anthropic products, indicating that user support data for Claude for Government is processed through a different mechanism not identified in this document.
This provision establishes that Claude for Government users do not have their support interactions processed by Intercom, while users of all other Anthropic products do, with support data for those users processed in the United States by Intercom.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Anthropic.