Security and what's missing
What happens to your credentials and your content, and an honest list of what this platform does not do yet.
Credentials
Every token, API key and password you connect is encrypted before it is stored, and decrypted only at the moment a tool needs to make a call. They are never shown back to you in the interface and never included in a run transcript.
You can revoke access from the other side at any time, and it takes effect immediately: remove the app from your Google account, revoke the bot token in BotFather, end the session in Telegram's device list, or roll the key in your OpenAI account.
Where your content goes
When an agent runs, the material it is working with - the emails it read, the messages it saw - is sent to your AI provider under your API key, and is governed by your agreement with them. It is not sent anywhere else, and it is not used to train anything here.
Run transcripts are stored so you can audit what happened. They contain whatever the agent read and wrote, so treat them as being as sensitive as the accounts behind them.
Agents act with your authority
An agent has exactly the permissions of the accounts you gave it, and it acts as you. It cannot tell a genuine customer email from one crafted to manipulate it, so be deliberate about which agents can send messages to the outside world, and read the first few runs of anything new. Responsibility for what your agents do rests with you - see the Terms of Service and Privacy Policy.
Not built yet
- Message-arrival triggers. Agents cannot react the instant something comes in. Poll on a schedule instead.
- Rich email. Sending is plain text only, with no formatting and no attachments.
- Full email bodies. Agents read sender, subject and a preview snippet, not the whole message.
Now available
- Tool approvals. You can now require sign-off before an agent sends a message or takes any other action. Mark individual tools as "requires approval" on the agent's edit page - the agent pauses mid-run and waits until you approve or reject on the Approvals page. See the Tool approvals help page for details.
Still stuck?
Start with the run transcript - it answers most questions about what an agent did and why. If the behaviour still does not make sense after reading it, the instructions are the next place to look.