Firefox Smart Window makes one AI decision on your device: whether an entry in its Smart Bar looks like chat or search. If it chooses chat, the full prompt can include your question, relevant saved Memories and material drawn from your browsing context. Mozilla's privacy notice says that package goes to a Mozilla server, then to a third-party language model. This is the concrete privacy boundary behind Mistral and Mozilla's new browser partnership, and it matters more than the phrase "privacy-first AI."
Mistral and Mozilla announced the tie-up on September 16. Mistral says its models now power Firefox Smart Window in beta for users in France and North America, with the United Kingdom and Germany expected later in 2026. The assistant can work across open tabs, retrieve something from browsing history, compare pages and help organize tabs. Mozilla's Smart Window product page still presents a waitlist, which points to a staged beta rather than a release that every Firefox user can open today.
The partnership gives Mozilla another AI supplier and gives Mistral distribution inside a browser. It also puts unusually detailed documentation beside the launch. Mozilla's Smart Window privacy notice explains which work happens locally, what Mozilla processes on its servers and when another provider receives a request. Read together, those documents describe a browser assistant with meaningful controls, but not an on-device Mistral system.
What the beta is supposed to do
Smart Window is an optional mode alongside the standard Firefox window. It requires a Mozilla account, and users can move between Smart Window and the standard browser from Firefox's interface. Mozilla says the assistant can answer questions, retrieve previously visited pages, close or organize tabs and use page context to help with a task. Private Window activity is excluded from the browsing activity used for Memories, according to the privacy notice.
The product page describes five jobs: grouping related tabs, displaying browsing history visually, comparing open material, summarizing pages and building a plan from guides or reviews. The pitch depends on context that a separate chatbot usually lacks. A browser already knows which pages are open and where you have been, so Smart Window can answer a question such as "compare the five black sneakers I looked at last week" by finding titles and URLs in history and fetching those pages in the background. Mozilla uses that example in its privacy documentation.
Mistral's part is less specific. The companies say Mistral models power the assistant and that the models are trained and fine-tuned for regional languages, dialects and cultural context. The announcement does not name the model version, publish a supported-language list or provide measurements for those regional claims. It says only that Mistral will help power Smart Window in the initial regions, while Mozilla says users can choose among three models or supply another endpoint.
That distinction affects how the launch should be read. Mistral is part of Smart Window's model layer, while Mozilla controls the browser features, context assembly and server relay described in the privacy notice. Calling the entire feature "Mistral-powered" is accurate at the partnership level, but it does not tell a user which request reaches which model. Neither launch page spells out the three offered models or identifies a default.
Local storage does not mean local processing
Mozilla calls its saved user context "Memories." Smart Window can infer interests from assistant conversations and Firefox activity, including activity in standard windows. By default, Mozilla processes that information on its server to infer a Memory. It says the server does not retain the input after processing. The resulting Memory is stored on the device, expires after a limited period unless later activity keeps it relevant, and can be reviewed or deleted in settings. Users can also block Memories from a chat or rerun a request without a selected Memory, according to the privacy notice.
One step does stay local: an on-device intent classifier decides whether the Smart Bar input should become a chat or a search. For chat, Firefox may assemble relevant Memories, page titles, URLs and content fetched from pages in the background. The full assembled prompt then goes to Mozilla. Mozilla forwards the required material to a third-party model, which sees a Mozilla IP address instead of the user's IP address. That proxy design separates the model provider from the user's network address, though the provider still receives the prompt content selected for the request.
Mistral says partners in Smart Window agree to zero data retention. Mozilla separately says it does not use conversations to train models and does not retain chat logs without permission. Those are useful limits, yet they describe retention after transmission. The assistant still needs to send selected content away from the device for hosted inference. Users deciding whether to turn on Memories need both parts of the story: where the saved Memory lives and where its relevant contents travel when used in a prompt. The claims appear in the launch announcement and privacy notice.
Search follows a separate path. If the assistant classifies an entry as search, or cannot answer a chat request, it may rewrite the query using Memories, browser context or chat history. The chosen search provider then handles that query under its own privacy terms. Mozilla also says it may call a search index partner when a language model lacks enough information, without including personal identifiers that link the request to the user. These routes are set out in the Smart Window privacy notice, though the launch post does not discuss them.
Model choice changes who handles the prompt
Mozilla's product page says Smart Window offers three models and lets people bring their own. The privacy notice adds an important routing detail: a custom endpoint that Mozilla does not provide receives information directly rather than through a Mozilla server. The operator's terms and privacy policy then apply. Model choice therefore changes more than answer style or speed. It can change the processor, the network route and the rules applied to a prompt.
The public pages leave several implementation questions open. They do not name the Mistral model, list the other hosted choices or say whether the same selection is available in every launch region. They also do not state which search index partner is used, provide a technical definition of "zero data retention," or link that promise to an outside audit. The Mistral announcement describes the policy, while Mozilla's notice explains the flow. Neither supplies the missing operational detail.
There is still a meaningful difference between this design and an assistant tied to one provider. A user can switch among Mozilla's offered models, disable Memories for a request or configure another endpoint. Smart Window is also opt-in rather than a replacement for ordinary Firefox browsing. Those controls are documented on the product page. Their value will depend on how plainly Firefox exposes them during setup and whether the browser shows the context attached to each request before it is sent. Mozilla says the resulting answer includes the specific Memories used, but that disclosure happens after processing.
Browser context raises the privacy stakes
A browser assistant can be more useful than a blank chat box precisely because it can see more. Page titles, URLs, open tabs and recent research can turn a vague request into a usable comparison. The same context can reveal health questions, purchases, work projects or travel plans. Mozilla says it tries to filter sensitive data from Memories and excludes Private Window activity, yet its notice does not promise that every sensitive detail will be detected before processing. The product page uses the more careful wording that Mozilla will "always try" to filter it.
For developers evaluating Smart Window, the right unit of inspection is the assembled request. Local classification and local Memory storage reduce some exposure. Mozilla's proxy prevents a hosted model from seeing the user's IP address. None of those controls makes the prompt local once chat processing begins. A useful test should record which tabs or history entries were selected, which Memories were attached, the chosen endpoint and whether rerunning with Memories disabled changes the outbound material. Mozilla's documentation confirms that each of those choices can affect the request.
The beta now has a clear test to pass. Mozilla needs to make the pre-send context as legible as the post-response Memory labels, and Mistral needs to identify the model and evidence behind its regional-language claims. Watch the Smart Window product page and privacy notice as access expands beyond France and North America. If those documents gain model names, retention verification and controls that show context before transmission, the partnership's privacy claim will become something users can check rather than a label they have to accept.