Security is a system of boundaries—not a badge.

Account protection

Customer authentication supports verified email, modern password hashing, passkeys, Google sign-in, optional app-based two-factor authentication, session protection, CSRF protection, and login throttling.

• Email verification
• Passkeys and TOTP two-factor authentication
• Stateful Google OAuth
• Rate-limited authentication

Administrator isolation

The Filament operations panel requires an explicit administrator grant and separate required MFA in production. Trading records are read-only and authentication secrets are not displayed.

• Role-gated access
• Required administrator MFA
• Read-only trading resources
• No tokens, passwords, or recovery codes in tables

Browser and transport policy

The production application enforces HTTPS and modern browser security headers, including a nonce-based Content Security Policy, HSTS, frame restrictions, referrer controls, MIME-sniffing protection, and a restrictive permissions policy.

• HTTPS and HSTS
• Nonce-based CSP
• Clickjacking and MIME defenses
• Restricted browser capabilities

Broker and MCP authorization

Max AI Trading will use official provider authorization and never ask for a Robinhood password. Production MCP execution requires encrypted token storage, minimal scopes, revocation, session binding, consent records, and safe handling of provider errors.

• Official authorization only
• Encrypted credentials at rest
• Revocation and reconnect flows
• No brokerage password collection

Execution defense in depth

An environment-level execution gate and each user’s policy must both permit live actions. Order intent must remain unchanged between review and submission, and ambiguous outcomes must be reconciled before retry.

• Dual execution gates
• Policy checks independent of AI text
• Idempotent broker calls
• Audit, monitoring, and reconciliation