Private VPS accounts, payments and data practices

The registration flow asks for a username and password, with email optional. It does not request a legal name, postal address, telephone number or identity document. The application stores the username, password hash, any supplied email and account creation date. A pseudonym can separate the account from a public identity; it does not mean the account has no record.

Saved configurations contain the plan, billing cycle, operating system, location, currency, date and private order reference. A supplied hostname, public SSH key or notification email may also be stored. Contact messages retain their subject, message, reference and date, with a pseudonym or email when provided. Keep private keys and wallet recovery material out of these fields.

An invoice records the asset and network, destination, USD value, conversion rate, payable amount, expiry and status. Verified events can add transaction identifiers, amounts received and confirmation information. Those are reconciliation records, separate from the identity fields omitted at signup.

Bitcoin transactions are publicly recorded and addresses can be associated with earlier transactions. Optional email does not remove that ledger history. A wallet provider or exchange may hold other identifying records. Choose the exact supported network, follow the private invoice and avoid publishing an order token or transaction details alongside personal accounts.

The current website uses an essential session cookie for authentication and form security. The attempt limiter keeps a hashed value derived from the request category and connecting IP address. A hash is not an anonymity guarantee, and expiry of an attempt window does not itself prove deletion of the stored record.

The published privacy page also describes the current web-server access and error logs. Requested URLs, connecting IP addresses and other technical request data can appear there. An order reference in a URL may therefore enter a log. The website has no advertising pixels or third-party analytics scripts; that does not remove essential application or server records.

Application and session records are kept outside the public web directory. Passwords are hashed. The current application does not define automatic deletion periods for accounts, orders, messages or payment records. Invoice validity is not a retention schedule. Consult the privacy policy for the complete scope and request process rather than assuming immediate erasure.

The software you later install may create authentication, access, database or diagnostic logs inside the VPS. Review its settings, access controls and backups separately from the hosting account. Production infrastructure logging must also be validated; the catalogue does not establish a verified no-logs fleet.

Use the published privacy page for questions, correction and deletion requests. It identifies the official contact and explains that the contact form currently saves a message without sending an email notification. This overview does not replace that policy or promise universal anonymity.