Security
What BotVault does with your keys.
BotVault is a hosted vault run as a small product. This page states exactly how your credentials are protected, what BotVault can see, and what it cannot. No marketing, just the mechanics.
Encryption at rest
Every credential value is encrypted with AES-256-GCM using a unique data key (DEK) per credential.
Each DEK is itself encrypted with a key-encryption key (KEK) derived per user via HKDF-SHA256 from a server-held master secret.
Account passwords are hashed with bcrypt and never stored in plaintext.
What BotVault can and cannot see
The server holds the master secret, so it can decrypt your values to serve them to your agents at runtime. That means BotVault is not a zero-knowledge system. Treat it the way you treat a hosted password manager like 1Password: you are trusting the operator and the infrastructure, and this page exists so that trust is informed.
What never happens with your values
- Your values are never written to logs.
- Values are returned only to authenticated, authorized bots.
Per-agent access
Each bot gets its own JWT token, signed with a secret separate from user sessions.
Tokens carry per-credential grants that you control from the dashboard.
Tokens have expiry dates and one-click revocation.
On the Claude Code path, the token lives in your OS keychain, not in a file or a prompt.
Every read is audited
Every credential fetch is written to your audit log with the bot's identity and a timestamp. The audit log is visible in your dashboard, so you can always answer the question: who read what, and when.
Transport and platform
HTTPS everywhere
All traffic between you, your agents, and the vault travels over HTTPS.
Strict CSP
The app ships a strict Content-Security-Policy.
Rate limiting
The bot API is rate limited to 60 requests per minute per token.
Hosting
Hosted on Vercel, with data in Turso (SQLite).
What BotVault is not
Not zero-knowledge
As explained above, the server can decrypt your values to serve your agents. That is a deliberate trade for runtime access.
Not a team secrets manager
BotVault is personal vaults only today.
No compliance certifications yet
BotVault is in public beta, run by a small team, and holds no compliance certifications yet. We would rather say that plainly than let you assume otherwise.
Found something?
If you find a vulnerability or anything that looks wrong, tell us through the feedback page. And if a bot looks compromised, revoke its token instantly from Bots in your dashboard.
Report via feedback