Security

Financial authority stays with the owner#

AI proposals and integration credentials cannot authorize funds. FloFi does not custody private keys or seed phrases. Financial execution requires the supported path’s fresh artifacts, explicit review and applicable owner wallet authorization.

Wallet proof, integration authentication and a transaction signature serve different purposes. Read Wallet Authorization before connecting an integration.

Scope reads and handoffs#

Developer keys authenticate server projects and are stored as digests. Live keys and mainnet strategies are refused in the sandbox release. Browser-origin Developer API requests are rejected. Approval handoff secrets travel in URL fragments, and execution status sharing is off by default.

Absent, unshared and another project’s execution resources return the same not-found response. Account changes, expired artifacts, mismatched hashes and unavailable capability paths fail closed.

Evidence is not a blanket certification#

Controlled forks, public read-only checks and exact owner testnet runs establish different facts. Preserve the original evidence class and the documented network, asset and operation. Engineering history and certification records remain in their primary repository documents.