What Sayso sees, keeps and never has.

Receives

The wallet address, each transaction before signing (to, data, value), the rules the owner signed, and anything the agent’s builder chooses to pass as context. Put no secrets in it.

Keeps

Every decision, in a signed log where each entry links to the one before; the owner’s signed rules; the Telegram chat the owner linked, so that questions can reach them. Log entries are kept for good: they include the rules’ text, the context the agent’s builder passed and the linked chat id (Privacy).

Never has

Any key of yours, or your money. With the SDK your agent signs; with a Safe, Sayso holds one of three keys and can only add its signature.

Outside services see transaction details, never keys: a simulation node (Alchemy), token data services, the decision model (TypeSafe) for unclear cases, and the rule compiler (OpenRouter) for the owner’s rule text, Telegram for the approval messages, Supabase for the dashboard’s copy of the decision log, and Cloudflare, in front of the check server. Details on the privacy page.

• Your rules are signed by the owner with their own wallet. The agent can never change them, and nothing the agent says reaches the judge as an instruction.
• Every verdict is signed for that wallet, that transaction and that chain, with an expiry, and the SDK checks it before signing.
• Every decision is signed and kept in a log where each entry links to the one before.
• Sayso’s own keys are held in AWS KMS.

• The Sayso API key leaks. It can ask checks for that one wallet and read the answers. It cannot change rules, approve, sign or move money. Message @saysoio at once.
• The agent’s key is stolen. The thief can sign without the SDK. Move the funds to a new wallet and register that one. With a Safe cosigner, the agent’s key alone moves nothing.
• The owner’s key is lost. The rules in force stay, but nobody can sign new ones for that wallet. Use a new agent wallet with a new owner.
• Something looks odd. Message @saysoio on X.

• Not externally audited yet. Our own reviews are done by separate AI agents, not a security firm. A full outside audit comes after we raise money.
• The Safe cosigner runs on the Base Sepolia test network today. On Base mainnet it opens first to a few design partners who accept that it is not externally audited.
• Contracts Sayso cannot read are at best “ask”, never “allow”. For an agent wallet, your rules can name your own contracts and functions; a listed call is then allowed only when the simulation shows nothing at stake.
• Permits, x402 payments and signed logins are not checked by Sayso’s server yet. In enforce mode they follow your signatures setting.
• Chain data can be up to 2 minutes old. A transaction that depends on one sent seconds earlier can show as “fails in simulation”.
• Approvals only on Telegram for now.