01. Who owns the corrections process?
Saskia Lindgren-Wexford, editor-in-chief. Every correction routes through Saskia regardless of beat.
Named editorial staff for the Proton VPN Reference Hub. Every download walkthrough, free-tier breakdown and jurisdiction page passes through the desk below before publication. Visible bylines, direct contact paths, conflict-of-interest disclosures on file.
Read about the hubEditor-in-chief since the hub launched in 2022.
Saskia oversees editorial direction across the Proton VPN Reference Hub and owns the corrections process. Prior to launching the hub, Saskia spent ten years covering privacy software for an industry trade publication. Master's in journalism from Columbia.
Beat scope: privacy strategy, the Swiss jurisdiction page coverage, corrections and the masthead-level editorial posture. Every published correction routes through Saskia before going live.
Contact: saskia@protonvpn.co.com. Conflict-of-interest disclosures: none affecting current Proton VPN coverage.
Read about the hub →Reviews protocol coverage, audit reports and threat-model articles.
Aleksander handles the security silo. Eight years in network-security engineering before pivoting to editorial. Holds CISSP and OSCP certifications. The reviewer of last resort on protocol breakdowns, audit-report summaries and secure-connection threat-model claims.
Beat scope: protocols (WireGuard, OpenVPN, Stealth), security overview, secure VPN connection and privacy jurisdiction.
Contact: aleksander@protonvpn.co.com. Disclosures: prior consulting work fully lapsed.
Read security overview →Reviews downloads, platform guides and speed coverage.
Mireille covers the platforms silo: VPN downloads, Proton VPN for PC, Mac, Linux, iOS, Android coverage. Six years in client-software engineering, with focus on cross-platform privacy tooling. Holds residency in cryptographic-build verification.
Beat scope: download paths, platform-specific guides, speed-and-performance benchmarking.
Contact: mireille@protonvpn.co.com. Disclosures: past employer relationships lapsed.
Read VPN download walkthrough →| Editor | Beat | Years | Contact |
|---|---|---|---|
| Saskia Lindgren-Wexford | Editor-in-chief, jurisdiction, corrections | Since 2022 | saskia@protonvpn.co.com |
| Aleksander Kowalczyk-Penn | Security: protocols, audits, threat models | Since 2022 | aleksander@protonvpn.co.com |
| Mireille Kasanga-Holt | Platforms: downloads, PC/Mac/Linux/mobile | Since 2023 | mireille@protonvpn.co.com |
| Contributing reviewers | Rotating topical | Project basis | Per byline |
Four questions about staff, credentials and conflict-of-interest handling.
Saskia Lindgren-Wexford, editor-in-chief. Every correction routes through Saskia regardless of beat.
No. Current staff hold no Proton AG equity and no supplier retainers.
Each contributor named with credentials. Readers can request verification via the editor of record.
From three pools: licensed privacy-software analysts, former privacy-software employees (with disclosure), and reader-sourced experts.
A reproducible methodology beats opinion-based recommendation at every horizon longer than a single subscription cycle.
The reader desk works from four recurring inputs. Weekly catalog and pricing scrapes capture promotional cycles and feature changes. Annual third-party security audits, when published by independent firms, inform the security overview pages. Reader inbox traffic — roughly 600 messages per week on the privacy-software beat — identifies the friction points real users hit. Published Swiss court rulings affecting the broader privacy-software ecosystem, when issued, drive event-driven jurisdiction-page updates.
Revision cadence is weekly for tracker pages, monthly for category explainers and event-driven for security audits, regulator actions or major policy changes. Every page carries a visible last-updated date in the byline. When facts change, the portal prefers visible revision notes over silent edits, because privacy-software readers benefit from seeing how context evolves rather than reading a static snapshot.
Independence is enforced, not claimed. Editors do not hold equity in any privacy-software provider, do not accept affiliate income from any provider, and decline partner-authored copy under any byline. Conflicts of interest, when applicable to a contributor's prior employment in privacy-software, surface at the top of the affected article rather than buried in disclosures footers. Reader donations and newsletter subscriptions are the only revenue streams. The Electronic Frontier Foundation and Privacy International archives provide external frameworks the reader desk consults.
Understanding the broader privacy-software landscape helps shoppers evaluate any single offering in proper context.
The privacy-software market expanded materially through the 2020s as households became more aware of internet service provider tracking, public Wi-Fi exposure and the data-broker ecosystem. The post-2020 shift toward remote work pushed adoption further, particularly in households where employer-supplied corporate VPNs did not cover personal browsing.
Three structural dynamics shape the 2026 market. First, jurisdictional differentiation: providers domiciled outside major surveillance alliances (Switzerland, Panama, British Virgin Islands) have positioned legal independence as the central trust-building claim. Second, audit transparency: open-source clients with independent security audits have become table stakes for credible providers. Third, multi-product bundling: privacy companies have expanded from single-product offerings into broader privacy-tool ecosystems covering email, file storage, password management and calendar. The bundle math now competes directly with single-product specialty offerings.
Regulatory attention from consumer-protection bodies and privacy commissioners affects how providers communicate features. The Federal Trade Commission has issued guidance on VPN advertising claims; the European Data Protection Board issues rulings affecting EU-jurisdictions providers. The portal tracks regulator actions as event-driven inputs to coverage.
A scope statement keeps reader expectations aligned with reality.
This hub is editorial. It does not sell subscriptions, does not run affiliate links, does not accept supplier placement fees and does not link to commercial properties from body content. Outbound links route to government, educational and editorial sources only. Reader donations and newsletter subscriptions are the funding model. The desk reads every inbound message and synthesises monthly into category-page revisions.
The hub is not the official site for any privacy-software product. Account creation, subscription billing, official client downloads and customer-support tickets all live on the relevant company's official property. Search the official URL directly when reaching for those functions. The disambiguation page covers this distinction in detail.