Privacy policy

What we store

The complete list. If a field is not here, it is not in the database — not nullable, absent.

What we do not store

Also complete, and the more useful half of the document.

• Your name, email address, phone number or postal address — no such columns exist.
• Any payment identity. On-chain settlement means no processor holds a record linking you to us.
• Connection logs, NetFlow, sFlow or packet capture at any point on the network.
• DNS query logs. Our resolvers run with query logging disabled.
• Web server access logs on this site. Page views are counted in aggregate with no address retention.
• Console session recordings, keystrokes or screenshots.
• Customer IP history at any layer.

Why the bandwidth counters exist

Per-port byte counters in five-minute buckets are how metered plans are billed and how we notice a link saturating. Each record holds a virtual interface identifier, a byte count and a timestamp. There are no addresses, no ports and no payload, so they cannot reconstruct who communicated with what.

We call this out because a provider claiming literally zero telemetry is either mistaken or unable to run a network. The claim worth making is not “we record nothing” — it is “here is exactly what we record and why it cannot identify you”.

This website

No cookies are set until you begin a checkout, and that cookie holds only a cart identifier with a 24-hour lifetime. There is no analytics of any kind: no Google Analytics, no tag manager, no session recording, no heatmaps.

The site makes zero third-party requests. Fonts are self-hosted, there is no CDN outside our own network, and no external script is loaded on any page. You can verify this in your browser’s network tab in about ten seconds, and we would encourage you to.

Legal requests

We review every request for validity, scope and jurisdiction, and challenge those that are improperly served, overbroad or from a jurisdiction with no authority over the server. Where a request is valid we comply with what it compels and nothing more.

What compliance produces is an Argon2id token hash, a USD balance, a list of server identifiers and a creation timestamp. Quarterly counts by jurisdiction are published in the transparency report, and the warrant canary is signed and rotated each quarter.

Where we are permitted to notify you, we do, the same day.

Your data on the server

Whatever you put on your server is yours and we do not access it. On an unencrypted VPS a hypervisor operator technically could — that is true of every virtualisation provider that exists, and any host claiming otherwise is being imprecise.

If that matters, choose LUKS2 at provision. You enter the passphrase over the console at first boot, it never transits our infrastructure, and we cannot recover it. That is the only arrangement that does not require trusting us, which is why we offer it at no charge.