Mistral Trains on User Data by Default: How to Opt Out

Mistral says standard Vibe users are not opted out of model training by default, while Vibe Enterprise customers are opted out by default. Standard users can disable training in their settings, and Enterprise administrators can manage the opt-in toggle centrally.

The Hacker News headline that surfaced the documentation—“Mistral now trains on user input by default, except on enterprise tier”—needs one qualification. Mistral’s official help page makes that Enterprise distinction specifically for Vibe, the product formerly called Le Chat. Studio Free data may be used for training, while pay-as-you-go customers have the right to opt out.

What Mistral currently says

Mistral’s help articles were marked “updated yesterday” when checked on September 2. They say conversations, documents, and other user-provided input and output may “in certain cases” be included in model-training programs. Because the pages publish no revision history or effective date, they prove the current rule, not that Mistral first flipped the default on August 31 or September 1.

Service or tier	Current training setting	What the user must do
Vibe, non-Enterprise	Not opted out by default	Disable training in the Admin panel or mobile app
Vibe Enterprise	Opted out by default	An administrator controls any opt-in
Mistral Studio Free	Input and output may be used for training	Treat Free as evaluation-only unless this use is acceptable
Studio/API pay-as-you-go	Customers have the right to opt out	Disable “Anonymous improvement data” in the Admin panel

Mistral also states that documents attached or uploaded to Vibe are input data. After an opt-out is confirmed, the company says it no longer uses the affected input or output for training.

Feedback is a separate exception. Mistral says that submitting thumbs-up or thumbs-down feedback with a comment authorizes use of the rating, input, and output to improve model behavior regardless of plan. Enterprise administrators should therefore pair the organization setting with staff guidance about feedback tools.

There is no accompanying token-price, subscription-price, or rate-card change. Opting out is presented as an account setting, not a paid feature. The commercial impact is therefore about governance and procurement rather than a new usage charge.

The official API rate documentation still lists Mistral Large 3 at $0.50 input, $0.05 cached input, and $1.50 output per million tokens; Mistral Medium 3.5 at $1.50, $0.15 cached, and $7.50; and Mistral Small 4 at $0.15, $0.015 cached, and $0.60. The canonical table above also carries the current Codestral and Ministral 3 rows from that same maintained source.

How to opt out now

For Vibe on the web, open the Mistral Admin panel, select Vibe under Manage, find Privacy, and disable Allow your interactions to be used to train our models.

For Vibe on iOS or Android, open Settings, choose Data & Account Controls under Account, and deselect Enable data sharing.

For Mistral Studio and related API services, open the Admin panel’s Privacy menu and disable the toggle under Anonymous improvement data. Free and pay-as-you-go have different published positions, so verify the exact organization and plan rather than inferring the setting from whether the account is paid.

Do both checks if your organization uses both products. Mistral explicitly warns that the Vibe and API toggles are separate; opting out of one does not opt out of the other.

Training opt-out is not Zero Data Retention

Training opt-out controls whether eligible data may improve Mistral models. Zero Data Retention (ZDR) controls whether supported API inputs and outputs are retained after returning a response. Mistral documents these as separate controls.

ZDR is available only for pay-as-you-go and supported stateless API calls. It is not available for Vibe Work or Chat on any plan because those products retain state for conversation history and related features. Mistral reviews ZDR requests and may approve or deny them, so teams must verify activation in the Admin panel rather than treating a submitted request as approval.

Who benefits—and who carries the risk

Mistral benefits from broader access to real interactions that can improve its models. Users who knowingly leave sharing enabled may also contribute to product quality.

The risk falls most heavily on individuals and teams that assumed paid or authenticated usage was excluded from training. The documented default does not mean every interaction will be trained on, but it does mean eligible Vibe content may be included unless the user opts out. That distinction matters for proprietary code, unpublished research, contracts, support logs, personal data, and files uploaded for analysis.

Enterprise’s opt-out default reduces that governance risk, but it should not replace verification. Administrators should record the setting, confirm who can change it, and include both Vibe and API controls in onboarding and periodic access reviews.

What teams should do today

1. Check both toggles in every Mistral workspace your organization controls and capture evidence of the chosen state.
2. Pause confidential uploads until the opt-out is confirmed; treat attached documents as input data.
3. Add Mistral’s training setting to vendor assessments, employee AI-use policies, and offboarding checks.
4. Ask Mistral for written terms covering retention, deletion, subprocessors, regions, and whether a setting change applies prospectively or to previously collected data.
5. Route sensitive workloads through an approved configuration and test that new workspaces inherit the intended policy.

For current costs, see the Mistral pricing page and Mistral API pricing guide. Compare governance and pricing with Anthropic and OpenAI, then estimate API spend with the token calculator.

Bottom line

Standard Mistral Vibe users should assume their input and output may be eligible for model training until they verify the opt-out. Enterprise Vibe is opted out by default, while Studio/API has a separate control that every API organization should inspect.

You do not need to buy Enterprise solely to stop training use: Mistral documents opt-out controls for standard Vibe and API users. The urgent action is to switch off both settings where required and stop treating a paid account as proof of training exclusion.

Sources: Mistral’s official training-use policy, data-training opt-out guide, Zero Data Retention guidance, and API rate documentation, plus the Hacker News discussion that surfaced the policy on September 2, 2026. Policy and pricing checked September 2, 2026. This is practical pricing analysis, not legal advice.