Security

PasswordsHashed with scrypt (memory-hard: N=217, r=8, 128 MiB per hash) and a per-user random salt. Older hashes are upgraded at your next sign-in. Plain-text passwords are never stored.
Sign-in protectionRate limits per network address and per account, a temporary lock after repeated failures, and the same answer whether or not an account exists.
Two-factor authenticationOptional authenticator-app codes (TOTP, RFC 6238) with single-use recovery codes. Codes cannot be reused.
SessionsHttpOnly, SameSite=Strict cookies (Secure in production). JavaScript cannot read them and nothing session-related is kept in browser storage. Only a SHA-256 hash of each 256-bit token is stored. Idle sessions expire. Changing your password signs out your other devices. You can sign out every session.
Confirmation for sensitive actionsChanging security settings, your phone number, withdrawals and operator actions need a recent password confirmation, plus a code when two-factor authentication is on.
Request protectionEvery state-changing request needs a per-session CSRF token and must come from this site. Cross-origin API access is off unless explicitly allowed.
Stored dataPhone numbers, verification references, withdrawal destinations and authenticator secrets are encrypted field by field (AES-256-GCM, envelope encryption with rotatable keys). Lookups use keyed hashes, not plain text.
BackupsBackups are encrypted and authenticated (AES-256-GCM) before they are written. The keys are kept separately from the backups.
TransportHTTPS is required in production. HSTS is sent on HTTPS requests. The live-data connection uses WSS and checks origin, session, message type and size.
HeadersStrict Content-Security-Policy (scripts only from this site), frame-ancestors none, nosniff, strict referrer policy, permissions policy and cross-origin isolation headers.
EnforcementRisk limits, order validation and account ownership checks run on the server. The browser is never the only check.
Audit trailSecurity and financial events go to an append-only log with a keyed hash chain, so tampering can be detected.
PaymentsFunds are credited only after a verified, replay-protected provider confirmation.
Third-party credentialsbinarytrade-online stores no Deriv tokens. Market data is public and unauthenticated.

To report a vulnerability, contact the operator.