Security & disclosure
Security boundaries and the controls required before production.
This page documents preview behavior and launch requirements. Final operator details, legal terms, contact channels, and production commitments have not been established.
Preview boundary
The frontend is a demonstration. It does not establish that a backend, provider adapter, smart contract, or payment flow has completed a security audit. No SOC 2, encryption, uptime, or other certification claim is made.
Keys and wallet signing
Private keys and seed phrases must never enter the app. Provider credentials belong in server-side secret storage. A wallet signer should verify a bounded domain, nonce, chain, recipient, and expiry before signing.
Access and isolation
Production requests, results, files, jobs, sessions, and receipts must be scoped to an authenticated owner. Authorization checks belong on the server rather than relying on hidden frontend controls.
Input and output handling
Validate content types, file size, dimensions, schemas, tool-call history, and terminal completion. Sanitize untrusted text before rendering it; do not execute model-generated code or incomplete tool arguments automatically.
Disclosure process
A dedicated disclosure address, response targets, and testing scope have not been published for this preview. Before enabling live accounts, the operator must provide a verified private reporting channel and explicit authorization boundaries.