Privacy by architecture
Don't trust us. Verify.
Most VPNs ask you to trust their no-log policy. Pangea is built so we can't see your traffic — even if we wanted to. Open source, rotating keys, isolated tunnels, and private keys that never leave your device.
Your keys, your device
Private keys are generated on your machine and never transmitted anywhere.
Rotating credentials
A fresh WireGuard keypair on every connection. Old keys are revoked instantly.
Isolated tunnels
Every account gets its own tunnel. You never share infrastructure with other users.
Under the hood
How it actually works
Every claim below is backed by code you can read. No vague promises — just architecture.
Private keys never leave your device
Your WireGuard private key is generated locally using X25519 elliptic-curve cryptography. Only the public key is sent to our provisioning service — the secret half stays on your hardware, always.
Most VPN providers generate your keys on their servers and hand you a config. That means they've seen your private key. We don't. We can't decrypt your traffic even if compelled to, because we never had the key.
Fresh keys, every single time
Every time you generate a config, a brand new WireGuard keypair is created and the previous one is permanently revoked. Your traffic can never be correlated across sessions.
Traditional VPNs give you one static key that identifies you for months or years. Pangea treats every connection as disposable — rotating keys mean even if one session were compromised, past and future sessions remain private.
One account, one tunnel — no sharing
Your VPN connection is provisioned to a dedicated tunnel tied to your account. You're not sharing bandwidth or infrastructure with hundreds of other users on the same node.
Shared-tunnel VPNs are the industry norm because they're cheaper to run. That also means if one user on your node gets flagged, everyone on that node suffers. Pangea provisions per-account isolation at the infrastructure level.
Architecturally unable to log your traffic
Pangea's control plane handles identity and billing. Your encrypted traffic flows through an isolated provisioning backend — we never see it, route it, or touch it.
"No-log" is a marketing checkbox for most VPNs. Our architecture enforces it: the system that knows who you are (Pangea) is structurally separated from the system that routes your traffic. We can't log what we can't see.
Configs encrypted at rest with AES-256-GCM
Your VPN configuration is encrypted before it's stored, using AES-256 in GCM mode with a unique initialisation vector per encryption. Even our own database can't be used to reconstruct your connection.
If our database were ever breached, attackers would find encrypted blobs — not usable VPN configs. Each config uses its own random 12-byte IV, and the encryption key is derived from a secret that never touches the database.
Open source. Verify, don't trust.
The Pangea VPN desktop app is open source under the GNU GPLv3. Read the code, audit the crypto, build it yourself. Privacy claims that can't be verified aren't worth making.
Closed-source VPNs ask you to trust their marketing. We publish the source so you can verify every claim on this page. The provisioning logic, key generation, and encryption are all in the repo.
View on GitHubComparison
What most VPNs won't tell you
The features that matter for privacy aren't the ones you see in ads.
| Feature | Pangea | Typical VPN |
|---|---|---|
| Private key stays on your device | — | |
| Fresh keypair every connection | — | |
| Per-account isolated tunnel | — | |
| Open source client | — | |
| Configs encrypted at rest | — | |
| Structural no-log architecture | — | |
| No-log policy (marketing claim) | ||
| WireGuard protocol |
Privacy you can prove
Read the code, check the architecture, then decide. We'd rather earn your trust than ask for it.
Pangea VPN is in active development. Features may change. The desktop app is open source under the GNU GPLv3.