Security
BusyBot holds credentials to your other systems. That is a serious responsibility, and this page describes what actually happens to them — not aspirations.
Credentials
- Encrypted at rest with AES-256-GCM. Secret fields are encrypted before they reach the database; the plaintext never lands in durable storage.
- Readable only by you. A saved secret is sent only to the account that owns it — to fill that credential's edit form — and never to another account. Model-provider API keys you bring (Settings → Keys) are write-only: after saving, only their last four characters are ever shown.
- Never logged. The event log scrubs secret-shaped keys as a backstop, and emitters are held to keeping values out in the first place. Audit records store changed field names, never values.
- Ownership-checked on every use. A credential is resolved against the user who owns it; a workflow cannot reference another account's credential.
Isolation
- BusyBot runs on its own Kubernetes cluster on DigitalOcean, in the United States.
- Every workspace's data is scoped per user, including cache keys.
- Pro plans run in a dedicated pod that wakes on demand and scales to zero; Enterprise runs on a contracted pool with its own URL.
- User-supplied code executes sandboxed — V8 isolates for lightweight JavaScript, container-level sandboxing for untrusted code.
Transport
- TLS on every public endpoint, with certificates issued and renewed automatically.
- The application and the API are separate origins with an explicit CORS allowlist.
Model providers
Prompts and completions are sent to the model provider you select (OpenAI, Anthropic, Google or xAI). On plans that support bring-your-own-key, calls run against your own provider account instead of ours.
Reporting a vulnerability
If you believe you have found a security issue, email ben@busybot.net before disclosing it publicly. We will confirm receipt and keep you updated on the fix.
Certifications
We do not currently hold SOC 2, ISO 27001 or HIPAA attestations. This page describes what the system does, not a certification.
Last updated 2026-10-22.