No-logs policy
Short version: we do not log what you do or when you do it, and we built the platform so that we couldn't even if we wanted to.
What we never collect
- Browsing history, DNS queries, or the content and destination of your traffic
- Connection or disconnection timestamps, session duration
- Your real IP address — not at sign-up, not at login, not while connected
- The VPN IP address you were assigned at any given time
- Bandwidth usage per user
The little we do store
- Account: an email and password hash, a Google account ID, or — for anonymous accounts — a SHA-256 hash of your 16-digit account number.
- Subscription: the date your paid time ends, and payment records (provider, plan, amount). Card details are handled by Stripe; we never see them. Vouchers are anonymous.
- Devices: the name you gave each device and its WireGuard public key or a generated OpenVPN username. Private keys are generated in your browser and never reach us.
- Sessions: a hashed login token and its expiry. We do not record the IP address or browser used.
How it's enforced technically
- The database schema simply has no fields for activity, IPs or timestamps of connections. It is available to independent auditors on request.
- VPN nodes receive only public keys and tunnel addresses. They never learn which account a key belongs to.
- Nodes are RAM-only: swap is disabled, logs live in
tmpfs, journald is volatile, WireGuard keeps no logs and OpenVPN runs withlog /dev/nulland no status file. - DNS resolvers on nodes run with query logging disabled.
- The web server's access logs are disabled at the reverse proxy.
Legal requests
Because we hold no activity data, we have nothing meaningful to hand over. We publish every request we receive on our transparency page.
Your rights
You can export everything we hold about you, or permanently delete your account and all associated data, at any time from account settings.
Last updated: November 2026