What we store, and what we do not.

What the order system stores

• An order reference and the configuration you chose (plan, location, size, term, add-ons, operating system).
• The price, the asset you chose to pay in, the invoice status and timestamps.
• A hash of your account access key. The key itself is shown once and not kept.
• The contact address, only if you choose to enter one.
• A transaction id, only if you choose to paste one.

What the order system does not store

• Your name, postal address or identity documents. None are requested.
• A password. There are no passwords, only the access key.
• Third-party analytics or advertising identifiers. The site uses no tracking scripts.

Web server and network data

The web server can record visitor IP addresses in access logs. The operator should disable IP logging for this site or truncate addresses, and delete any logs that remain within a short, stated period.

Session cookies are used for sign-in and form protection. They are not used for tracking.

What happens inside your server

Your VPS is yours. We do not publish or sell its contents and we do not read them as part of normal operation. AnonVPS, like any host, controls the hypervisor, so a VPS cannot be made safe against a hostile host. RAM-only plans and disk encryption reduce what is left behind on hardware. They do not change that trust relationship. Read privacy architecture for the details.

Legal requests

If a legal request arrives, we can only hand over what exists. The list above is that data. See the law enforcement policy.

How to read a no-logs claim

A useful policy lists data, not intentions. For any provider, ask four questions: what is collected at order time, what is collected at the web server and network layer, how long each item is kept and what happens when a legal request arrives. The sections above answer those questions for AnonVPS. Where something is described as something the operator should do, it is a commitment to hold the operator to rather than a technical guarantee.

What you can do to hold less of yourself

• Leave the contact field empty unless you want order updates.
• Pay with a coin that suits your threat model. See paying with Monero.
• Use a RAM-only plan for workloads that should leave no state on disk.
• Encrypt storage on persistent plans. See LUKS with remote unlock.

Common questions