Privacy-focused hosting, clearly stated

OmbraHost is built around private account creation, anonymous signup by design and client control of a self-managed VPS. We do not regularly monitor client activity and do not inspect a client's VPS content. The goal is to keep the client's identity and hosting activity separate from any unnecessary collection.

An alias and a password are enough to open an OmbraHost account; an email address is optional. The form does not ask for a legal name, phone number, postal address, date of birth or identity document upload. Standard signup does not use traditional KYC verification, and no outgoing activation or recovery email is currently connected. This is the OmbraHost account flow; an exchange, wallet provider, domain registrar, certificate issuer or other provider may have separate requirements.

OmbraHost does not store activity logs generated by clients' use of VPS instances. We do not keep records of websites visited, commands executed, applications used, traffic, connections, DNS requests, running processes or content inside a client's VPS. We do not regularly inspect client files, databases, websites or applications. The client controls the VPS and remains responsible for the software, services, licenses and content operated there.

OmbraHost does not ask for passports, identity cards, proof of address or other KYC documents to open the standard account. It does not require a legal name, phone number, postal address or date of birth. Payment is configured for cryptocurrency routes rather than payment cards or bank transfers. The account flow is deliberately limited to the information needed to create and protect the workspace.

The private account space keeps only the operational records needed for the workspace and payment: an alias, a protected password hash, an optional email address, configuration choices, orders, invoices, payment requests, server quote snapshots, pricing timestamps and support correspondence. These records remain outside the public document root. Receiving destinations and payment execution details are private and are not published in public articles or reference files.

OmbraHost supports BTC, ETH, SOL, LTC, native TRX, USDT ERC-20, USDT TRC-20 and USDC ERC-20. An authenticated payment uses a server-retrieved USD market rate and an expiring quote valid for twenty-five minutes. No card number or bank account is requested by this payment. A public blockchain transaction, a wallet address or an exchange record may nevertheless link payment activity to information outside OmbraHost. No blockchain transaction observer is connected, and a payment status or historical receipt does not prove that a transaction was independently observed or that infrastructure was provisioned.

OmbraHost does not scan, index or copy files, databases, websites or applications stored in a client VPS as part of the ordinary operation of the service. The public site has no advertising tracker or behavioral profiling script connected, and account information is not sold for advertising purposes. A privacy-focused account is not authorization to access another person's system or content.

The account space uses a session cookie for authenticated state. The public entry may remember a manual language choice for one year in the ombra_language_choice preference cookie. Country selection uses a local DB-IP dataset and does not transmit the visitor's IP address to a geolocation provider or store it in that country database. Browser preferences and country estimates may be wrong; explicit language URLs and the language menu remain available.

OmbraHost keeps account, billing, payment and support records only for the operational, security and legal purposes related to the service. Retention may differ for inactive accounts, invoices, payment requests, support correspondence, security events, backups and legal retention. The private runtime environment does not build a permanent identity profile for marketing purposes, and no client activity logs from inside a VPS are kept. Deletion and access requests remain subject to applicable records and legal obligations.

A quote, an order record and a verified payment are separate events. The current application has no connected blockchain observer or automatic infrastructure provisioning integration. Creating an account or preparing a payment does not activate a server. Refund, cancellation, service level and provisioning terms are governed by the applicable OmbraHost policy and operator confirmation; this privacy policy maintains a clear boundary between the account and payment.

OmbraHost may be used for legitimate websites, applications, software development, testing, VPN services, private infrastructure, remote systems and other lawful workloads. Email spam, phishing, credential theft, malware distribution, fraud, attacks against third-party systems, unauthorized access and child sexual abuse material are prohibited. Abuse reports are reviewed individually against the available facts. Except in serious or urgent cases, OmbraHost may contact the client and seek a reasonable resolution; serious abuse, security threats or a binding legal or network obligation may require immediate restriction.

OmbraHost does not process, enforce or take any action solely because a notification under the United States Digital Millennium Copyright Act (DMCA) has been received. A DMCA notification alone does not suspend, restrict or terminate a client service. Other abuse reports are handled separately and reviewed individually.

The standard OmbraHost flow allows an alias, a password and optionally an email instead of a legal identity. No identity document upload is required. The VPS privacy commitment excludes logging of ordinary activity and inspection of content within the client's VPS. Cryptocurrency payment avoids card and bank data in the OmbraHost payment form. These measures form the practical basis of the service's anonymity-first approach.

OmbraHost reserves the right to restrict or terminate a service involving serious abuse, prohibited activity, security threats or a situation where action is required by applicable legal or network obligations. Except in urgent or serious cases, the service may first be restricted while the client is contacted and a reasonable resolution is considered. Privacy remains a fundamental principle, but it does not relieve the client of responsibility for lawful use.