Skip to main content
On this page

Account security

Your account holds prepaid credit and the keys to your agents, so this page states every way the platform proves it is you: what you sign in with, the second factors you can add, the one proof a sensitive action asks for, and what support will never ask you for.

Signing in#

Three ways reach an account, and any of them works with a second factor:

What you useWhat happens
Email and passwordThe password is checked, then your second factor if you have one
A one-time code by emailYou ask for a code on the sign-in page and type what arrives; the code is single-use and expires
A passkeyYour device signs a challenge with the passkey; nothing secret leaves the device

A passkey can also carry the whole sign-in on its own when you set it up: the browser asks for your fingerprint, face or device PIN, and the account opens without typing a password. Passkeys are bound to this site's address, so a look-alike domain cannot use one.

Second factors#

A password or email code alone is one factor. Add a second one in Settings → Security and the account asks for it at sign-in:

  • An authenticator app (TOTP). Scan the setup code with an app such as Aegis, 1Password or Google Authenticator, and type the six digits the app shows. Enrolling and turning the factor off both require you to confirm it is you first.
  • A passkey. Register the device (or security key) you will sign in with. Each passkey can be named and removed separately, so losing one device does not force you to drop the factor.
  • Recovery codes. Ten single-use codes shown once when you set a second factor. Keep them somewhere that is not the device with the factor. Each code signs you in alone; regenerating them requires your step-up proof and invalidates the old set.

At least one recovery method is the point: with two independent factors (for example an authenticator app and a passkey on another device) a lost phone is an inconvenience, not a locked account.

Confirming it is you#

Some actions are irreversible or change how you sign in: changing the password or the email address, turning a second factor on or off, adding or removing a passkey, regenerating recovery codes, and revoking an API key. The platform asks you to confirm it is you before them, and the confirmation is valid for ten minutes.

The proof is one factor, never a pair:

  • a passkey, if the account has one : one tap, the same ceremony as signing in;
  • an authenticator code or a recovery code, if the account has an authenticator app;
  • the password, only for an account with no second factor at all.

If the account has a second factor, a password alone is not a confirmation and is refused before it is checked. The confirmation dialog shows which one it wants and the action you are confirming, and it never shows a password field beside a code field. If your passkey cannot be used in this browser (for example a browser without WebAuthn), the dialog says so and tells you which other proof the account has, instead of offering something the gateway will refuse.

A confirmation code is single-use: the same code cannot approve two actions, and an expired or reused one is refused and the dialog asks again.

Losing a device#

If the device holding the only second factor is gone:

  1. On the sign-in page, ask for a factor reset. The request is rate-limited and sends a confirmation link to the account's email address.
  2. Confirming the link removes every second factor (authenticator app, passkeys and recovery codes) and revokes every session, so nothing survives that was signed in before the reset. The password and the address stay.
  3. Sign in with your password and the emailed code, then set up a new second factor and a fresh set of recovery codes.

Recovery codes work while you still have them. Write to support@rackduck.com only if neither path works: support can explain the process but will not remove a factor for you on request alone.

What support never asks for#

The operator's support address will never ask for your password, an authenticator code, a recovery code, an API key, or a copy of a payment's private key : not by email, not in the dashboard and not on social media. A message that asks for any of these is not from the platform. Code, recovery-code sets and keys are secrets: the platform stores what it needs to verify them, never the values themselves in readable form.

The security page states what the platform guarantees about your data, the machines and the money; this page is only about proving who you are.

This site uses only the technical cookies the sign-in and the security need. No analytics, no advertising, no tracking. Cookie policy