What "no logs" really means for a VPS — and how to check it
"No logs" is the most repeated claim in privacy hosting. Here is what a provider can and cannot avoid logging, what stays under your control on the server, and how to judge the claim yourself.
Short answer: a no-logs VPS provider does not record what you do on your server and keeps as little account data as it needs to bill you. It does not mean that no data exists anywhere — the data centre network, the payment itself and the logs inside your own server are separate questions. A trustworthy no-logs claim tells you which of these it covers.
Three layers of logs
| Layer | Examples | Who controls it |
|---|---|---|
| Account and billing | Email, balance, deposit transactions, order history | The provider |
| Network | Traffic volume counters, abuse reports, upstream flow data | The provider and the data centre upstream |
| Inside your server | auth.log, web-server access logs, shell history, journald | You — full root |
Layer 1: account and billing data
This is the layer a provider can actually minimise. At NoctisNode the account is an email and a password; there is no name, phone, address or ID to store in the first place. Payments are in crypto, so there is no card number or billing address either. What necessarily remains is the account email, the balance, and the deposit transactions that were credited to it — a provider cannot bill you without those.
The practical test: look at the signup form. Every field a provider asks for is a field it keeps. Fewer fields is the only no-logs promise you can verify before paying.
Layer 2: the network
Your VPS runs on hardware in a data centre, and traffic leaves through that data centre's network. Bandwidth counters and abuse reports exist at that level for any host. Treat any provider that claims the network layer is perfectly invisible with suspicion. What protects you here is encryption: if your traffic is TLS, WireGuard or Tor, the network sees volumes and endpoints, not content.
Layer 3: logs inside your own server
This layer is entirely yours, and it is the one people forget. A fresh Linux image logs SSH logins, web requests and system events by default. If a server is seized or compromised, those files say more about its users than any provider ever could.
- ▹Set journald to volatile storage (`Storage=volatile` in `/etc/systemd/journald.conf`) so logs live in RAM only.
- ▹Turn off or shorten web-server access logs, or strip client IPs from them.
- ▹Disable shell history for root if you do not need it.
- ▹Encrypt the disk so data at rest is unreadable without your key — see the [LUKS encrypted root guide](/guides/luks-encrypted-root).
- ▹Harden SSH so the auth log has less to record — see [SSH hardening](/guides/ssh-hardening).
How to judge a no-logs claim
- 01.Count the signup fields. Email-only beats anything that asks for a name or phone.
- 02.Check the payment methods. Cards and PayPal attach an identity to the account no matter what the logging policy says.
- 03.Look for a warrant canary that is actually updated — see the [NoctisNode canary](/canary).
- 04.Read whether the policy distinguishes account data from server data. Vague, absolute promises are a worse sign than a precise, limited one.
- 05.Assume the network layer exists, and encrypt accordingly.
FAQ
QDoes a no-logs VPS mean no data is stored at all?
ANo. A provider must keep the account email, the balance and the deposits credited to it in order to bill you. No-logs means it does not record what you do on the server and does not collect identity data beyond that.
QWho can see my traffic on a no-logs VPS?
AThe data centre network sees traffic volumes and endpoints, as with any host. Use TLS, WireGuard or Tor so it cannot see content.
QAre the logs inside my VPS deleted automatically?
ANo. Logs inside the server are under your control with full root. Configure journald, web-server logs and disk encryption yourself.
QHow fast is a no-logs VPS deployed?
AAt NoctisNode, about 35 seconds after the payment is confirmed and credited to your balance.