Tor Project keeps Mullvad ties but pauses co-branding after co-founder donation concerns

Tor keeps the Mullvad collaboration, with new limits

The Tor Project has decided to keep working with Mullvad rather than end the relationship, while tightening the boundaries around it. In a statement published on its blog and shared via Hacker News's front-page feed on 9 October 2026, the organisation said the move follows community concern about a political donation made by a Mullvad co-founder.

According to the statement, the donation raised questions about the Tor Project's funding relationship with the company behind Mullvad Browser. Community members asked how continued collaboration squares with Tor's mission of advancing human rights and freedoms, and the organisation says it heard both demands to cut ties and warnings about what ending the relationship would mean for Tor's work and the communities it serves. The statement does not identify the co-founder involved or provide details of the donation itself.

A review before the decision

The Tor Project frames the outcome as the product of an extensive review rather than a snap judgment. It says the process involved discussions with community members, staff and the board, a survey of staff, and detailed financial analysis and scenario planning. The mention of financial modelling is notable: privacy and anti-censorship work is, in the organisation's own description, badly short of resources, which makes such partnerships hard to walk away from.

The mission framing runs through the whole statement. Tor builds tools that people use to protect themselves from repression and surveillance and to express themselves freely, and it argues that this work benefits from collaboration across organisations. At the same time, it draws a values line: defending free expression does not mean every kind of speech aligns with Tor's mission, and the organisation says it firmly opposes rhetoric that threatens other human rights and freedoms.

What changes in practice

The concrete changes concern presentation rather than engineering. The Tor Project has paused proactive co-branding with Mullvad, which means joint promotional activity is on hold even as technical collaboration continues under an agreement with a deliberately narrow scope. It has also reviewed how Mullvad Browser is described and endorsed on Tor's own channels and reworded language that suggested broader alignment between the two organisations' values. The aim, it says, is to describe the relationship more accurately and remove any suggestion of implicit endorsement.

Why Tor says the partnership earns its keep

The statement sets out what the collaboration has delivered: improvements to how Tor Browser's codebase is structured, maintained and audited; feedback from users beyond Tor Browser's core audience; and a safer proving ground for features that could later reach Tor Browser users. It also positions Mullvad Browser as an additional free, open-source privacy tool serving different user needs, which widens access to online privacy overall.

The Tor Project does not shy away from the tension. It acknowledges that the benefits flowing to Mullvad from the arrangement are difficult for parts of its community to accept, and says its responsibility is to ensure the collaboration never compromises its mission or its independence. It also concedes the decision will not satisfy everyone, that continuing carries a real cost to trust for some community members, and that the concerns those members raised are shaping how the organisation moves forward. The statement closes on the idea that the mission has always required both principle and pragmatism, with collaborations that must serve, and never obscure, Tor's human rights commitments.

Why it matters

This is a governance decision as much as a funding one. Mission-driven infrastructure projects increasingly face versions of the same question: what to do when a sponsor or technical partner becomes politically contested. The Tor Project has chosen a middle path, combining transparency about the trade-offs and a tightened public association with continued technical cooperation, rather than either a clean break or quiet continuity.

For the wider privacy and open-source community, the statement sets a visible precedent for handling such disputes: a documented review, an explicit acknowledgement of the trust cost, and a public rationale tying the decision back to the mission. Whether that satisfies the community members who pushed for a separation, and whether other projects adopt a similar process when their own funders draw controversy, will help determine how these conflicts get resolved across the ecosystem.