No-logs policy

What we log, in plain language.

"No logs" is the easiest claim in this industry to make and the hardest to back up. This page states exactly what we keep, what we do not, and the server architecture that makes the "do not" side true rather than aspirational.

What we collect

An email address, your subscription state, and the payment reference our processor gives us. That is the full list — it is what a subscription needs to exist and nothing more.

What we do not collect

  • Browsing history — the sites and services you connect to through the tunnel.
  • DNS queries — lookups resolve inside the tunnel and are not written down.
  • Traffic destinations or connection timestamps — when you connected, for how long, or to which server.
  • Bandwidth used per session — aggregate server load is measured at the machine, not attributed to an account.

Why: RAM-only servers

Every server in our fleet runs its operating system entirely in memory. There is no disk to write a log file to, even if something in the stack tried to. The fleet reboots on a schedule regardless, and a power-cycle clears whatever was in memory completely.

That is the difference between a no-logs policy and a no-logs architecture: a policy is a decision that can be reversed quietly; an architecture with nowhere to persist a log has to be rebuilt to start logging, not just re-configured. It is also our own hardware, not rented cloud capacity, which is what makes the RAM-only claim ours to keep rather than a vendor's to honour on our behalf.

How long we keep what we do collect

Your email address and billing state persist for as long as your account exists, because the subscription cannot run without them. Deleting your account removes them — see the privacy policy for how account deletion works and why it is permanent once requested.

What this policy is not

It is not an independently audited finding. Nobody outside the company has inspected this infrastructure yet, and describing an internal review as an audit would undercut the point of publishing this page at all. Where this claim stands today — verified architecture, pending third-party audit — is laid out row by row on the transparency page.