Account
The website records a username, a password hash, an optional email address and the account creation date. The registration form does not request your name, postal address, telephone number or identity document.
Less data. Clear boundaries.
A pseudonym can keep your public identity separate from your account. Here is what the website records, why those records exist and what a private account does not conceal.
Account and configuration data
Server configuration
Saved orders contain the selected plan, billing cycle, operating system, location, currency, creation date and private reference. A hostname, public SSH key and contact email may also be saved when supplied.
Messages
The contact form records the subject, message, reference and date, with an optional pseudonym and email. Supply only the information needed to handle your question.
Payment records and public networks
A crypto invoice stores its currency and network, destination address, dollar value, conversion rate, payable amount, expiry and payment status. Verified payment events can add transaction identifiers, received amounts and confirmation information. These records support reconciliation and order tracking.
Several supported payment networks have public ledgers. Wallet addresses, transaction amounts and identifiers can be visible independently of this website. Paying in cryptocurrency does not erase a public transaction or guarantee anonymity. Your wallet provider and exchange have their own data practices.
Conversion rates are requested from Coinbase or its backup provider Kraken by the server. The rate request does not send the order reference, username, wallet destination, payment amount or contact message. No bank card profile is stored by this website.
Sessions, anti-abuse checks and trackers
The website uses the silentvps_local session cookie for authentication and form security. It is restricted to the site path, uses HttpOnly and SameSite=Lax, and uses the Secure flag on HTTPS. Authentication pages and the contact form can create a session. Editorial pages do not create a fresh session for an anonymous visitor without an existing session cookie.
Form submissions use anti-forgery tokens and attempt limits. The attempt limiter stores a SHA-256 value derived from the request category and connecting IP address, with a five-minute attempt window. Hashing this value does not make it anonymous, and expiration of the window is not a guarantee that the stored row has been deleted.
The website includes no advertising pixels or third-party analytics scripts. Fonts, logos and interface assets are served locally. The current web-server configuration keeps access and error logs; access records can include the connecting IP address, requested URL, user agent and referrer. An order reference in a URL can therefore appear in a technical log. Infrastructure logging must be assessed separately from the account form.
Storage and retention
Application records and session files are stored outside the public web directory. Passwords are stored as hashes rather than readable passwords. Private order references can reveal order and payment information to someone who possesses them; keep them confidential.
A payment quote lasts 25 minutes and a saved configuration continuation lasts 30 minutes. These are validity windows, not deletion periods for the underlying order or invoice.
The current application does not define automatic deletion periods for accounts, saved orders, contact messages or payment records. A fixed retention schedule and any legal accounting requirements must be established by the operator. This page therefore makes no promise of immediate or automatic erasure.
Questions, access and deletion requests
Write to [email protected] to ask about your records, correct information or request deletion. Identify the relevant account or order privately and explain your request. Do not include your password or wallet secrets. The site has no self-service account deletion tool; the contact form records a message without sending an email notification.
Rights, exceptions and the competent supervisory authority depend on the applicable data-protection rules. Where those rules apply, a request may cover access, correction, deletion, restriction or portability. Data required to resolve a dispute or meet a legal obligation may need to be retained. The CNIL reference below explains the information a controller must provide.
Operator, recipients and purposes
SilentVPS operates from the United States. The official contact for privacy questions is [email protected]. Account and order records are used to manage access, configurations and payments; messages are used to handle your request; session and attempt-limit records protect authentication and forms.
The operator handles the application's stored records. The email provider processes messages you send by email; a wallet, exchange or public network processes transfers made through it under its own practices. The server-side conversion-rate provider receives currency requests rather than your account details. A valid legal demand may require disclosure of records actually held. This page does not promise immunity from such demands.
Where a particular data-protection law applies, processing must rely on the corresponding legal grounds, such as steps requested for an order, contractual administration or proportionate security interests. This page does not claim an independent compliance certification or a verified logging policy for every infrastructure provider.
Tracking choices and policy changes
No cross-site tracking or advertising pixels are used. Browser Do Not Track settings do not change the essential session and security processing described here. This website does not sell personal information or share it with an advertising network.
This version takes effect on 9 October 2026. Significant changes to the purposes or practices described here will be identified on this page with an updated date. Questions about the version relevant to your records can be sent to [email protected].