Tor Keeps Mullvad Technical Partnership, Pauses Joint Promotion
The Tor Project said on Oct. 9, 2026, it will keep its relationship with Mullvad but set clear limits. Tor Project The statement answered concern about a political donation by a Mullvad co-founder, which raised questions about Mullvad's funding relationship with Tor.
The decision followed review that included discussions with community members, staff and the board, a staff survey, and financial analysis and planning for different funding outcomes. The project said it will continue technical work with Mullvad to support work that Tor users and contributors depend on.
In practice, the limit has two parts. The project has paused proactive co-branding with Mullvad, meaning joint promotion such as shared announcements and logos, while technical work continues under a narrowly scoped agreement. It also said it reviewed how Mullvad Browser is described and endorsed on its own websites and channels, and clarified wording that suggested broader agreement on values.
Mullvad is a founding member of the Tor Project's Membership Program and contributes at the Shallot level, the program's highest tier. Tor Project The joint work included developing Mullvad Browser and improving Tor Browser. Tor Project Both groups have pointed to human rights work as a reason for the browser collaboration, Wired and Mullvad has pointed to the Tor Project's record of building privacy-focused browsers as why it saw the project as a partner.
The broader context here is familiar to anyone who keeps shared infrastructure running. Joint engineering and joint messaging are different dependencies. One covers code, review, releases and user support. The other covers reputation, donor expectations and community trust. Decoupling them lets a project keep continuity for users while limiting risk when a funder becomes controversial. It is a governance control, not a fork.
In my view the specifics are worth noting because they are narrow and reversible. A pause on proactive co-branding stops new joint promotion. It does not require a rewrite of shipped software or disruption for current users. A narrowly scoped technical agreement does similar work for engineering, by defining what cooperation covers and what it does not. Clearer language on Tor's own documentation and download pages completes the pattern, and precision there matters because security-conscious users read those pages closely.
Looking at what this means for teams building on Tor, continuity is the central point. The project committed to sustain work that users and contributors depend on. For downstream packagers, browser maintainers and operators who test against Tor Browser behavior, that commitment matters more than logo placement. Worth flagging, in my view, is the process signal. Community discussion, staff survey input, board involvement, and financial planning point to an effort to treat reliance on one large funder as operational risk, which is sound practice where a top tier can create a sense of influence even when governance stays separate.
I have seen a version of this at home as my two children grew up alongside each wave of new tools. They rarely followed funding structures. They followed whether a tool kept working, stayed understandable and stayed available. By keeping the technical work intact while tightening the public boundary, Tor preserves that continuity. The long arc for privacy tooling depends on this kind of quiet, steady maintenance that keeps usable software in people's hands.
