Version history

Cohere updated their Cohere Enterprise Data Commitments on September 18, 2026. Change detected: 1 sentence(s) removed, 1 sentence(s) modified. Document contained 97 sentences after update.

Cohere updated their Cohere Enterprise Data Commitments on September 17, 2026. Change detected: 2 sentence(s) modified. Document contained 98 sentences after update.

Cohere updated their Cohere Enterprise Data Commitments on September 15, 2026. Change detected: 24 sentence(s) added, 23 sentence(s) removed, 2 sentence(s) modified. Document contained 98 sentences after update.

Cohere updated their Cohere Enterprise Data Commitments on September 13, 2026. Change detected: 23 sentence(s) added, 23 sentence(s) removed, 1 sentence(s) modified. Document contained 97 sentences after update.

Cohere updated their Cohere Enterprise Data Commitments on September 11, 2026. Change detected: 1 sentence(s) modified. Document contained 97 sentences after update.

Cohere restructured its Enterprise Data Commitments document in an update detected on September 10, 2026. The revised version reorganizes and expands existing data governance disclosures including opt-out controls for training data use, logging and monitoring practices, data retention timelines (30-day auto-deletion for most logs), personal information filtering, and compliance certification information. The operational change is primarily organizational and clarifying; core protections and controls remain substantively similar to the prior language.

In an update detected on September 9, 2026, Cohere restructured its Enterprise Data Commitments document. The revised language reorders and reframes existing data protection provisions, adding an introductory statement that 'Cohere maintains robust controls to protect enterprise data and respect our enterprise customers' rights regarding their data.' The substantive terms regarding opt-out controls, data retention, logging, monitoring, and compliance certifications remain operationally consistent with the prior version. The change does not alter the core data handling practices, retention periods, or deployment options available to enterprise customers.

Cohere restructured its Enterprise Data Commitments document detected on August 30, 2026. The company removed and re-added substantially identical language describing its data handling practices across deployment options, logging and monitoring procedures, data retention controls, and compliance certifications. The operational difference is minimal; the revised version adds an opening statement that 'Cohere maintains robust controls to protect enterprise data and respect our enterprise customers' rights regarding their data,' but the core provisions regarding opt-out mechanisms, 30-day deletion timelines, and flagged-content retention remain substantively unchanged.

Cohere revised its product lineup descriptions in the Enterprise Data Commitments document detected on August 28, 2026. The updated text removes the 'New' label from several existing models (Command, Transcribe, North Mini Code) and adds references to a new Parse model for document parsing. This is a product catalog update with no material change to data governance, privacy commitments, or enterprise terms.

In an update detected on August 27, 2026, Cohere reorganized and expanded its Enterprise Data Commitments documentation. The change appears to restructure existing content around data control options, opt-out mechanisms for training data, logging and monitoring practices, data retention timelines, and compliance resources. The practical effect is a more detailed explanation of how Cohere handles customer data across its SaaS Platform and deployment options, with explicit disclosure of data retention periods (30 days for logged prompts and generations), filtering of personal information before training use, and the ability to opt out of training data use via dashboard settings.

The detected change appears to involve restructuring of Cohere's website navigation and featured content sections. The diff shows modifications to header navigation, research initiatives, and blog featured content, with additions of sections on Aya Models, Open Science Community, and Catalyst Grants. The operational impact on the Enterprise Data Commitments document itself is unclear from the provided diff fragments, which appear to show website navigation changes rather than substantive policy modifications.

Cohere's Enterprise Data Commitments document was restructured in an update detected on August 25, 2026. The substantive provisions regarding data control, opt-out mechanisms, logging, monitoring, data retention, and privacy compliance appear to remain materially unchanged; however, the document was reformatted with added introductory language stating 'Cohere maintains robust controls to protect enterprise data and respect our enterprise customers' rights regarding their data.' The practical operational effect of the restructuring on enterprise customers' data governance is unclear from the diff alone.

Cohere updated marketing descriptions for two products on its website. The Command product description was expanded to state 'High-performance generative AI models for real-world applications', and the Model Vault description was revised to state 'Model Vault provides fully-isolated, performant inference with Saas simplicity'. These are product marketing updates with no operational change to the underlying service terms or data governance policies.

In an update detected on August 18, 2026, Cohere revised its Enterprise Data Commitments to explicitly describe data handling controls across its deployment options. The updated terms state that in third-party cloud and private deployments, Cohere does not receive customer inputs or outputs; that users can opt out of data use in training via dashboard settings; that prompts and generations are automatically deleted after 30 days unless flagged for policy violations or retained under contract; and that Cohere logs and monitors SaaS Platform usage for compliance and security. The change establishes specific operational procedures for data retention, logging, and user controls rather than materially altering the substantive scope of data collection or use.

Cohere's Enterprise Data Commitments document was restructured in an update detected on August 16, 2026, but the substantive content describing data controls, opt-out mechanisms, logging practices, retention policies, and compliance resources remained materially the same. The change involved reorganizing and rephrasing the same commitments rather than adding new restrictions or protections. No material change to the operational terms governing enterprise customer data handling was detected.

Cohere's website navigation and footer structure were reorganized in an update detected on August 14, 2026. The changes involved restructuring product pages, consolidating navigation menus, and removing email subscription language ('You can unsubscribe at any time'). These appear to be formatting and navigation changes to the public website rather than modifications to substantive data governance or privacy commitments stated in the Enterprise Data Commitments document itself.

The detected change to Cohere's Enterprise Data Commitments document on August 12, 2026 appears to be a minor navigation or formatting adjustment. The specific modification involved adding a 'Skip to content' link at the beginning of the document, which is a standard web accessibility feature. This change does not alter Cohere's data commitments, obligations, or the substantive terms governing enterprise customer relationships.

Cohere's Enterprise Data Commitments page was restructured in an update detected on August 8, 2026. The opening statement, 'Cohere maintains robust controls to protect enterprise data and respect our enterprise customers' rights regarding their data,' remains present but the document layout was significantly reorganized to feature product listings, navigation menus, and a newsletter signup form. The substantive content of the data commitments themselves does not appear in the provided diff hunks, so the operational scope of any policy changes cannot be determined from this change alone.