Provision record
Mistral AI · Mistral AI Data Processing Addendum · View original document ↗

Breach notification must include specified content elements

Common · 267 of 343 platforms
Stay ahead of the changes
Track Mistral AI 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 Mistral AI'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

Baseten

Customer agrees to: notify Baseten in advance; and in good faith, consult with Baseten and consider any clarifications or corrections Baseten may reasonably recommend or request to any such notification...

Kling AI

Any such information that is meant to be shown to the public on our platform will be disclosed publicly. This Policy does not apply to the use of any such information by third parties after it is uploaded and displayed publicly on Kling AI.

Postman

Any content made public will be publicly accessible through the internet and may be crawled and indexed by search engines.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
This notification shall include: The name and contact details of Mistral AI's point of contact...the nature of the Personal Data Breach...A description of the measures Customer could take to mitigate...

Excerpt from Mistral AI's Data Processing Addendum

Provision details

Document information
Document
Mistral AI Data Processing Addendum
Entity
Mistral AI
Date stated by the document
July 27, 2026
As printed in Mistral AI’s text (version CA-V-006754), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
May 11, 2026
Text quoted from version
CA-V-006754, captured Sept. 11, 2026
Record ID
CA-P-061942
Document ID
CA-D-000771
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-006754)
60acff3547f5a04d22bf895f1b248ecef43e99bf66252bd867ef8c9bee93e94f
Analysis generated
May 11, 2026 11:22 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-006754, captured Sept. 11, 2026 (checked Oct. 5, 2026)
Citation Record
Entity: Mistral AI
Document: Mistral AI Data Processing Addendum
Record ID: CA-P-061942
Version: CA-V-006754
Captured: 2026-09-11 00:55:39 UTC
SHA-256: 60acff3547f5a04d…
URL: https://conductatlas.com/platform/mistral-ai/mistral-ai-data-processing-addendum/provision/CA-P-061942/breach-notification-must-include-specified-content-elements/
Accessed: Nov. 1, 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 Mistral AI's Breach notification must include specified content elements clause do?

The clause states: “This notification shall include: The name and contact details of Mistral AI's point of contact...the nature of the Personal Data Breach...A description of the measures Customer could take to mitigate...”

How many platforms have this type of clause?

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

Is ConductAtlas affiliated with Mistral AI?

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