An alias is a better starting point
Create an account workspace without a public identity profile.
Content revised · English
- Required
- Alias and password
- Optional
- Not requested
- Name / phone / address / ID
- Records remain
- Session and workspace data
The account fields
The current account form uses an alias and a password. Email is optional. No name, phone number, street address or identity document is requested by this application.
Where the boundary sits
Using an alias can reduce what you disclose in account fields. Browser activity, connection metadata, payment history and reused identifiers may still connect activity to a person; account design is only one part of the privacy picture.
Keep the account recoverable
Use a unique password and protect your credentials. An optional email may support future contact arrangements, but the application has no external email verification or recovery delivery service.
Questions, answered.
Do I need a public profile?
The account uses an alias. It has no public member directory and requests no public identity profile.
Does an alias prevent every kind of identification?
No. Reused identifiers, browser activity, public transaction history, domains and your own application can still link records.
Is email verification or TOTP enabled?
There is no outbound verification-mail service or TOTP enrolment in the current integration. Use a unique stored password and read the recovery boundary.
Are particular email providers required?
Email is optional in this local flow. If added, use an address you control; no external email verification or provider whitelist is claimed.
Can an invoice exist without a legal name?
The order and billing records use the account alias and configuration. A future production operator must confirm any statutory invoice information rather than copying another operator’s requirements.
Is there phone verification?
The local form has no phone-number field or telephone verification step.
Can an alias-based account face an AUP review?
Yes under the proposed launch rules. The conduct of the service, not the public identity field, determines policy compliance.
Does the account flow depend on the plan?
The local alias-based account is shared across the catalogue. Plan and region compatibility still determine the available configurations.