C05 · Decision
Why Mullvad, and the Honest Single-Provider Trade
Nothing loads from YouTube until you press play. The video then plays in YouTube’s privacy-enhanced mode.
Why the Communication Suite runs Mullvad on the laptop and phone, and plain Mullvad WireGuard on the travel router in its nested mode, and the trade that comes with it. Account-number signup paid with cash (the Setup Guide calls it "the one truly anonymous account in the kit"), and QUIC, DAITA and Multihop in one app. One account within a persona, a separate key per device, and different actual relays for the router and the endpoints. Then the honest part: two Mullvad layers are not two independent providers, so an account or provider compromise is shared; one provider remains one trust domain. Proton is a possible regional fallback, and a self-hosted outer hop changes the trust assumptions without guaranteeing anything about detection.
What you’ll learn
- Know why Mullvad was chosen
- Understand the shared-provider risk
- Know the stated fallbacks
Chapters
The honest limits
One provider remains one trust domain: an account or provider compromise reaches both tunnels. Proton and any self-hosted outer hop need their own validation.
Check before you rely on it
These details change. Confirm them against the vendor’s current pages.
- Mullvad features; Proton as a regional fallback.
- Mullvad's cash-by-mail procedure and activation time.