Most "no-logs" hosting is a marketing word with nothing behind it. Ours is a published policy: we retain only what running the service technically requires, we name each piece, and we give you three ways to check. You don't exist. We don't ask — and we don't log.
A no-logs VPS is a virtual server run by a host that does not keep records of what you do with it. The valuable part is not the phrase; it is the specifics behind it. HushVPS minimises collection at signup and minimises retention afterward, then writes both down so the claim is checkable rather than decorative.
Here is the part slogans skip: a machine cannot run on literally zero data. To deliver your VPS we have to route packets to it, schedule it on a hypervisor, and confirm a Monero payment. Those things exist for a moment whether we want them to or not. The meaningful question is not "do you touch any data" — every host does — but "what do you write down, keep, and could later be forced to hand over." A no-logs policy is an answer to that second question, and it is only worth anything if the host states it plainly instead of hiding behind an absolute it cannot honour.
So we do not claim a mystical zero. We claim minimisation plus transparency: collect the least, keep the least, delete the rest, and publish the list. If a provider tells you it keeps absolutely nothing while still delivering working servers, ask how the packets find your box — the honest answer is always "some transient handling," and pretending otherwise is the first sign the rest of the policy is theatre.
Every host must handle certain data to function. The difference between a logging host and a no-logs host is what happens after the moment passes — whether that data is written to a durable, searchable log or discarded.
The right side is not a leap of faith — it follows from the design. You cannot log a name you never asked for, and you cannot hand over a card number that no processor ever created. This is the same minimisation that powers our no-KYC Monero VPS.
This is the heart of a no-logs policy. Exact lifetimes are set by our operations policy and mirrored in our privacy policy — the placeholders below flag where the owner must confirm the precise window before publish.
| Data type | Do we keep it? | How long |
|---|---|---|
| KYC / identity documents | No — never collected | N/A |
| Real name / billing address | No | N/A |
| Payment card / bank data | No — Monero only | N/A |
| Traffic / connection access logs | No | Not written |
| VPS disk contents | No — your root, encrypt it | Yours to control |
| Optional order email | Only if you provide one | Kept only as long as operationally required |
| Order token & plan record | Yes — to run & support the service | Kept only as long as operationally required |
| Monero invoice / payment confirmation | Yes — accounting integrity | Kept only as long as operationally required |
| Short-lived operational / abuse signals | Transient | Kept only as long as operationally required |
| Server error / crash diagnostics | Minimised, no user traffic | Kept only as long as operationally required |
Where a row says "N/A," the data does not exist to retain because it is never collected. Retained items are kept only as long as operationally required — we will not print a specific number we cannot stand behind.
A policy you cannot verify is just a promise. These are the concrete artefacts you can inspect before and after you pay — no login required.
Our privacy policy states in plain language what is collected, what is kept, and for how long. It is written to match this page's retention table, not to bury the answer in legalese.
Our warrant canary is signed and refreshed on a schedule. If it stops updating or its wording changes, that is a signal in itself. See how we handle requests on the transparency page.
Order with the email field blank, pay in Monero, and notice you were never asked for an identity. Data that is never collected cannot be logged — verify it by walking the flow, not by trusting a badge.
Want the background before you commit? Our field guide, what "no-logs hosting" actually means, breaks down the claims worth checking and the red flags that give a fake policy away.
Every plan runs the same minimisation policy — there is no "privacy tier." Pick the size you need; the no-logs posture is identical from the smallest box to the largest. Prices are in USD, billed monthly, and charged in Monero at checkout.
A quiet, low-cost box for a Tor relay, a small onion service, or a personal WireGuard exit.
The sweet spot for self-hosting — a mail server, a Nextcloud, a private app stack that needs real headroom.
For heavier workloads — a seedbox, a busy relay, or several services sharing one hardened host.
Our biggest ghost — for build servers, dense containers, and anything that eats CPU and RAM for breakfast.
Need to compare cycles or see the full spec grid? The pricing page lays out monthly and yearly side by side.
No KYC, no name, no card. The identity that a logging host would store simply never enters our systems.
Payment confirms without a processor writing your name to a ledger. No card trail means no card record to keep.
We do not inspect what runs inside your VPS. Encrypt the disk and even the operational layer sees only ciphertext.
Minimisation is paired with a clear acceptable-use policy — no CSAM, malware, spam, or DDoS. Offshore-legal, not anything-goes.
Spin up a no-logs VPS paid in Monero, or read the surrounding pieces before you spend a coin — the anonymity model, the payment model, and the policy in writing.