7 Total
4 High severity
3 Medium severity
0 Low severity
Summary

Cohere's Usage Policy establishes permitted and prohibited uses for developers and businesses deploying Cohere's AI models and API services. The policy prohibits use cases including generation of content promoting violence, child sexual abuse material, fraud facilitation, unauthorized surveillance systems, and disinformation or coordinated influence operations. Developers must submit use cases for approval, document potential harms in their applications, and obtain additional approval before deployment in healthcare, legal, financial advisory, or minor-facing product categories.

Technical / Legal Breakdown

This document is Cohere's Usage Policy (also referred to as an Acceptable Use Policy), which governs permitted and prohibited uses of Cohere's API, models, and related services, with its legal basis deriving from Cohere's broader Terms of Service. The policy states that developers must outline and obtain approval for their use case to access the Cohere API, must document potential harms of their applications, and must refer to model cards for information about model capabilities and limitations. The policy enumerates categories of strictly prohibited use including generation of content that facilitates violence or physical harm, CSAM, hate speech, harassment, fraud, privacy violations, disinformation, influence operations, unauthorized surveillance, and applications targeting minors without appropriate safeguards; it also identifies a distinct set of use cases requiring special approval, such as medical or health-related applications, legal advice, applications targeting or used by minors, and high-stakes automated decision-making affecting individuals. The policy engages with the EU AI Act, which classifies certain AI applications as high-risk or prohibited, and with applicable consumer protection and data privacy frameworks including GDPR and CCPA, particularly where developers deploy Cohere models in health, legal, financial, and minor-facing contexts. Compliance teams evaluating downstream deployment of Cohere's API should note that the policy places affirmative obligations on developers as operators, including harm documentation, use case approval, and safeguard implementation, creating a tiered accountability structure between Cohere and its API customers.

Institutional Analysis

Institutional analysis available with Compliance

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

Start Compliance free trial

5 important changes detected

7 versions captured · Last updated: June 2026

What changed Cohere's Acceptable Use Policy underwent documentation restructuring on June 11, 2026. The change involved removal of extensive navigation elements and course materials from the policy documentation, while retaining core policy language. The operational policy itself—what uses of Cohere services are permitted or prohibited—appears materially unchanged based on the text provided.
Why this matters This change reflects restructuring of how Cohere's Acceptable Use Policy is presented and organized in its documentation, not substantive modifications to the policy terms themselves. The core policy language—describing what uses of Cohere Services are permitted—remains in place. No new restrictions, permissions, or obligations are introduced by this documentation reorganization.
View full change record →
What changed Cohere's Acceptable Use Policy documentation was reorganized on June 10, 2026, with substantial additions to navigation and educational content in the policy document. The updated document added extensive new sections covering integration tutorials, model deployment guides, fine-tuning instructions, and use-case examples. One sentence in the policy itself was modified, though the core usage policy language applying to all Cohere Services remains substantively unchanged. The operational effect is expanded instructional content alongside the policy framework, though the binding policy requirements themselves were not materially altered.
Why this matters The updated policy documentation adds instructional content and integration guides but does not materially alter the binding usage policy requirements. The core language stating that the Usage Policy applies to all Cohere Services remains unchanged. Users continue to operate under the same policy framework; the change introduces additional reference materials and tutorials rather than new restrictions or rights.
View full change record →

June 10, 2026 unknown

Cohere updated their Cohere Usage Policy on June 10, 2026. Change detected: 2 sentence(s) added, 1 sentence(s) modified. Document contained 41 sentences after update.

View change record →
June 9, 2026 low

Cohere updated its Cohere Usage Policy on June 9, 2026. The change involved adding a single item 'North' to a navigation menu of product models and guides within the document. …

View change record →
May 24, 2026 high

Cohere removed 38 sentences from its Usage Policy on May 24, 2026, substantially reducing the document from a detailed acceptable use policy to a minimal stub containing only navigation and …

View change record →

Recent Provision Changes Jun 11, 2026

7 provisions unchanged.

View full change record →
High — 4 provisions
Medium — 3 provisions

Monitoring

Cohere has updated this document before.

Monitor includes same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Start Monitor free trial Or create a free account →

Compliance Governance Intelligence

Need provision-level monitoring and regulatory mapping?

Compliance includes governance timelines, compliance memos, audit-ready analysis, and full provision tracking.

Start Compliance free trial

Cross-platform context

See how other platforms handle Categorical Prohibition on Harmful Use Cases and similar clauses.

Compare across platforms →

Mapped Governance Frameworks

California AB 2013 AI Training Data Transparency
US-CA
View official text ↗
ePrivacy Directive
European Union
View official text ↗
Archival ProvenanceSource & Archival Record
Last Captured June 11, 2026 00:53 UTC
Capture Method Automated scheduled archival capture
Document ID CA-D-000442
Version ID CA-V-003669
SHA-256 4d0e12d916ee253b550e1c45fc4f827f2b18b2fbec04aaa2d5b578c55ce67f79
✓ Snapshot stored ✓ Text extracted ✓ Change verified ✓ Hash verified

Governance Monitoring

Monitor governance changes across the platforms you rely on.

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

Create free account Compare plans