Security
How we protect your keys and data
What Baseboard does, in full. Each line is enforced in code.
Keys
- Every API key and OAuth token is encrypted with AES-256-GCM under its own data key.
- A sealed key is bound to its workspace, project and provider. Copied anywhere else, it won’t decrypt.
- Only the broker can decrypt. It opens a key for one provider call, then drops it.
- OAuth tokens are refreshed before they expire, so nobody re-enters them.
- Keys never pass through an agent. The CLI reads them at a hidden prompt and refuses to run without a terminal.
Access
- Sign-in is a one-time code sent by email. There are no passwords.
- New members can read everything they’re given and change nothing.
- Each change (refunds, bans, rollbacks, write SQL, file deletes and the rest) is off until an owner allows it for that person.
- Owners are held to their own levels too, and can always change them.
- Members only open the projects an owner gives them.
- Every change asks for confirmation before it runs.
Assistant, tokens and CLI
- All three act as a member and can never do more than that member can.
- The assistant asks in the chat before any change.
- Access tokens are stored only as a SHA-256 hash. They can be limited to some tools and projects, and stop working when their member leaves.
Your providers
- Postgres queries run in read-only transactions. Write SQL and cell edits are separate permissions, both off by default.
- Baseboard never merges, reverts or re-runs CI. GitHub needs a fine-grained token for a single repository; classic tokens are refused.
- Convex’s one-click connect makes a deploy key that can only read.
- File download links expire after five minutes.
- Matching apps to databases returns the names of your hosts’ settings, never their values.
Audit log
- Every read and every change is logged with who made it (member, assistant or token), the tool, the connection and the time.
- Logs are kept for: Free 7 days, Pro 365 days, Team with no limit.