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

1 important change detected

2 versions captured · Last updated: May 2026

What changed 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 heading elements. The previous version included universal requirements prohibiting specific activities such as child exploitation, sexually explicit content involving minors, and defined enforcement mechanisms including restriction, suspension, or termination of access. The updated version retains only document structure and no substantive policy content, meaning Cohere Services users no longer have a posted acceptable use policy to reference or rely upon.
Why this matters The updated policy removes all substantive acceptable use requirements that were previously posted and enforceable. Users no longer have a referenced standard defining what conduct is prohibited on the platform. The removal of enforcement procedures means users cannot verify what conduct may trigger access restriction, suspension, or termination. The elimination of the child safety and sexually explicit content prohibitions from the posted policy creates uncertainty about whether these protections remain in effect through other terms or have been abandoned.
View full change record →

Recent Provision Changes May 24, 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 May 24, 2026 00:42 UTC
Capture Method Automated scheduled archival capture
Document ID CA-D-000442
Version ID CA-V-002946
SHA-256 23e30e1b4082491490f28973d75dbfd7b9856939f2092a4012d2eaaad1e225a3
✓ 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