Our log policy is a list, not an adjective.
“No logs” is a marketing phrase. Every provider keeps something, because they have to bill you. What matters is exactly what, so here it is, and it is the whole of it. There is no annex and no “other technical data as required”.
9 things kept. The rest is never written down.
| Item | Kept | For how long, and why |
|---|---|---|
| Sites you visit | NOT RECORDED | Our resolver answers from memory and keeps no query log. |
| DNS lookups | NOT RECORDED | Same resolver, on the same machine as the tunnel. Nothing written. |
| When you connect and disconnect | NOT RECORDED | Nothing tied to an account, so there is nothing to line up. |
| How much you use | NOT RECORDED | Nothing is metered per account, so there is no reason to count it. |
| Your home IP address | In memory only | WireGuard holds it while you are connected, because replies have to reach you. From launch, forgotten within five minutes of you disconnecting. Never written to disk. |
| Email address | Yes | While you have access, and 90 days after it ends; gone from backups 30 days later. To sign you in, and to tell you about your account. |
| Where you signed in from | Yes | Only if you have an account. Auth0, which runs sign-in, keeps the IP address of your last sign-in while your sign-in exists, and each sign-in for one day. Nothing links it to what you do on the VPN. |
| Emails we send you | Yes | Only if you have an account: sign-in codes, a note when a device is added, and your invitation if we invite you. Cloudflare, which sends them, keeps a record of each delivery for about a month, and no copy of what it said. |
| Your subscription | Yes | Only if you pay: the plan, monthly or yearly, when it renews or ends, and when you first paid, for the 30-day refund. Kept with your account. |
| Billing record | Yes | Six years, because HMRC requires it, with any dispute or fraud warning on a payment. Card numbers stay with Stripe and never reach us. |
| 30-day refund fingerprints | Yes | Only if you take the 30-day refund: a keyed fingerprint of your email address and of the card refunded, for two years, so the refund is once per person. It cannot be turned back into your address or card number. |
| Device public keys | Yes | Until you remove the device. A public key on its own says nothing about you. |
| Support tickets | Yes | Two years, so the next person to help you can see what happened last time. |
| Server load totals | Yes | Ninety days. Bytes and connection counts per server, with no account attached. Not for any minute when fewer than five devices are connected to that server: then only the machine itself (memory, disk, uptime). |
How the list stays true.
Where you go
The resolver that answers your DNS lookups runs on the same server as the tunnel and keeps no query log. Traffic is forwarded without being recorded. The tunnel ends on our server, where traffic is decrypted and sent on, so we could in principle see where it goes and read anything that is not itself encrypted. Most of it is HTTPS, which we cannot read. The rest we pass on without recording it. To send replies back to the right device, the server's kernel keeps a table of open connections in memory, as every router does. Each entry disappears when its connection goes quiet; the table is never written down, and we read only how many entries it has.
Your real IP address
WireGuard, by design, remembers each device's last address and the time of its last handshake while it is connected, because replies have to reach you. From launch, once a device has been idle for three minutes, the server forgets both; it checks every thirty seconds, so that happens within five minutes of you disconnecting. Until then, the only device connected is our own test phone, and the server holds its address until the device is removed or the server restarts. Inside the tunnel, each device has one private address, picked at random when it is added and the same on every server, so it says nothing about where or when you connect. None of it is written to disk.
What the server writes to disk
Nothing about you. The system journal is kept in memory only and is gone at every restart. The firewall logs no connections, nothing captures packets, and the resolver keeps no record of lookups. The list of devices allowed to connect is kept in memory and fetched again after a restart, and the program that keeps it up to date never logs a key or an address.
Server load totals
To know when London needs another machine, each server reports its totals every minute: bytes in and out, how many devices are connected, and how busy the machine is, with no account, device or address attached. Those totals are kept for ninety days. For any minute when fewer than five devices are connected to a server, none of them is kept, because with so few people they could show when one of them was online: only that the machine is up, and its memory and disk.
The rented server
The London server is rented from OVHcloud, which has physical access to it, as any host would. The protection is not that nobody could reach the machine. It is that nothing about where you go is ever on it.
What this list does not cover.
This website. It sets no cookies, except two that keep you signed in to your account, and runs no analytics that follow you. It is served by Cloudflare, which handles requests to deliver it. The strip at the top reads your address from the request to show it back to you and does not store it. Page views are counted as daily totals per page and per country, with no address or identifier attached.
Payments. Taken by Stripe, which keeps card details under its own privacy policy. We never see a card number.
Email. Sent through Cloudflare's email service, which sees the address it delivers to and keeps a record of each delivery for about a month, with no copy of what it said. Emails you send us are forwarded to our mailbox at Microsoft.
Everything else about personal data is in the privacy notice.
Every change, dated.
| Version | Date | What changed |
|---|---|---|
| 1.0 | 3 October 2026 | First version, published before launch. |
| 1.1 | 10 October 2026 | Added where you signed in from, held by Auth0, now that friends and family can sign in. |
| 1.2 | 10 October 2026 | Added the emails we send you, now that sign-in codes and device alerts come from our own address. |
| 1.3 | 17 October 2026 | Added your subscription, for when paying opens, and disputes and fraud warnings to the billing record; an account is deleted 90 days after access ends; invitations among the emails we send. |
| 1.4 | 5 November 2026 | Server load totals are no longer kept for any minute when fewer than five devices are connected to a server, so they cannot show when one person was online. Added the 30-day refund fingerprints, for when paying opens: the refund is once per person. |