Concepts explained · September 8, 2026

Does downloading the model keep your data local?

Use Mistral’s funding news to separate open weights, model location and data routes, then follow a document through three different setups.

01Why this question now

What do openness and control actually let you control?

On September 8, Mistral announced a €3 billion Series D at a post-money valuation above €21 billion. Its announcement describes sovereignty in terms of data, models, compute and production systems. That is the company’s account of its direction; how a particular product works still needs checking.

Suppose you want AI to summarize an internal document. Using an open model does not, by itself, tell you where that document goes. Who provides the model, whose machines run it, and which other tools receive the document are different questions.

02Separate model and service

Weights are the parameters a model learned

Weights are numerical parameters learned during training. They work with a model architecture and inference code to process inputs. Open weights generally means those parameters can be obtained; the specific model’s terms still determine permitted uses.

Some organizations define open-source AI more specifically. The Open Source Initiative’s version 1.0 combines freedoms to use, study, modify and share with requirements for data information, code and parameters. A download button alone does not establish that a system meets that definition.

03Follow one document

The same model can sit on different data routes

These are three illustrative setups written by BitShovel, not tests of a particular product. Each arrow means an input is handed to the next processing step. Whether it leaves the environment you manage depends on deployment and tool configuration. Self-deployment may use rented cloud servers; it does not necessarily mean a personal computer.

Mistral’s Vibe Code offline-model documentation also treats telemetry, automatic updates and tools that reach external services separately from local model configuration. Model location and the whole application’s data route need separate checks.

Follow the document’s route, not just the model’s name
  1. A · Within your environmentDocument → local app → local model

    This simplified setup has no external processing step. Check separately for app networking, logging and synchronization.

  2. B · A hosted serviceDocument → provider’s app → provider-run model

    Even if the weights are downloadable, the provider processes this request. Its service documentation governs retention and use.

  3. C · Local model, external toolDocument → external text extraction → local model

    The model is local, but an earlier step sends the document to another service. Checking only the model’s address misses this route.

04A detail in real documentation

Local code does not imply local-only data

Mistral Workflows offers a concrete example. In its documented hybrid mode, your code runs in your environment while the platform manages orchestration, state and history. Workflow inputs and outputs pass through the platform. The documentation describes controls including payload encryption and offloading larger inputs and outputs to file storage you control (object storage).

The encryption page calls the data exchanged by a workflow, such as inputs and outputs, its payloads. It distinguishes the default cleartext mode from separately configured encryption, which can cover every payload or only selected fields. That concerns application data handling; it does not establish that network transport is unencrypted. Passing through a platform does not, by itself, establish training use or a leak.

When code runs in your environment, the next questions are which data passes through the platform and which protections are enabled. This describes the documented hybrid mode, not the data route of every Mistral product.

  • Mistral Workflows · OverviewOfficial documentation · What runs whereThe hybrid deployment split, payload route and available controls.
  • Workflows · EncryptionOfficial documentation · default and encrypted modesPayload encryption requires configuration; it is not a blanket default guarantee.

05Use the distinctions

Use a sample file to ask three questions

Start with a sample file that contains no private or internal information and ask the tool provider the three questions below. This is our suggested way to understand a setup, not a finding that any product passed an inspection.

  • Where does processing happen? Identify the app, model and external tools such as text extraction or search.
  • What gets retained? Ask separately about original files, prompts, outputs, logs and synced copies, using the actual service documentation.
  • What can you take when changing tools? Use the sample to check exports of files, results and needed settings. Obtaining a model does not migrate an entire workflow.