No-log policy

What we never log

• Your browsing history or the websites and services you connect to.
• DNS queries you make through the tunnel.
• The contents of your traffic, or traffic metadata tied to you.
• Per-user bandwidth or data-transfer logs.
• Connection timestamps or your originating IP address linked to your account.
• Any record that maps your account to the sites you visit.

What we keep, and why

To operate the service we hold a small amount of data, none of which describes your activity:

• A hash of your account number — to check that a number is valid and in good standing.
• Your registered device public keys and assigned tunnel IPs — so the network knows which devices are authorized and how to route them.
• A coarse “last seen” per device — so you can recognize and remove your own devices.
• Aggregate server health and capacity — not tied to any individual, used to keep the network healthy.
• Minimal payment records — the accounting facts required to sell account time, never your activity.

Why we can keep so little

The account model makes this possible. Because there is no email, name, or password — just a number — and because WireGuard only needs your device's public key to route you, we never need your real identity or a record of your activity to run the service. We can't lose what we never collect.

Requests from third parties

If we receive a lawful request for user data, we can only ever provide what we actually hold — which does not include browsing history, traffic logs, or activity tied to your account, because those records do not exist.

Verification

We intend to have this policy and our systems verified by an independent third-party audit, and to publish the results. (Audit status: planned.)

Changes

Any change that would affect what we log will be reflected here, with the date above updated. Questions? Email privacy@xruby-vpn.com.