Track 1 platform and get the weekly governance digest. No credit card required.
This page describes what the document states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability may vary by jurisdiction. Methodology
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.
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 available with Compliance
Regulatory exposure by statute, material risk assessment, vendor due diligence action items, and enforcement precedent. Available on Compliance.
Start Compliance free trial5 important changes detected
7 versions captured · Last updated: June 2026
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 →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 →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 →Monitoring
Cohere has updated this document before.
Monitor includes same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
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 trialCross-platform context
See how other platforms handle Categorical Prohibition on Harmful Use Cases and similar clauses.
Compare across platforms →Governance Monitoring
Structured alerts for policy changes, governance events, and provision updates across 318+ platforms.