8 Total
5 High severity
3 Medium severity
0 Low severity
Summary

Cohere's Usage Policy sets out the rules developers and businesses must follow when using Cohere's AI models and API. The single most important thing for developers to know is that they must describe and get approval for their specific use case before accessing the API, and they are personally responsible if their applications cause harm — including any harm caused by their own end users. If you are building a product with Cohere's technology, review the prohibited use categories carefully, as violations can result in termination of access.

Technical Summary

This document is Cohere's Usage Policy (Acceptable Use Policy) governing access to and use of the Cohere API and related AI models, with legal basis established through contractual agreement at the point of API access. The most significant obligations created include a mandatory use-case disclosure and approval requirement prior to API access, downstream operator accountability for ensuring end-user compliance, and affirmative prohibitions on specific categories of harmful outputs. Notable provisions that deviate from industry standard include an explicit prohibition on generating 'Non-Consensual Intimate Imagery (NCII),' a broad restriction on AI-generated content for 'influence operations' and 'disinformation,' and a requirement that developers document potential harms of their applications — an affirmative risk-assessment obligation uncommon in standard API ToS. The policy engages the EU AI Act (particularly high-risk AI system provisions), FTC Act Section 5 on unfair or deceptive practices, and GDPR/CCPA through its privacy violation prohibitions; compliance teams should note that the policy's prohibition on 'surveillance' and 'tracking individuals without their knowledge' may interact with obligations under ECPA and state wiretapping statutes, and the broad 'political content' restriction warrants review for platforms operating in regulated electoral or political advertising contexts.

Evidence Provenance
Captured April 29, 2026 08:11 UTC
Document ID CA-D-000442
Version ID CA-V-001020
Wayback Machine View archived versions →
SHA-256 6a378336939dc282ba5c613e4109653e501afb610fdef634c0718fd7e6692cd7
✓ Snapshot stored ✓ Text extracted ✓ Change verified ✓ Cryptographically signed
Institutional Analysis

🔒 Institutional analysis locked

Regulatory exposure by statute, material risk assessment, vendor due diligence action items, and enforcement precedent. Available on Professional.

Upgrade to Professional — $149/mo
Change Timeline
View full version history (0 captures) →
High Severity — 5 provisions
Medium Severity — 3 provisions

Cross-platform context

See how other platforms handle Developer Liability for End-User Misuse and similar clauses.

Compare across platforms →