Methodology · Updated May 2026
How we research VPN products
Our editorial process is based on synthesizing publicly verifiable data rather than independent hands-on testing. Every recommendation traces to an audit, a public benchmark, official documentation, or aggregated user reports.
This is not marketing copy. It is the process we apply, the sources we rely on, and the criteria that determine whether a VPN earns a recommendation, a runner-up slot, or a do-not-buy verdict.
Why our process is research-based
Our editorial process is based on synthesizing publicly verifiable data rather than independent hands-on testing. We do this because:
- Independent testing requires significant ongoing budget for subscriptions, hardware, and international travel.
- High-quality test sources already exist (Tom's Guide, PCMag, Cybernews, AV-TEST). Duplicating their work adds no value.
- Our value-add is synthesizing, contextualizing, and verifying claims across multiple sources.
What we DO
- Read every independent audit (Deloitte, PwC, KPMG, Cure53) and verify attribution against current public records.
- Track AV-TEST and AV-Comparatives benchmarks for performance and security data.
- Monitor user feedback on Trustpilot, Reddit, and the App Store, weighted by sample size and recency.
- Verify pricing on official provider sites monthly.
- Cross-reference streaming unblock reports across major review sites.
What we DON'T do
- Run our own speed tests on personal subscriptions.
- Conduct hands-on app testing on personal devices.
- Publish claims we cannot link to a verifiable source.
Sources we trust
Editorial independence
We earn affiliate commissions when readers subscribe through our links, at no extra cost to you. Those commissions cover hosting and the time it takes to do this properly. They do not change which VPN we recommend. We do not accept sponsored content, provider press access, or affiliate placement based on commission rates rather than research findings. See our affiliate disclosure for the legal version.
Contact
Spot a methodology issue, a sourcing error, or a claim that does not look right? Email [email protected] with the URL and the specific concern. We respond within 5 business days and publicly correct errors with a dated changelog.
Related reading
This methodology page is reviewed and updated at minimum once per quarter. Last review: May 2026.