No KYC signup: an alias, a password, no identity upload
Create an OmbraHost account with an alias and password. Email is optional; no name, phone number or identity-document upload is requested at signup.
Content revised · English
- Document collection
- No upload field
- Telephone verification
- Not requested
- Account scope
- Account interface
- Suppliers
- Future policies need review
The exact signup requirements
An alias and password create the OmbraHost account. Email is optional. The form does not request a legal name, postal address, telephone number or identity-document upload. Account data is kept in private application storage, separate from the public website.
A limited, accurate statement
A future operational policy must reflect the actual operator and suppliers. An exchange or payment intermediary may apply its own checks, regardless of what the hosting account form requests.
Privacy with accountability
Reducing identity collection does not excuse abusive workloads or remove lawful obligations. Read the use policy and manage the identifiers your own application collects from visitors.
What fewer signup fields do not change
A session cookie and private account, order and support records still exist. The site does not claim zero logging or guaranteed anonymity. Payment intermediaries, domain registrars and certificate issuers may have their own requirements; the account form cannot change their policies.
Keep account access and service delivery separate
Use a unique password and keep it securely. Outgoing recovery email is not connected, so an optional email address is not a working password-reset guarantee. The catalogue records plan, region and billing choices; transaction observation and infrastructure provisioning are separate integrations and are not connected.
Questions, answered.
What do I need for No KYC signup?
An alias and password are required. Email is optional. No legal name, address, phone number or identity-document upload is requested by the OmbraHost signup form.
Does this bind every supplier to the same rule?
No. A future operator and its suppliers must publish their actual requirements. Exchanges and other payment intermediaries can collect identity data independently.
Can I use an alias to ignore the use policy?
The proposed acceptable-use rules apply to the workload regardless of the account name. Lower data collection does not authorise harmful activity.
Is identity verification universally unnecessary for hosting?
No universal legal statement is made. A future operator must assess the rules, service and suppliers that apply to it before publishing a live verification policy.
Could the payment step still involve identity records?
Yes. A wallet source, exchange or another intermediary may impose its own checks. The authenticated checkout requests no identity upload and uses configured fixed receiving instructions. Public blockchain activity and records outside this website remain separate privacy considerations.
May I add identifying information voluntarily?
The optional email can be edited in settings, but avoid adding unnecessary personal data. The signup form does not need a legal name or address to create a workspace.
What if a lawful authority requests account data?
The launch operator would need a verified request process and an accurate retention map. An alias is not a promise that no records exist or that a lawful order can be ignored.
Does refund handling require an identity document?
No document-upload step exists in the account application. The proposed live refund process verifies account control and the refund destination; any eventual statutory requirement must be stated by the operator.