Privacy deserves a readable record

The OmbraHost catalogue presents hosting configurations with their resources, compatible regions, operating systems and full USD billing-cycle totals. You can create an account, prepare a configuration, request a cryptocurrency quote and keep order and support records in your workspace. Catalogue specifications describe the configuration to evaluate; they are not proof of reserved capacity or a delivered service.

Account signup uses an alias and password; an email address is optional. Passwords are stored as protected hashes. No identity document is requested for account signup.

The application keeps account details, selected configurations, orders, invoices, payment requests, quote snapshots and support messages in private server-side storage outside the public website. Account privacy does not remove any requirements imposed by a domain registry, certificate issuer or infrastructure provider.

A manual language choice is remembered for one year in a preference cookie. When language selection uses an estimated country, the connection address is looked up in a local DB-IP country database. This lookup does not send the visitor’s IP address to a geolocation provider or store it in that country database.

This statement applies only to country lookup. Server security logs and account records may contain personal data. Country estimates and VPN locations can be inaccurate; every language edition remains available through the language menu.

Eight asset-and-network routes cover BTC, ETH, SOL, LTC, native TRX, USDT ERC-20, USDT TRC-20 and USDC ERC-20. USD quotes use retrieved market rates and expire after 25 minutes. Checkout identifies the chosen network, quoted amount and expiry so you can review the request before sending funds.

No independent blockchain transaction observer is connected. A payment request, receiving address, submitted transaction reference or account status does not by itself establish verified receipt of funds. Review the payment guides and the exact checkout network; cryptocurrency transfers cannot be treated as confirmed merely because a request was created.

No automatic infrastructure provisioning or outgoing email service is connected. Creating an account, choosing a configuration or recording a payment state does not demonstrate that a server has been delivered, resources reserved, software licensed or a message sent. Actual availability and fulfilment need separate confirmation before you rely on a service.

OmbraHost has not published a legal-request history, audited request statistics, an independent security or no-log audit, or a warrant canary. The absence of a published report must not be interpreted as a zero-request or zero-log claim.

Account activity, billing records, security events, support messages and customer traffic are different data categories. The privacy notice describes current application practices and the retention decisions that still require an operator-specific schedule; this page does not promise an automated deletion or zero-log control.

A meaningful legal-request report should distinguish requests received, requests considered valid, requests challenged and disclosures made, with reporting periods and publication limits. A canary or an absence-of-order statement would not replace an independent security audit. Legal restrictions and reporting delays may limit what an operator can publish.