Mistral now trains on user input by default outside enterprise tier

What happened

A Hacker News submission that reached the site's front page reports that Mistral now feeds user input into model training by default, with the enterprise tier described as the exception. The post links to a help article in Mistral's Trust, Security and Compliance collection titled "Can I opt out of my input or output data being used for training?", which explains how users can keep their data out of future models.

According to that article, conversations, documents and other content users hand over can, in certain circumstances, end up in Mistral's model training programmes. No single account-wide switch is described. Instead, the opt-out steps differ by product and surface.

The opt-out procedures

The help article documents three separate paths:

• Vibe data training can be disabled through the Admin panel.
• Vibe users on iOS and Android follow a different procedure inside the mobile apps.
• Mistral Studio and its related API services can likewise be excluded from training via the Admin panel.

The structure implies training is active unless someone intervenes on each surface. Nothing in the article indicates one toggle covers every product, so a user who opts out of Vibe on the web could still be contributing data from the mobile app, Studio sessions or API calls until they repeat the steps there.

What is documented and what is reported

The enterprise exemption appears in the Hacker News headline; the quoted portion of the help text does not spell out tier-based differences. The help centre lists related articles on activating Zero Data Retention, exercising GDPR rights and how the Memories feature handles data, which suggests stronger controls exist for accounts that need them. The precise scope of the enterprise carve-out is therefore best treated as reported by the Hacker News post rather than confirmed by the documentation itself.

Why it matters

Default-on training shifts the burden of privacy from provider to user. Anyone pasting source code, internal documents or client material into Vibe or Mistral Studio may now be supplying that content to training runs unless they act. API users are the more consequential group: developers integrating Mistral models often assume prompts and completions stay out of training unless they explicitly opt in, and this arrangement, as summarised by the Hacker News post, reverses that expectation, with the switch tucked into an Admin panel rather than the API itself.

Fragmented opt-outs compound the risk. Because each surface carries its own procedure, the realistic failure mode is partial coverage: a user confident they have opted out on desktop while mobile or API traffic keeps feeding future models.

How the change surfaced matters too. The help article is procedural documentation, not an announcement, and the attention came from a community thread rather than a Mistral blog post or email. For users, that is the practical lesson: data-handling defaults at AI providers can change inside support pages, and the help centre, including its articles on Zero Data Retention and GDPR rights, is worth reading alongside any model's pricing page.