Built to be trusted with your keys.
Brohns acts on your behalf, so security isn't a feature — it's the foundation. Here's exactly how your data and the keys you connect are protected.
Encrypted credential vault
Every third-party key you connect (Google Maps, Hunter.io, Resend/SMTP, Claude, and the rest) is stored encrypted at rest. Keys are never displayed back to the browser after you save them.
Server-side-only key access
Secrets are decrypted only on the server, just in time, to run a tool you approved — never in your browser and never in the client bundle. Every access is logged.
Per-ecosystem data isolation
Each ecosystem is a walled-off world. Agents only ever see the context of the one ecosystem they belong to — never the store, the database, or any other ecosystem. Your data is scoped to your account with database row-level security.
Approval-first by default
Agents propose; you approve. Nothing outward-facing — an email, a reply, a published post, ad spend — happens until you say so. More autonomy is something you grant deliberately, step by step, once trust is earned. We never send automatically out of the box.
A visible activity timeline
Every action an agent takes is written to a timeline you can read: what it did, what's waiting on you, and the time it saved. Nothing happens silently.
Responsible disclosure
Found a vulnerability? Please email security@brohns.com and give us a reasonable window to fix it before disclosing. We appreciate your help keeping Brohns safe.