Trust · Your inbox is yours
Your mail is private, even from your admin
Brigham.ai reads a mailbox on behalf of one person. No one else’s runs, admins included, can see it.
Private to the person. Not to the role.
Being a workspace admin lets you manage the workspace. It doesn’t let you read a colleague’s mail through Brigham.ai.
How it’s built
Queried live
Brigham.ai asks the Gmail API when you ask a question. It does not copy your mailbox into its own database.
Almost nothing stored
Message ids, the thread summaries you have seen, and follow-up candidates. Enough to work, nothing more.
Drafts and approved sends
Reply drafts land in your Gmail Drafts folder. Sending is available, and each message waits for your approval. Compose access is a separate opt-in.
Calendar read first
Calendar access starts read-only. Editing events is a separate grant.
Access matrix
- You, in your own runs
- Your mail and calendar, within the scopes you granted
- A teammate’s runs
- No access
- Workspace admin
- No access
- Brigham.ai staff
- No routine access. See the Privacy Policy for the limited exceptions
- Sharing a thread
- An explicit, per-thread choice you make
Generated as you
Briefings and automations run as their owner. Your morning briefing contains your meetings and your threads, built from what you can see and nothing else. Mail you’ve read through Brigham.ai is also untrusted content, so a message in your inbox can’t make Brigham.ai act.
Questions, answered.
Is this tested?
Yes. A core test confirms that one person’s runs can’t read another person’s mail, and that a revoked connection stops working at once.
Does Google data train models?
No. We don’t use customer content to train models, and our use of Google data follows the Limited Use requirements described in the Privacy Policy.
Keep reading.
Keep your inbox yours
Request access and connect your mailbox read-only.