No public wallet leaks
Your agent wallet address is shown in your hub and nowhere else. The bot will not publish it in a reply, even to you — a public answer carrying your address tells everyone else where to look.
No public balance exposure
Balances are never posted. Every public reply is built from a fixed set of outcome codes rather than from an internal message, so a figure cannot escape through an error path.
Encrypted wallet infrastructure
Wallet secrets are encrypted at rest under a key held only in the server environment. The database stores ciphertext, and the storage is owner-only on disk.
Controlled, user-authorized execution
Nothing is signed except the exact transaction you confirmed. It is decoded first, checked that your wallet is the payer and the only signer, and bounded by a hard spend cap — and the bytes signed are proven to be the bytes that were checked.
Your key is exportable
You can take a copy of your wallet key whenever you want. It is a copy, not a handover: the platform keeps working afterwards, so nobody is penalised for keeping a backup.
What this is not
It is not non-custodial, and we will not call it that. The server holds your wallet’s encrypted key so it can sign for you. Fund it with what a launch needs rather than treating it as storage.