VPSRENTO
- We store three things: a hash of your access token, a billing ledger (transaction ID + amount), and the support tickets you send us. That is the list.
- We never collect your email, name, phone number, IP history, or anything about what your server does.
- This website runs zero trackers, zero analytics, zero cookies. View source and check — we’ll wait.
- A court order gets the ledger rows for an account, which the blockchain already publishes. Nothing else exists to hand over.
- Data lives exactly as long as your account. Delete the account and it is gone.
01 Who we are
VPSRento operates VPS hosting from fifteen jurisdictions and has done so since March 2021. This policy covers vpsrento.com, the client area, and the hosting services themselves.
The operating principle has been the same since day one: data we don’t hold is data that can’t hurt you. Not in a breach, not in a courtroom, not in an acquisition. Five years, zero customer identities on file — that sentence is the whole strategy.
02 What we store (the complete list)
| Data | Why it exists | Form |
|---|---|---|
| Access token hash | Authenticates you to the client area | A one-way hash. The token itself is shown once at creation and never stored. |
| Billing ledger | Accounting — a business must keep books | One row per payment: transaction ID, coin, USD value at time of payment, timestamp, the service it paid for. |
| Support tickets | So we can answer you | The contents of conversations you start in the client area or by PGP email. |
| Account configuration (optional) | Features you switch on | SSH public keys, sub-token hashes, a TOTP secret if you enable 2FA, firewall rules, reverse DNS records. |
That is the complete list. If a piece of data is not on it, we do not have it — there is no shadow profile, no “service improvement” telemetry, no fraud-score vendor quietly receiving a copy.
03 What we never collect
Identity. No email address, no name, no phone number, no date of birth, no country of residence. Signup asks for none of it because there is no signup form — payment creates the account.
Activity. No activity logs, no connection logs, no traffic metadata on the hosting side. We do not log what your VPS does, who connects to it, or where its packets go. Node storage is encrypted at rest.
Client-area history. We do not record which IP addresses you manage your account from. The client area keeps a list of your currently active sessions so you can revoke them — it is not a history, and it stores no IP addresses.
This website. No analytics, no tag managers, no pixels, no A/B tools, no heatmaps, no chat widgets. No cookies, period — the site sets none. (The client area uses your browser’s own local storage for preferences; that data never leaves your machine and we never see it.)
Don’t take our word for it. Open the source of this page: one stylesheet, one JavaScript file, one font request. There is no analytics endpoint to call. The strongest privacy policy is the kind you can verify with Ctrl+U.
One honest disclosure. This site loads its fonts (Inter, JetBrains Mono) from Google Fonts. Your browser makes a request to Google’s font CDN when you visit, and like any CDN it sees the request. If that bothers you, block fonts.googleapis.com — the site falls back to system fonts and works identically. We would rather point at the one third-party request than hide it behind a proxy and claim perfection.
04 What a court order could actually get
People ask this constantly, so here is the walkthrough. A valid court order from a hosting jurisdiction — the only kind we answer — demanding “everything on account X” would yield:
- The billing ledger rows for that account: transaction IDs, amounts, dates, services. Every satoshi of which is already public on the respective blockchains.
- The contents of any tickets you sent us. Lesson: don’t put secrets in tickets.
- Active configuration: SSH public keys (public by design), firewall rules, rDNS records.
It would not yield: who you are (we don’t know), your email address (doesn’t exist), your server’s activity (never logged), your traffic (never inspected), or your other accounts (tokens are unlinked hashes — even we can’t tell two accounts belong to the same person).
Physical seizure. Node storage is encrypted at rest, which protects against casual access to pulled drives. But a running VPS is a running VPS: if your threat model includes a datacenter visit with legal authority, encrypt your own volume with LUKS and keep the key far away from the server. That is operational advice, not legal cover — see our hardening checklist for the setup.
The record so far. In five years we have received zero valid orders from our hosting jurisdictions and handed over zero bytes of customer data. If that ever changes, the warrant canary changes first — it is PGP-signed and updated monthly.
05 Retention
Data lives exactly as long as your account, and not a day longer.
Delete the account in Settings and the following happens within 24 hours: services are wiped (random-overwrite before the block device is reissued to another customer), tickets are destroyed, configuration is destroyed, sub-tokens die with the parent.
One exception, and it identifies no one: the billing ledger rows remain, because they are our books and a business must keep accounts. A ledger row is a transaction ID and an amount. It contains no identity because none was ever attached to it.
06 Third parties
Paymento processes payments. It sees what the blockchain shows: a sending address, an amount, a timestamp, and our invoice reference — in practice, a transaction ID. It never sees your token, your services, or your tickets.
Beyond that, the list of third parties who receive anything from us is empty. No analytics vendors. No advertising networks. No support-desk SaaS — the ticket system runs on our own hardware. No email service provider, because we send no email. No CDN with tracking ambitions.
The single external request this site makes is the Google Fonts fetch disclosed in §03. That is the whole supply chain.
07 Your rights, by architecture
Most privacy regulations grant rights — access, rectification, erasure, portability — that companies then “process” within 30 days. We satisfy them by design, instantly, without a request:
- Access: log in. Everything we hold about your account is visible in the client area, because it fits on a settings page.
- Rectification: change it yourself. There is nothing to petition for.
- Erasure: delete the account. Gone in 24 hours, ledger rows excepted as above.
- Portability: your data is on your server. rsync it anywhere, any time, without asking.
You never need to ask us to exercise a right. That is deliberate, and it is the part of this policy we are proudest of.
08 Changes
Same mechanism as the Terms of Service: material changes are announced 30 days before they take effect, on the warrant canary page and a site-wide banner.
A frank note: a privacy policy is only worth what the company does when changing it. If this document ever grows longer and softer — new data categories, new “partners”, new legitimate interests — treat that as what it would be: a reason to leave, announced 30 days early so you can. Hold us to that.
09 Contact
Privacy questions: tickets in the client area — the only channel that exists. We answer our own policy — median first reply across all tickets is 14 minutes in 2026.