Provision record
Cohere · Cohere SaaS Agreement · View original document ↗

Recipient must safeguard Confidential Information with at least own-data standard

Common · 290 of 343 platforms
Stay ahead of the changes
Track Cohere and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what Cohere's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

How other platforms handle this

Teladoc

if any information you provide to Teladoc Health becomes inaccurate, incomplete or otherwise false or misleading, you will immediately notify Teladoc Health

Credit Karma

We are not responsible for any information that you agree to share with third parties in connection with Third Party Content or Third Party Services.

Kling AI

If you access third party services through Kling AI, you must comply with any terms and conditions applicable to those services.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
Each Party will take all necessary precautions and measures to safeguard the other Party's Confidential Information...which will in any event be at least as stringent as the precautions that the Recipient takes to protect its own Confidential Information...

Excerpt from Cohere's SaaS Agreement

Provision details

Document information
Document
Cohere SaaS Agreement
Entity
Cohere
Date stated by the document
April 8, 2025
As printed in Cohere’s text (version CA-V-007600), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
May 11, 2026
Text quoted from version
CA-V-007300, captured Oct. 2, 2026
Record ID
CA-P-070050
Document ID
CA-D-000768
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-007300)
8e59f8aa83e4ccce2bd88ecb7b36974d1bc7b742ade23d408e6e6a0a7b84583d
Analysis generated
May 11, 2026 11:52 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-007300, captured Oct. 2, 2026 (checked Oct. 5, 2026)
Not the current version. The document's current version is CA-V-007600, captured Oct. 16, 2026; this clause has not been re-checked against it.
Citation Record
Entity: Cohere
Document: Cohere SaaS Agreement
Record ID: CA-P-070050
Version: CA-V-007300
Captured: 2026-10-02 00:59:20 UTC
SHA-256: 8e59f8aa83e4ccce…
URL: https://conductatlas.com/platform/cohere/cohere-saas-agreement/provision/CA-P-070050/recipient-must-safeguard-confidential-information-with-at-least-own-data-standard/
Accessed: Nov. 3, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Cohere's Recipient must safeguard Confidential Information with at least own-data standard clause do?

The clause states: “Each Party will take all necessary precautions and measures to safeguard the other Party's Confidential Information...which will in any event be at least as stringent as the precautions that the Recipient takes to protect its own Confidential Information...”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 290 platforms. See the full comparison.

Is ConductAtlas affiliated with Cohere?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cohere.