Security and compliance
Security for operators
How sign-in works
You sign in with your wallet (Sign-In with Ethereum). There is no password to steal. The platform stores no private key for you.
- The sign-in message includes a one-time code that expires in 5 minutes and works once.
- The message must name the platform's console address. A message made for another site is rejected.
- Your session is a random token in a cookie that the browser's scripts cannot read (HttpOnly), sent
over HTTPS only (Secure). Only a hash of it is stored on the server.
- Sessions last 30 days from last use and at most 90 days from sign-in. After that you sign in again.
- Sign out (in Settings, or the account menu) ends the session on that browser.
- Sign-in attempts are rate-limited per IP address (30 per minute).
Protect your wallet
Your wallet is your account. The biggest risks are:
- A fake site that asks you to sign. Always type the console address yourself or use a bookmark.
- A sign-in message that asks for more than a login. Read what the wallet shows. A sign-in message
should not ask to spend tokens.
- Malware on your device. Use a hardware wallet if you can.
- Anyone who has your seed phrase. Never share it, including with "support". The platform never asks.
Two-factor authentication
2FA is optional for operators and recommended. It uses an authenticator app (time-based 6-digit codes). Your wallet sign-in does not change: the code is asked for before sensitive actions.
To turn it on:
- Open Security (in your terminal menu, or
/account/security). - Select Set up two-factor authentication.
- Scan the QR code with an authenticator app, or add the setup key by hand if you cannot scan it.
- Enter the 6-digit code under "Code from your app" and select Turn on 2FA.
- Save the recovery codes shown under "Save your recovery codes". Each works once. Select
I saved these codes somewhere safe when done.
With 2FA on, these actions ask for a code: changing the wallet that receives your trading fee, removing a custom domain, inviting, removing or changing the role of team members, transferring ownership, deleting a terminal, managing API keys and webhooks, and generating new recovery codes. After a correct code, you are not asked again for 10 minutes on that device.
- Five wrong codes in a row lock code entry for 15 minutes.
- When you have 2 or fewer recovery codes left, the page warns you. Select New recovery codes to get a fresh set.
- To turn 2FA off, select Turn off 2FA and confirm with a current code or a recovery code.
- If you lose both the device and your recovery codes, contact support. There is no self-service
reset.
Sessions
- Security lists "Where you are signed in". Select Sign out on a session to end it, or Sign out all other sessions.
- Sign out on shared computers.
- Turning 2FA on or off starts a fresh session on the current browser.
Request forgery protection
The session cookie is SameSite=Lax. Every console request that changes something must also come from the console's own address (Origin check) and carry a per-session anti-forgery token. Requests from other sites are refused.
Your clients' security
- Clients trade from their own wallet. The platform and you cannot move their funds.
- Their browser holds a limited trading key ("agent key"), encrypted, which can place and cancel
orders but cannot withdraw. It expires after about 30 days.
- Your site is served with a strict content security policy and security headers, and shows only
your branding data as text.
Things only you can protect
| Item | Why it matters | What to do |
|---|---|---|
| Owner wallet | Controls the terminal | Hardware wallet, backups |
| Builder address | Receives fees | Separate wallet, keep >= 100 USDC on Hyperliquid |
| Billing notices, verification | Use a mailbox you control with its own 2FA | |
| Your DNS account | Custom domain | 2FA on the registrar and DNS provider; a hijacked DNS record could serve a fake site on your name |
Report a problem
Write to the contact listed in the platform's security.txt file at /.well-known/security.txt on the console address. Do not post exploits publicly.