Data use, training & retention
How this is scored
What happens to prompts, uploaded files, connected data and outputs: whether any of it trains a model (the vendor's or a model provider's), how long it is kept and where logs live, whether zero-retention is available, and whether a data processing agreement covers it.
0 — No statement on training or retention; the privacy policy is a website policy that does not cover the product.
3 — A general statement that business data is "not used for training", with no word on retention, on the model providers behind the product or on logs.
5 — Business data excluded from training by contract, retention periods stated for chats and files, and a DPA offered to business customers.
8 — No-training commitments stated for the vendor and every model provider it routes to, retention configurable by the admin (including deletion of chat history), zero-data-retention terms with the model providers named, and abuse-monitoring retention described.
10 — Data use fully accounted for: training, retention, logging and abuse monitoring stated per model provider, customer-controlled retention and deletion with an audit trail, outputs and connected data treated as customer data in the DPA, and an independent audit (SOC 2, ISO 27001 or ISO 42001) covering the product.
The Head of IT
Retention is documented in real detail — chats kept until the user deletes the conversation or the account, API inputs and outputs held for thirty rolling days for abuse monitoring, fine-tuning data until deleted — and a data processing agreement with controller and processor roles is published. But the default is that inputs and outputs train Mistral's models unless opted out, in-app thumbs feedback is used for training even under business terms, and the vendor states zero-data-retention is unavailable for Vibe Work and Chat regardless of plan, applying only to stateless API calls on pay-as-you-go with approval at Mistral's discretion. I could not sign this without a fight with our data protection officer. 5 6 7