Transient network handling
Routing packets and maintaining interface state are required to deliver connectivity. They are not automatically a retained browsing history.
No-logs VPS: records, retention and limits
A useful no-logs statement separates account records, billing state, infrastructure diagnostics and traffic history. SilentVPS is designed around data minimization; the final production retention policy will be supplied before launch.
At a glance
No-logs hosting needs a precise definition of which records are excluded and which remain. Account, billing, infrastructure and guest-system records are different categories. SilentVPS has not published validated retention periods; assess specific data handling rather than treating a no-logs label as proof.
A running server always handles some data
Packets must be routed, a hypervisor must schedule work and a payment must be confirmed. Handling those events is different from keeping a searchable history of every connection. The question is which events become durable records, for what reason, and for how long.
Avoid treating “zero logs” as a claim that no data can ever exist. A responsible implementation names its necessary records, restricts access, limits retention and distinguishes platform telemetry from the logs you configure inside your own virtual machine.
Transient operations and persistent records
Service records
The chosen plan, allocation, order token and billing status are needed to manage the service.
Optional contact
A supplied notification email is account data. Leaving the field blank removes that item from your configuration.
Diagnostics and abuse signals
These should be minimized, scoped to operations and described explicitly instead of hidden under a broad no-logs slogan.
The retention checklist
Identity documents
Not part of the account flow, so there is no document-upload record to retain.
Name, address and card
These fields are absent from the configuration.
Connection and request history
The production operator must confirm infrastructure logging settings and exclusions.
Order and payment records
Necessary service state; exact retention periods await the operator’s policy.
Crash and error data
The final policy must distinguish server diagnostics from traffic contents.
VPS files and snapshots
Your guest filesystem and any snapshot feature need their own security model. Host access cannot be ruled out merely by holding root in a VM.
Verification before trust
Read the final privacy document, compare its data list with the signup and billing screens, and check whether technical settings support the public wording. A signed canary or request ledger can add context only if it is authentic, current and independently checkable.
SilentVPS has no published signed canary, audited operational retention window or measured production history yet. The corresponding pages preserve a place for those disclosures without inventing evidence. You can already inspect the signup and order flow on this website.
Your applications have their own logs
Nginx, SSH, mail servers, containers and monitoring tools may log inside the guest. Review each service, its access rules and its rotation policy. Encrypt sensitive backups, terminate your own TLS and keep encryption keys outside unnecessary third-party systems.
Disk encryption is useful but has limits on a running hosted VM. It protects certain storage exposures; it does not turn a provider-operated hypervisor into hardware that you own. Plan for recovery and protect the administrative device as carefully as the server.
Four sizes. The same privacy baseline.
Monthly or annual billing, with 30% off the twelve-month total when you pay yearly. Prices are in USD; cryptocurrency amounts depend on the invoice exchange rate. Full root, KVM virtualization, NVMe, IPv4 and IPv6 are part of the target specification for every tier.
Veil
$13/month · $109.20/year. 1 vCPU, 2 GB RAM, 30 GB NVMe and 2 TB monthly transfer. A compact starting point for one lightweight service.
Shade
$33/month · $277.20/year. 2 vCPU, 4 GB RAM, 80 GB NVMe and 4 TB monthly transfer. More room for applications and everyday self-hosting.
Eclipse
$63/month · $529.20/year. 4 vCPU, 8 GB RAM, 160 GB NVMe and 8 TB monthly transfer. Space for a larger stack or transfer-intensive workload.
Obsidian
$118/month · $991.20/year. 8 vCPU, 16 GB RAM, 320 GB NVMe and 16 TB monthly transfer. The largest configuration for dense services and heavier compute.
Questions, answered
Can a working VPS use literally no data?+
No. Routing, scheduling, account state and payment confirmation require handling some information. A precise no-logs claim concerns which events become retained records and their purpose.
Which records does the service need?+
Configuration, account and order token, payment status, allocation state and limited diagnostics. Optional email exists only if supplied. Exact production retention windows await the operator’s final policy.
How can I verify the retention claims?+
Compare the final written data list with the actual signup and billing flow, infrastructure settings and any authentic current audit or signed disclosure. SilentVPS has no published operational audit or signed canary yet.
What happens if customer data is requested?+
A request can concern only records that exist. The operator must define the validated production response process in its own documents; no court jurisdiction or response history is fabricated on this website.
Does full root mean a host can never access my VM?+
No. Root controls the guest operating system, while the provider operates hardware and hypervisor layers. Encryption and restricted keys protect specific risks but do not erase that trust boundary.
Are anonymous signup and no logs the same thing?+
No. The first concerns the identity information collected; the second concerns records retained over time. Both need their own implementation and verification.
A useful next step.
MAKE YOUR NEXT MOVE QUIETLY
Find your serverYour infrastructure. Your identity stays yours.
Choose the resources you need. Keep the personal details you don’t need to share.