All systems operational 12 elite locations · Europe & Asia Pay with crypto · 0 KYC
Home / No-Logs VPS — Exactly What Is and Isn't Stored
Privacy product

No-Logs VPS — Exactly What Is and Isn't Stored

No-logs VPS on VPSbit — privacy without KYC

No-logs VPS spelled out: no payload or guest-traffic logs, connection metadata expires within 24 hours, billing rows stay, no KYC. From $4.80/mo.

Short answer

No-logs VPS spelled out: no payload or guest-traffic logs, connection metadata expires within 24 hours, billing rows stay, 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 now

The claim, defined without the marketing

In brief: guest traffic and payloads are never written down anywhere on the platform. Any connection metadata is deleted after 24 hours. Money and support make billing entries and panel activity unavoidable, so those are kept, named, and bounded. A host promising zero logs forever while sending invoices is hiding something in the gap between the slogan and the ledger — what follows is the claim an auditor can actually check, class by class.

Treat the published privacy policy as the binding text, because it predates this page and outranks it. The policy rules out payload inspection and guest-traffic logging outright, and it caps connection metadata — the source IP, the destination port, the moment a connection occurred — at 24 hours, retained only so the abuse desk can react to a live complaint rather than a stale one. The never-collected list is equally explicit and shorter to read: your VPS's destination lists, the DNS queries guest traffic generates, and the content of the traffic itself.

A minimal-retention server rack storing almost nothing

The account behind all of it is either a 32-character token or an email paired with a 12-character password; KYC documents never enter the flow at any point, on any tier, under any flag.

The records that stay — and the reason each exists

Here is what survives, and the honest reason each row survives it. Accounting law and dispute handling force the billing side: a status, a coin, an amount, an invoice code — four fields, no name, no address, no purpose string. Panel activity — ordered reboots, logins into your own account — exists so that no account can flip state without a trace, which protects you as much as it protects anyone: a contested change has a timestamp and nothing else attached.

Guest traffic, to repeat the load-bearing sentence, is never logged anywhere on the platform — so a request that shows up even one day late has nothing to find, no matter how formal the letterhead. The 24-hour clock covers only the connection events an abuse desk may ever need; your payloads sit outside that window entirely, on every tier at every one of the 12 locations, and no feature exists to widen it retroactively.

The distinction matters when you read other hosts' privacy pages: retention spelled out per record class beats a blanket never that collapses at the first invoice or the first subpoena, and the anonymity guide covers what this posture does and does not buy you end to end.

Verify it yourself instead of trusting the sales page

Audit the posture yourself — no support ticket, no account, no permission required. Three public artifacts do the job between them: the warrant canary, reissued monthly and dated, where silence past the usual date is itself a signal worth acting on; the status log, with incidents appended as they happen rather than curated afterwards; and the looking glass, whose RTT readings from each facility are indicative rather than guaranteed, but whose existence from twelve cities is hard to fake cheaply.

There is also a layer you control outright, and it is the layer that shrinks the file fastest. Encrypt the full disk — the LUKS walkthrough in the guides covers it command by command — or encrypt client-side so nothing readable ever lands on the disk in the first place, and sign up with a token alone so no mailbox links the account back to a person. The tradeoffs of token-only signup, chiefly recovery, are laid out in the no-email guide.

Conduct no invoice pays for is spelled out in the AUP, and abuse is acted on only through process issued under the facility's own jurisdiction — the enforcement line the catalog carries on every page, priced identically from the entry rung up.

Retention regimes, location by location

What the platform keeps is only half the file; the other half is what each facility's law could compel, and the two halves answer different questions. The catalog spans 12 sites with deliberately different regimes, and the locations table spells out the governing law at each one rather than averaging it into a vague somewhere in Europe. Reykjavik operates with no mandatory data retention statute; Amsterdam, Frankfurt, Stockholm and Helsinki sit under EU GDPR with national hosting case law behind it; Zurich answers to the Swiss FADP outside the EU entirely.

Platform-side, all 12 handle metadata identically: the same 24-hour cap, the same categorical never on payloads, the same billing-and-panel rows with the same four fields. The location choice changes the legal weather around the rack, not the retention policy inside it — which is why both columns belong in any honest no-logs argument, and why a page that discusses only one of them is selling half a picture. The jurisdiction ranking works through the flags in order, with the premiums attached.

Network cables at a low-retention VPS facility

What a no-logs VPS will not give you

Low retention is not an invisibility cloak, and saying so plainly is cheaper than a customer learning it during an incident. It does not erase the payment trail: a KYC exchange withdrawal stays on the exchange's ledger forever, whatever this host does or refuses to do. It does not encrypt your traffic by existing; a plain HTTP site on a no-logs box is as readable on the wire as anywhere else on the planet. It does not protect conduct the AUP bans, and it does not place the machine outside criminal process at the facility's courthouse.

What it does is shrink the file to its documented minimum: no payload records anywhere, metadata gone inside 24 hours, billing rows that attach to a document-free account and nothing else. For the frank version of that ceiling — including the failure modes that are entirely yours — read the limits-of-anonymity guide, which exists precisely because half the no-logs marketing on the market overclaims in exactly this spot and gets believed until it matters.

From signup to first server on the minimal file

Run the whole funnel in your head and watch what accumulates, row by row. You open the account with a 32-character token or an email plus a 12-character password; nothing else is collected, so nothing else can leak, subpoena, or breach. You pick a plan — Core at $6 list, $4.80 annual-eff — and a flag among the 12. You settle one live-rate invoice in any of 19 coins. Roughly 60 seconds after the credit clears, root SSH is yours and the countdown on any connection metadata has already begun.

The file at the end of that sequence is short enough to print: an invoice row, a plan row, and panel events you triggered yourself. No payload record, no guest-traffic record, no identity document, and any connection metadata already inside its 24-hour countdown. Compare that against a card-paid signup at a typical host — name, address, card token, 3-D Secure event, statement line — and the difference is not marketing vocabulary, it is table rows that either exist or do not.

Layer your own controls on top and the file shrinks further still: token-only signup removes the mailbox, client-side encryption removes readable disks, and paying in XMR removes the on-chain link. The host does its half; the guide to anonymous signup covers yours in equal detail.

The posture, condensed for an auditor

Written the way an auditor would read it, in the order the questions get asked: guest traffic and payload bytes are never logged, inspected or stored anywhere on the platform, by any component, at any tier. Connection metadata — arrival time, source IP, destination port — lives at most 24 hours, and only so the abuse desk can act on a complaint while the connection is still a fact rather than a memory.

Billing rows — a status, a coin, an amount, an invoice code — and panel activity survive because accounting law and dispute handling require them, and they attach to an account that is a 32-character token or an email with a 12-character password. No identity document enters the flow at any point, on any tier, at any of the 12 sites, and no product exists that widens the metadata window for a fee.

The warrant canary, the status log and the looking glass are the artifacts that let you re-check this posture from the outside, month after month, without asking anyone's permission or opening a ticket. Core starts at $6 list, $4.80 on the annual term; the no-KYC page carries the signup mechanics, and the invoice carries all nineteen coins.

A no-KYC VPS with minimal retention, from $4.80/mo. Launch a server

Does a no-logs VPS make me actually anonymous?

It does not. Low retention and a no-KYC funnel shrink the surface but leave the payment trail, the facility's jurisdiction and your own slip-ups in place — the limits-of-anonymity guide draws that ceiling frankly.<ul><li>Kept: minimal billing rows, panel events</li><li>Not solved: payment trail, your own opsec</li></ul>

What falls under connection metadata, exactly?

The moment a connection arrived, the source IP it came from, and the destination port it targeted on your VM. The abuse desk may hold that trio for up to 24 hours — after that it no longer exists.<ul><li>Time: connection arrival moment</li><li>Source: client IP</li><li>Target: destination port on your VM</li></ul>

Is the content of my traffic logged?

No. Payload bytes and guest-traffic flows are neither logged nor inspected nor stored — the network carries no DPI feature that could do either.<ul><li>Payload: never stored</li><li>Guest flows: never stored</li><li>DPI: not present on the network</li></ul>

What are billing records kept for?

Accounting law and support disputes demand them. They attach to the account itself — and the account never carries an identity document — so they never grow into a dossier on you personally.<ul><li>Purpose: accounting law, dispute handling</li><li>Attach to: the account, not a person</li></ul>

Could law enforcement get inside my VM?

Only via criminal process under the jurisdiction where the facility operates; a US-form DMCA letter gets recorded and closed. The AUP bans the conduct that would make such a request interesting in the first place.<ul><li>Valid: criminal process from the facility's jurisdiction</li><li>Invalid: US-form DMCA templates</li></ul>

For low exposure, which location should I pick?

Start with Reykjavik and Zurich for their speech-friendly posture; the locations table spells out the retention law at each facility. All 12 handle metadata the same way.

Primary sources

Ready to launch?

Build the box — VPS or bare metal — create the password, pay the invoice that follows.