Trust & architecture

The plain-English version of our Privacy Policy - what we actually log, what we don't, and how the system is built underneath. Nothing here overrides the Privacy Policy; this just explains it without the legal phrasing.

Real WireGuard

The actual, unmodified WireGuard protocol - not a proprietary or "WireGuard-inspired" tunnel. Open, audited cryptography, not something we rolled ourselves.

No traffic logging

We never log or inspect which sites you visit, the content of your traffic, or your DNS queries - technically not possible to disclose what was never recorded.

Billing metadata only

Connect/disconnect timestamps, which server, and billed duration - enough to bill accurately and investigate abuse, nothing about what you did while connected.

No data sold

We don't sell or share your data with advertisers or data brokers, ever - free tier is ad-supported by third-party ad networks shown to you, not by selling your browsing data.

What actually happens to your traffic

Your device encrypts traffic locally with WireGuard, sends it to whichever server you picked, and that server forwards it to the internet under its own exit IP. The server never decrypts or inspects the contents of that traffic to log it - it just routes packets. DNS-level ad/tracker/malware blocking (on paid tiers) works the same way: a resolver checks each domain lookup against a blocklist and returns nothing for a match, without recording which domains you queried.

What we log, and why

Account info (email, name, plan) - so you can log in and we know what you're entitled to.
Connection metadata (when you connected, which server, how long) - the only way to bill pay-per-use accurately, and the only signal we have to investigate a fraud/chargeback report without ever looking at traffic content.
Payment references - handled by Stripe; we store a customer/subscription reference, never your card number.
Support ticket contents - only what you write when you contact us, used only to answer that ticket.

Full detail, retention periods, and your rights are in the Privacy Policy.

Security practices

Passwords hashed with bcrypt - never stored in plain text, never recoverable by anyone including us.
Two-factor authentication (email or authenticator app) and passkey sign-in, both opt-in.
One-time backup codes so 2FA never permanently locks you out of your own account.
Every staff action that touches an account (suspension, role change, deletion) is written to an append-only audit log - staff can't quietly act on an account without a trace.
The whole site and API run over HTTPS; the client-server API connection is separate from and in addition to the WireGuard tunnel itself.

Independent verification

Don't take our word for the "no leaks" part - run our own WebRTC leak test or an independent one (ipleak.net, browserleaks.com) while connected. Check current uptime on the status page, and see our standing legal-request disclosure on the transparency page.