VPSbitNo-logs VPS — stated precisely, from $4.80/mo
A no-logs VPS stated precisely: no payload or guest traffic logs, connection metadata ages out in 24 hours, billing records remain. No KYC, from $4.80/mo.
A no-logs VPS stated precisely: no payload or guest traffic logs, connection metadata ages out in 24 hours, billing records remain. No KYC, from $4.80/mo.
12 locations · 19 coins · SLA 99.95% · no KYC · public canary
VPS from $4.80* — Core on the annual term (list $6/mo), one invoice for 12 months, no auto-charges. Dedicated with IPMI from $39.20/mo. Crypto invoice, no KYC.
Launch nowWhat “no logs” means here — stated precisely
Short answer: no payload or guest traffic logs exist. Connection metadata ages out within 24 hours. Billing records and panel actions are retained, because money and support need them. Any provider that says “zero logs, ever” while billing you is lying about something — this page is the version that survives an audit.
The published privacy policy is the contract: no payload inspection, no guest traffic logging, connection metadata (when a connection happened, from which IP, to which port) kept at most 24 hours for abuse response. What is never collected: traffic content, DNS queries of guest traffic, destination lists of your VPS.
What we do keep — and why
Billing records (an invoice code, an amount, a coin, a status) exist because accounting law and support tickets require them. Panel actions (logins to your own account, reboots you ordered) exist so an account cannot silently change state. Both are tied to the account — which is a 32-character token or an email plus a 12-character password, with no KYC documents anywhere in the flow.
The 24-hour metadata window bounds what any future request could reach: a query arriving a day late finds nothing about guest traffic, because guest traffic is not logged at all — the window applies to the connection events the abuse desk needs, not to your payloads.
Open a no-KYC, low-retention VPS — from $4.80/mo.
Launch serverHow to verify, not trust
Three artifacts let you audit posture without writing to anyone: the warrant canary (dated, monthly — a stalled update is the tell), the status log (incidents appended with dates), and the looking glass (indicative RTT from every facility). The AUP states what no invoice covers, and abuse moves only on process from the facility's own jurisdiction.
Operationally, you can shrink what exists: full-disk encryption (LUKS guide), client-side encryption before anything touches the disk, and token-only signup so no mailbox ties the account to a person. Token-only signup covers the tradeoffs.
More rankings and guides
- Limits of no-KYC anonymity
- No-KYC VPS
- Anonymous VPS
- how-anonymous-is-vpsbit
- VPS for a privacy tools stack
Is a VPS with no logs truly anonymous?
No. No-KYC plus low retention is a small surface, not invisibility: the payment chain, your own operational mistakes and the facility's jurisdiction all exist. The honest page on the ceiling is the limits-of-anonymity guide.
What exactly counts as “connection metadata”?
When a connection arrived, from which source IP, to which destination port on your VM. Kept at most 24 hours for the abuse desk, then gone.
Do you log traffic content?
No. Payloads and guest traffic flows are not logged, inspected or stored. There is no DPI feature on the network.
Why keep billing records at all?
Accounting law and support disputes require them. They are tied to the account — which needs no identity — not to a dossier about you.
Can law enforcement read my VM?
Only through the facility's own jurisdiction, on criminal process. US-form DMCA mail is recorded and closed. The AUP bans the conduct that would make any of this interesting.
Which location is best for low exposure?
Reykjavik and Zurich for the speech-friendly posture; the locations table lists the retention law of every facility. Metadata handling is identical at all twelve.
Primary sources
Ready to launch?
Build the box — VPS or bare metal — create the password, pay the invoice that follows.