Accounts and access

No. The intended signup flow uses a unique username and password without requesting an email address, phone number, or identity document. The Acceptable Use Policy and applicable legal obligations still apply.
Link to this answer ↗

Recovery codes are shown once when the account is created. Store them offline and separately from the password; they are the recovery path when no email address or phone number is attached to the account.
Link to this answer ↗

The account may not be recoverable because support has no verified email or phone identity to fall back on. Never assume that a wallet transaction, username, or support message alone proves account ownership.
Link to this answer ↗

Add a supported SSH public key, such as Ed25519 or ECDSA P-256. Never paste a private key, seed phrase, recovery code, password, or API secret into the dashboard or a support request.
Link to this answer ↗

API secrets should be displayed only when created and stored as hashes by the service. Revoke a key or active session if it is exposed, and use a separate key for each system so access can be withdrawn independently.
Link to this answer ↗