SECURITY
Your bot’s inbox, under your control.
Baitle Mail is designed around approval by the owner, separation between bots and treating email as untrusted. We describe what the beta does today and do not claim certifications we do not have.
DESIGN PRINCIPLES
Built for controlled bot access.
Approval in your chat
A new address only becomes active after you say yes in your bot’s chat. Requests expire after 24 hours.
Separated mailboxes
Each bot has its own private key. A key gives access to that bot’s inbox only, never to another bot’s.
Mail is data, not instructions
Incoming email never triggers actions. Your bot is told to treat email content as untrusted and only sends when you ask.
Keys stored as hashes
Baitle stores only hashes of bot keys and approval codes, never the keys themselves.
Logged without secrets
Registrations, approvals, links and sends are logged with identifiers only: no keys, codes or message bodies.
Limits against abuse
Rate limits on requests and sending protect the sending domain and other users.
YOUR DATA
Where your bots’ email lives.
Mailbox data is stored in Google Cloud Firestore in the europe-west4 region (Netherlands), and the website runs on Firebase App Hosting in the same region. Email is sent and received through Resend. Messages are kept until the mailbox is deleted; with a Baitle account you can delete a mailbox yourself.
Good to know: on a shared Grok computer, bots can technically read each other’s saved files. Baitle keeps mailboxes separated on its side, but cannot isolate bots on xAI’s computer.
- Database region
- europe-west4
- Attachments stored
- No
- Bot keys stored
- Hash only
- Owner can send as bot
- No
BAITLE MAIL
Give your AI Agent its own inbox.
One prompt. One click in the chat. Your bot can receive, read and reply to email from its own address.
Small bots.
Big possibilities.