The security behind Brea.
Here is exactly how your data, your keys, and your account stay protected.
- ✓CASA Tier 2 verified
- ✓Never trained on your data
- ✓Encrypted in transit & at rest
Updated Aug 2026
01 / Credentials
Your keys never meet the model.
Passwords, API keys, and tokens are stored encrypted and injected server-side at the moment a tool runs, outside the machine your agent runs on. The AI works with references, never raw secrets.
model requests
gmail.create_draft { account: "ref_8f2a…" } // no secret in context
broker verifies
owner ✓ · scope ✓ · pinned to your account // server-side
key injected
authorization: •••••••••••••••• // never enters the chat
result returned
201 · draft ready for your review // key stays behind
Fig. 01: one real tool call. A reference is all the model ever holds.
So even if the model is asked to reveal a key, it has nothing to reveal.
02 / Data handling
What Brea does. What it never will.
Brea always
Encrypts everything. TLS on every connection. Authenticated encryption at rest, with every secret sealed to your account alone.
Asks before it matters. Important actions wait for your approval. Email goes out as drafts you review.
Keeps the receipts. A clear, reviewable history of every step your agent takes.
Runs you a private machine. A dedicated, isolated instance per customer, with its own encrypted storage.
Deletes when you say so. Disconnect an app and access dies instantly. Close your account and everything goes with it.
Brea never
Trains on your data. Your conversations and files never teach a model.
Shows the model your keys. Credentials join server-side, at call time. The model only holds references.
Shares your instance. No other customer touches your machine or your storage.
Sells your data. Not to advertisers, not to partners, not to anyone.
Keeps secrets after you leave. Credentials, model keys, and workspace are all destroyed on deletion.
03 / Infrastructure
A private machine, just for you.
Your agent does not live in a crowd. It runs on its own isolated instance: provisioned when you join, destroyed when you leave.
- Compute
- One dedicated instance per customer. No shared runtime, no noisy neighbors.
- Storage
- A private encrypted volume. Secrets stay encrypted at rest, sealed to your account.
- Network
- No public inbound access. Internal services live on a private network.
- Runtime
- The agent runs a short allowlist of commands inside its own workspace, and nothing else.
- Deletion
- Account deletion destroys credentials, model keys, and workspace together.
04 / Compliance
Independently assessed.
Brea has passed the App Defense Alliance's Cloud Application Security Assessment at Tier 2, the security bar Google requires before an app may work with restricted account data like Gmail.
Responsible disclosure
Found something? Email [email protected]. A human reads every report.
05 / Questions
Asked, answered.
More questions? Email us
By now your agent could already have started.
Your to-do list, handled. Connect your tools, send a text, and let Brea take it from there.