What can your VPS host see?

What can the operator of a KVM host see?

Everything the virtual machine is made of. A KVM VPS is a process on someone else's server. Its disk is a file or volume on the host, its RAM is host memory, and its network card is a virtual interface plugged into the host's network. Being root inside the guest gives no control over any of it.

The standard tools of a KVM host show how direct that access is. libvirt's virsh opens a guest's serial console, reports traffic counters per virtual interface, and dumps the memory of a running guest to a file for analysis, optionally without pausing it. This describes what any KVM host can do, not how a given host is run. For your own planning, assume that whoever administers the physical server can use this access.

What does VPS With Crypto keep about me?

Here is the complete list. What billing and running a VPS need is kept: your account number, plus an email if you added one; every top-up and order (amount, coin, network, transaction ID, date); and for each VPS its name, plan, rental length, city, system, SSH public key, IP addresses and dates, with the temporary root password when you gave no key, which stops working once you change it. A referral code is kept only if the link you came through carried one. The data-centre network gear is not ours. Records are handed over only on the order of a Panamanian court.

You sign in with an account number alone; adding an email is up to you. No KYC: signing up and paying take no identity document, no selfie, no card and no phone number. The privacy policy is the reference text; this page only maps it next to the technical layers.

Does paying in crypto without KYC make me invisible?

No. No KYC is not invisibility: every payment sits on a public blockchain, our billing links your account number to your orders and IP addresses, and your traffic crosses the data-centre network.

A Bitcoin, Ethereum, Tron, Solana or Litecoin payment is public. Anyone who learns the transaction ID or the receiving address can read the amount and the time, and follow the coins backwards. If they left an exchange that verified your identity, that exchange can tie the withdrawal to you. Incoming payments are checked against public sanctions lists of blockchain addresses, and funds sent from a listed address are not credited.

What no KYC does change: there is no ID scan, selfie, card or phone number on file to leak or hand over. Which hosts ask for ID, and when compares that part across providers.

What does the data-centre network see?

The envelope of every connection. Each packet in and out of the VPS crosses network equipment run by the data centre. SSH and TLS encrypt what is inside a connection, but source and destination addresses, ports, packet sizes and timing stay readable to every network along the way. The DNS lookups your server makes go to whichever resolver it is configured to use, in clear unless you set up encrypted DNS. Your VPS runs in a data centre in the city you pick, on IP addresses registered in that country (US, GB, NL or DE in the registry whois).

What happens to my root password and SSH keys?

With a key, only the public half ever leaves your machine. You log in as root over SSH. Add a public key at checkout and password login stays disabled; skip it and the team sets a temporary root password, shown in your dashboard, that you change with passwd the first time you log in.

A temporary password is created by the team and shown in your dashboard, so treat it as known to others until you replace it. Change it with passwd at your first login, add a key, and turn password login off. The SSH security guide has the exact steps. Nobody from our team will ever ask for your account number, your root password or your private SSH key, by email or in a chat.

What does encryption on the VPS protect?

It depends on where the keys live.

• Disk encryption inside the guest, such as LUKS, protects a disk image copied while the VPS is off. While it runs, the key sits in guest memory, which the host can dump.
• TLS and SSH protect data between machines, not on them.
• End-to-end encryption keeps content unreadable on the server itself. Encrypted rooms on a Matrix homeserver are stored as ciphertext; the server still knows who talks in which room, and when.
• Backups encrypted before upload stay unreadable wherever they are stored.

The rule behind all four: data the server must process in clear can be read by whoever controls the server. Data that arrives encrypted, with keys that never touch the VPS, cannot.