Create your private workspace

Open Create account and choose an alias that is not already used. The local form does not ask for a legal name, street address or identity document. An alias keeps the account name separate from your public identity; it does not remove the session cookie or the records the application needs to keep.

Use a unique password and store it in a password manager before submitting. The server stores a password hash rather than the readable password. A guessed password, an exposed device or a reused credential can still compromise an account.

Email is optional in this account flow. It can provide contact context, but adding it connects another identifier to the account. The account application has no outbound mail delivery or automatic email verification. Its recovery page explains the current boundary rather than issuing a pretend reset email.

Submit the form, then open the workspace and account settings. Confirm the alias and optional email. Settings allow a password change using the current password; support tickets let you record a question. Do not expect a production welcome message, a working TOTP enrolment or a hosting allocation.

A website login is not an SSH key or a remote-desktop password. When a real service is connected, store those credentials separately and limit who can use them. Avoid putting passwords, wallet seed phrases or private keys in a support message.