Mistral + Mozilla Smart Window: Privacy, Models and Access

Short answer: Mistral and Mozilla announced a partnership on September 16, 2026, for Firefox Smart Window, where Mistral Small 4 is among the selectable models in Mozilla’s optional AI browsing assistant. Smart Window is still a beta feature, not a new Mistral browser, not a Mistral-only model surface and not a local-only assistant. Firefox 155 documentation records availability for users in the United States, Canada and France, with progressive rollout possibly delaying visibility; Mozilla’s September 2 explainer described the earlier pre-Firefox-155 United States and Canada stage. Mistral says the United Kingdom and Germany are expected later this year. The privacy design reduces what model providers can identify, but pages, tabs, history and prompts can still be processed to answer a request. Treat it as a user-controlled research window, not an autonomous browser agent.

What changed in the Mistral–Mozilla partnership

Mistral’s announcement connects its partnership with Mozilla to Smart Window, Mozilla’s AI browsing assistant for Firefox, while Mozilla’s current model table lists Mistral Small 4 as one selectable option. The stated goal is to combine Mozilla’s privacy-first browser position with Mistral’s open-model and multilingual AI work. The announcement specifically points to complex searches, remembering something important that was clicked away from, and sourcing information from browser tabs.

That is a partnership around an experience and its model options. It does not mean Firefox has become a Mistral product, that every Firefox AI feature uses Mistral, or that all Smart Window computation runs on a device. Firefox can expose other providers, and Mozilla’s model help explicitly documents a provider choice and BYOM. The practical change for a reader is that Mistral is now one of the available model paths inside an optional Firefox research workflow.

Mistral’s statements about “zero data retention” and the partnership’s privacy properties are vendor claims. Mozilla’s own privacy, safety and support documentation provides the more detailed data-flow description, so both should be read together.

Smart Window availability: beta, regions and devices

Status: Smart Window is optional and remains in beta. Mozilla says it is separate from a classic Firefox window, and opening a Smart Window does not change the classic browsing experience. A Mozilla account is required. A user can open a new Smart Window or convert a classic window, and tabs remain available during the switch.

Regions: The current documentation needs careful reading:

• Mozilla’s Smart Window model and safety pages describe a gradual rollout beginning in the United States and Canada with Firefox 150, then France with Firefox 155.
• Firefox 155 release notes say Smart Window is available for users in the United States, Canada and France to try, subject to a progressive rollout.
• Mozilla’s September 2 “AI on your terms” explainer describes the earlier pre-Firefox-155 stage, when Smart Window was available in English to people in the United States and Canada.
• Mistral’s September 16 partnership announcement says the collaboration will cover Smart Window for people in France and North America, with the United Kingdom and Germany expected later this year.

These dated statements establish a staged rollout, not universal access. The September 2 explainer describes the pre-Firefox-155 United States and Canada stage; Firefox 155 documentation records availability for users in the United States, Canada and France, with progressive rollout possibly delaying visibility. Mistral’s September 16 announcement says the partnership covers France and North America, with the United Kingdom and Germany expected later this year. Check the actual Firefox account and build for visibility. Outside the documented markets, a waitlist or no-access state is expected.

Devices: The product and support materials describe Smart Window as a Firefox window, and the independent hands-on report reviewed it on Ubuntu Linux with desktop Firefox. Firefox itself is available on Windows, macOS, Linux, iOS and Android, but that does not establish Smart Window support on every Firefox client. No reviewed Mozilla page confirms a mobile Smart Window rollout. For a current check, use a supported desktop Firefox build, sign in to the Mozilla account and look for New Smart Window or the AI controls; do not infer mobile availability from the browser’s general download list.

Access can also depend on progressive rollout, a portal or waitlist, model-provider availability and daily usage limits. Mozilla says the normal browser continues to work after the Smart Window chat quota is reached. Its support page recommends at least 4 GB of available RAM for the intended experience; lower-memory systems can still run Smart Window, but memories and history search are limited. Chats and memories are stored locally and do not sync across devices.

Which models can Smart Window use?

Mozilla’s latest Smart Window model-help page lists three choices:

The model list is not a permanent contract. Mozilla says it evaluates model additions and removals, and the support page contains an older duplicate table with different entries. An independent It’s FOSS hands-on test also saw an older build with Gemini 2.5 Flash Lite, Qwen3-235B-A22B-Instruct-2507 and gpt-oss-120B rather than the current Mistral Small 4 table. That difference is useful evidence that the roster changes during beta; it is not a benchmark or proof that every account sees every model.

Choose a model in Settings → AI controls → Smart Window settings or per conversation when the interface allows it. The partnership therefore expands choice without making Mistral exclusive. If a model name, host or capability matters to a workflow, record what the signed-in browser actually offers on the day of use.

What Smart Window can—and cannot—do

Mozilla describes Smart Window as an assistant for research and organisation. It can summarize a page, compare information across selected tabs, make recommendations, help plan, retrieve something from browsing history when asked, group tabs, identify duplicate tabs and use Exa to search for current information with source citations. You can reference tabs with an @ tag or explicitly select the context to share.

The important boundary is that it is not a browser-control agent. Mozilla’s getting-started guidance says Smart Window cannot click buttons, fill forms, complete purchases, book flights or hotels, change browser settings, or sign in to sites using saved credentials. It should not be treated as an unattended agent for transactions, account administration or regulated decisions. A prompt can produce a plan, but a person must carry out the consequential action.

Mozilla’s terms also warn that outputs can hallucinate and should not be the sole source for factual or professional decisions. The product is useful when it compresses a set of pages you can inspect; it is not a substitute for checking primary documents or completing the task yourself.

Privacy: what is protected and what still leaves your device

“Private” does not mean “nothing is sent anywhere.” Smart Window is an optional service that processes the context needed to answer a request. Mozilla’s privacy notice and help pages describe these boundaries:

• The assistant may receive the current page, tabs you reference and browsing history when you ask it to use history. It cannot access Private Windows, passwords, payment information, unread email or local files.
• A request is sent to Mozilla and then to the selected model provider under the documented flow. Mozilla says its proxy prevents the provider from seeing your IP address, browser/computer identifier or direct location information.
• Mozilla says chats are not retained on its servers or by the model hosts, and are not used to train models, unless the user opts in to feedback, review or related learning controls. “Chats are stored locally” means the browser can keep them on the device; it does not mean the prompt never left the device.
• Memories are optional and local after Mozilla processes activity to infer interests. The privacy notice says activity such as sites visited (excluding Private Windows) can be processed on Mozilla’s server for that purpose. You can inspect or delete memories and retry without memories. Memories and chats are not synced across devices.
• Mistral’s partnership announcement says partners agree to zero data retention. That is a Mistral/vendor statement; the Mozilla privacy notice and the selected endpoint’s terms remain the operative documents for a real workflow.
• If you supply a custom endpoint, Mozilla says the data may be processed by that endpoint without being routed through Mozilla. The endpoint’s owner then controls its own retention, training, security, residency and incident terms.

For a privacy-sensitive team, the right question is not “Is the browser private?” It is “Which context did I share, which endpoint received it, what identity metadata was hidden, and what local or remote retention rules apply?” Do not paste credentials, payment details, confidential client material or regulated personal data merely because the interface offers a privacy label.

A practical privacy-sensitive workflow

1. Separate research from action. Use Smart Window for public pages, comparison and summarization. Keep account work, secrets and transactions in a classic or private workflow.
2. Share the smallest context. Select only the tabs needed for the question. Use an @Tab reference rather than asking the assistant to inspect every open tab.
3. Make uncertainty visible. Ask: “Summarize these sources, list each claim’s source, mark conflicts and say what is not established.” Treat a citation as a starting point for inspection, not a guarantee.
4. Choose the endpoint intentionally. Review the current Mistral, Qwen or Gemini option shown by Firefox. Use BYOM only when the custom endpoint’s retention, training, region, access and deletion terms are acceptable.
5. Control memories. Leave learning and memories off when they are not needed. Before a sensitive query, check whether memories are enabled; after a session, inspect or delete any memory you did not intend to keep.
6. Verify before acting. Open the cited primary source and check dates, numbers and scope. Smart Window cannot safely click, buy, book or sign in for you, so retain a human approval step.
7. Plan for limits. Daily chat quotas, beta changes and low-memory restrictions can interrupt a workflow. Keep a classic Firefox path and a manual research fallback.

Useful prompts are narrow and auditable: “Compare the pricing claims in these three selected pages; quote no more than one short phrase, give the publication date for each, and list unresolved contradictions.” For a history retrieval, ask for the matching page title and URL before accepting a summary. These prompts improve reviewability; they do not eliminate hallucination or prompt-injection risk.

How Smart Window compares with an AI-first browser

Search results for “AI browser” are dominated by AI-first products and generic comparison pages. Those pages often discuss products such as Comet, Arc or Dia but omit the details that matter for Smart Window: the optional separate window, provider/model choice, Mozilla proxy, memory controls, dated rollout transition and explicit inability to complete transactions.

Mozilla’s approach is closer to an AI layer inside an established browser than to an autonomous browser replacement. A TechRadar interview with Firefox leadership describes a model-agnostic strategy and user choice, while the product documentation makes the limits concrete. It would be misleading to rank Smart Window as “more private” or “more capable” than every competitor without equivalent tests and current terms. The useful comparison is operational: Smart Window makes context selection and provider choice visible, but still sends selected context for processing and keeps a human at the action boundary.

For teams already evaluating browser agents, our browser-agent workflow guide covers a different, Claude-specific automation surface. For Mistral’s broader funding and sovereignty context, see the Mistral funding and sovereignty context. The AI assistant privacy audit is a separate OpenAI history/privacy topic, not a Smart Window owner.

What the independent testing and community signals show

It’s FOSS reports an early hands-on session on Ubuntu 26.04 LTS using Firefox 151.0.2. The reviewer needed a Mozilla account and beta activation, described the build as pre-production, and reported that page summarization and cross-questioning worked in that test. The report saw an older model list and could not establish rollout outside the tested markets. It is useful evidence of setup friction and one person’s experience, not a performance benchmark or a guarantee for your account.

Official Firefox posts and Mozilla Connect discussions show the same beta pattern: optional access, a waitlist or progressive rollout, questions about proxying and local models, and user feedback about the interface. Mozilla employee replies mention BYOM routes such as OpenRouter or local-serving tools, but those community replies are not a substitute for the current support contract. A Mozilla Support thread also records a user who had a beta email but still saw the waitlist; do not rely on unsupported configuration changes to bypass the rollout.

Frequently asked questions

Is Smart Window a Mistral browser?

No. It is an optional Firefox window and assistant. Mistral is one model/provider option in the documented roster; Mozilla also lists Qwen, Gemini and BYOM. The partnership does not replace Firefox’s classic or private windows.

Is Mistral Small 4 the only Smart Window model?

No. Mozilla’s current help table lists Mistral Small 4, Qwen3-235B and Gemini 3.1 Flash Lite, plus a custom endpoint option. Older Mozilla material and an independent hands-on report show different entries, so check the model picker in your build.

Is Smart Window local or private by default?

It is not local-only. Selected page, tab, history and prompt context can be sent for processing. Mozilla documents a proxy and no model-host conversation retention in the standard flow, while Mistral makes a zero-retention partner claim. Memories can involve server-side processing before local storage, and custom endpoints have separate terms.

Can Smart Window fill a form or buy something?

Mozilla’s support guidance says it cannot click buttons, fill forms, complete purchases, book travel, change settings or sign in with saved credentials. It can help you research or plan, but a person must perform the consequential action.

Why can’t I see Smart Window?

The feature is beta and progressively rolled out. Region, Firefox version, Mozilla account, waitlist or portal activation, model availability and daily limits can all matter. The September 2 explainer described the pre-Firefox-155 United States and Canada stage; Firefox 155 documents availability for users in the United States, Canada and France, with progressive rollout possibly delaying visibility. No reviewed page confirms a mobile rollout. Check the current Smart Window controls in a supported desktop Firefox build rather than treating a product-page waitlist as a global launch.

Bottom line

Mistral and Mozilla’s announced partnership places Mistral Small 4 among the selectable models in a thoughtful, choice-oriented Firefox AI experiment. The strongest current use case is privacy-aware research: select a few public tabs, ask for a source-backed comparison, inspect the cited pages and keep a person in control of any action. The strongest caveat is equally important: Smart Window still sends selected context for processing, is a changing beta, has daily and hardware limits, and is not an autonomous browser agent.

Before adopting it for sensitive work, verify the current region and model picker, decide whether memories are appropriate, record the provider or custom endpoint, and confirm that the data and retention terms fit the workflow. Recheck these facts before publication because Mozilla’s model roster and rollout can change during beta.

Sources and scope

• Mistral: Mistral and Mozilla are bringing open, private and multilingual AI to your web browser, September 16, 2026. Partnership announcement and vendor claims.
• Mozilla: Firefox AI on your terms, September 2, 2026. Product framing, provider choice and beta context.
• Firefox 155 release notes, September 1, 2026. Progressive regional availability.
• Mozilla Support: Smart Window models. Current model table, hosts, BYOM and rollout notes.
• Mozilla Smart Window privacy notice. Data flow, memories, local chats, custom endpoints and retention language.
• Mozilla Support: Smart Window safety and Get started with Smart Window. Proxy, prompt-injection, access and action boundaries.
• Mozilla Smart Window terms. Beta terms, rate limits, age requirement and output warnings.
• Firefox Smart Window product page and Smart Window start prompts. Product surface and examples.
• It’s FOSS hands-on: Firefox Smart Window brings AI into your browsing experience. Independent early desktop test.
• TechRadar interview with Firefox leadership. Independent context on model choice and browser strategy.
• Firefox community beta announcement and Mozilla Connect discussion. Official community rollout and feedback signals.

Scope note: This draft reports sources accessed on September 16, 2026. It distinguishes the Mistral vendor announcement from Mozilla’s product, privacy and support documentation; records the dated rollout transition from the pre-Firefox-155 September 2 explainer to Firefox 155 availability for users in the United States, Canada and France subject to progressive rollout, plus the changing model roster; and treats It’s FOSS, TechRadar, Reddit and Mozilla Connect as independent or community context rather than proof of universal behavior. No Smart Window account test, model benchmark, mobile test, API call, external publication or WordPress mutation was performed for this package.