Provider snapshot
Proton VPN
Proton VPN is a Swiss VPN provider with public no-logs statements, published audit material, open-source apps, Secure Core routing, and a privacy-first product posture. Aerod evaluates it as a transparency-forward VPN option, not as a browser-anonymity guarantee.
- Category
- vpn
- Jurisdiction
- Switzerland, according to Proton VPN public no-logs material.
- Network notes
- Proton VPN says DNS queries are routed through encrypted VPN tunnels and resolved on Proton servers while connected.
- Audit notes
- Proton VPN says its no-logs policy has been verified by Securitum and that it has passed a fifth consecutive annual no-logs audit.
- App notes
- Proton VPN states that its apps are open source and available for inspection.
- Last reviewed
- 2026-08-05
Proton VPN is best evaluated as a transparency-forward VPN route layer. Its public materials emphasize Swiss jurisdiction, public audit material, open-source applications, Secure Core routing, and privacy-focused documentation. Those points are relevant to provider trust, but they do not erase browser fingerprinting, storage, extensions, or logged-in identity.
What Aerod reviewed
This page reviews Proton VPN’s published transparency posture, application controls, routing modes, and the verification workflow required after connection. Aerod does not claim a continuous independent benchmark of speed, server availability, streaming access, or uptime.
| Area | What to review | Why it matters |
|---|---|---|
| Provider transparency | Audit material, app source availability, and documentation dates | Trust claims are stronger when the supporting material is public and current. |
| Secure Core | Whether the extra routing layer fits the threat model | More hops can change latency and do not replace browser isolation. |
| Kill switch | Behavior on the target operating system | Implementation details can vary by platform. |
| DNS and WebRTC | Observed behavior after connection | The VPN status indicator is not a complete exposure test. |
| Browser context | Accounts, storage, timezone, language, and extensions | Browser identity remains independent of the VPN route. |
Aerod verdict
Working verdict
Strong fit when public transparency and audit posture are high priorities.
Proton VPN is a strong candidate for users who value public documentation, open-source positioning, and a privacy-oriented provider model. It still requires DNS, WebRTC, kill-switch, and browser checks after connection.
Where Proton VPN fits best
- Users who prioritize provider transparency and public assurance material.
- People who want a free or paid entry point from the same provider ecosystem, subject to current plan terms.
- Threat models that may benefit from Secure Core and can accept the performance tradeoff.
- Users willing to inspect the exact application behavior on their operating system.
Where it is not the best fit
- A user who interprets open-source apps as proof that every operational claim is independently verified.
- A workflow expecting Secure Core to hide logged-in identity or browser fingerprints.
- A purchase based on an old plan comparison or server-count claim.
- A situation where the user cannot test the selected platform’s kill switch and DNS behavior.
Setup sequence
- Choose the plan and routing mode that actually matches the threat model.
- Review protocol, kill-switch, auto-connect, and split-tunneling behavior.
- Connect to the intended region.
- Verify the visible route with IP Lookup.
- Review DNS and WebRTC.
- Test a controlled disconnect.
- Review the browser profile separately with Browser Leak Test.
Validation checklist
Minimum validation path
- Confirm the selected plan and feature set.
- Verify visible IP, ASN, owner, and location.
- Verify DNS behavior.
- Review WebRTC candidates.
- Test kill-switch behavior.
- Review split-tunneling rules.
- Review browser profile signals.
- Keep provider audit claims separate from observed session results.
Strengths and limitations
Strengths
- Transparency-forward product positioning.
- Public documentation and audit material.
- Routing options for ordinary and higher-risk workflows.
Limitations
- Public transparency does not remove provider trust.
- Secure Core can add latency.
- Browser and account identity remain separate from the VPN route.