O
My feedback
34 results found
-
821 votesO
supported this idea
·
-
1,033 votesO
supported this idea
·
-
1,157 votesO
supported this idea
·
-
1,237 votesO
supported this idea
·
-
1,621 votesO
supported this idea
·
-
1,701 votesO
supported this idea
·
-
2,001 votes
Proton and Standard Notes are joining forces: https://proton.me/blog/proton-standard-notes-join-forces
O
supported this idea
·
-
2,491 votesO
supported this idea
·
-
2,570 votesO
supported this idea
·
-
4,061 votes
An error occurred while saving the comment O
supported this idea
·
-
890 votesO
supported this idea
·
-
877 votesO
supported this idea
·
-
1,169 votesO
supported this idea
·
-
128 votesO
supported this idea
·
-
199 votesO
supported this idea
·
-
1,370 votesO
supported this idea
·
-
35 votes
An error occurred while saving the comment O
commented
Interesting. Some ideas from Lumo:
Can Proton VPN see your real traffic?
What passes through Proton VPN’s servers
When you connect to Proton VPN, all of your internet packets travel through Proton’s VPN gateways before reaching their final destination. Technically, any service that sits on the path can inspect the raw traffic (IP headers, DNS queries, unencrypted payloads, etc.).Proton’s policy and technical safeguards
Zero‑log policy – Proton’s publicly audited policy states that it does not retain connection logs, IP‑address logs, or any metadata that could be linked back to a user. Their internal systems are designed to discard session data as soon as the tunnel is torn down.
No traffic inspection – The VPN software does not include a man‑in‑the‑middle component, nor does Proton run deep‑packet inspection for advertising or analytics. The tunnel is a standard WireGuard/OpenVPN tunnel that forwards packets unchanged.
Jurisdiction & transparency – Proton is headquartered in Switzerland, which has strong privacy protections and a legal framework that makes forced disclosure of user data difficult. Proton also publishes regular transparency reports and undergoes independent audits of its infrastructure.
What could happen in theory
Even with the policies above, any operator of the exit nodes has the technical ability to see the traffic that leaves their network. If Proton were compelled (by a court order, for example) to modify its software to log or inspect traffic, it could technically do so. The real protection comes from the commitment not to do it and the legal environment that discourages such changes.Mitigating the “single‑hop” trust model
If you want to reduce reliance on a single provider for the exit hop, a *multi‑hop (double‑VPN) setup is the usual approach. Here’s how it works and why it matches the suggestion you saw:Partnered double‑hop – Two independent VPN providers each run a hop. Your traffic is encrypted twice: first by Provider A, then by Provider B. Provider B sees only the encrypted payload from Provider A, not your original data, and vice‑versa.
Benefits – Even if Provider A were compromised or forced to log, Provider B’s independent jurisdiction and policies would still shield the final exit point from your original ISP.
Existing examples – Mullvad partners with Obscura (as you noted) to offer a “double‑hop” configuration that combines two distinct infrastructures.
Practical ways to achieve a similar level of independence with Proton VPNManual double‑VPN – Run Proton VPN on one device (e.g., your router) and then run a second VPN client (e.g., Mullvad, IVPN, or Obscura) on top of it. This creates two encrypted layers without needing a formal partnership.
Proton VPN “Secure Core” – Proton already offers a Secure Core architecture that routes traffic through hardened servers in privacy‑friendly jurisdictions (Switzerland → Iceland/Sweden) before exiting to the wider internet. While not a true third‑party hop, it adds an extra barrier against network‑level adversaries.
Use a dedicated “exit‑only” server – Some advanced users set up a self‑hosted VPN endpoint (e.g., a VPS they control) and chain it after Proton VPN. This gives you full control over the final hop while still benefiting from Proton’s entry‑node privacy.
Bottom lineProton VPN does not log or intentionally inspect your traffic, and its Swiss jurisdiction offers strong legal protection.
Technically, any VPN provider—including Proton—could see the traffic that exits its network; the trust model rests on policy, audits, and jurisdiction.
If you need an extra layer of independence, a double‑VPN (either via a partner arrangement or a manual cascade of two separate VPN services) is the most straightforward way to achieve it.
Recommendation for youEnable Secure Core in Proton VPN if you haven’t already—it already adds a hardened, multi‑hop entry path.
If you want a truly independent exit hop, set up a second VPN (Mullvad, Obscura, or any reputable no‑logs provider) on top of Proton VPN, either on the same device or via a router‑level cascade.
Keep an eye on Proton’s roadmap; they occasionally introduce new multi‑hop features, and a formal partnership could appear in the future.
By combining Proton’s strong entry‑node privacy with an independent exit node, you get the “no‑one‑sees‑everything” guarantee that many privacy‑focused users seek.O
supported this idea
·
-
1,237 votesO
supported this idea
·
-
170 votesO
supported this idea
·
-
409 votesO
supported this idea
·
yes