Security & privacy

This page says what BuddyBots does with your data and what protects it, in plain words. It applies to the hosted service; the self-hosted build keeps everything on your own machine.

Where your data lives

• Each organisation has its own rows in the database and its own folder for files, skills, uploads and screenshots. Every query is scoped to the organisation of the signed-in session; an id from another organisation answers "not found".
• API keys and connector credentials are stored in the vault, per organisation, and never returned by the API (only a masked form). Platform keys in the server environment act as shared keys and are shown as "provided by BuddyBots".
• Browser profiles (cookies, logins a bot picks up) are per organisation and per bot when "Isolated browser profile per bot" is on.
• Sessions are HttpOnly, SameSite=Lax cookies, marked Secure over HTTPS, valid 30 days. Changing your password ends every other session.

What bots can and cannot do

• Bots only act while a task is running, and only inside their organisation's workspace folder and connected apps.
• Sending, publishing, paying, deleting and every write to a connected app go through an approval gate. You decide once, always, or deny; "always" creates a rule you can see and remove.
• Bots never type passwords, one-time codes or CAPTCHA answers; they pause and ask you to take over in the mirrored browser.
• Shell commands run in a per-organisation sandbox (bubblewrap): a fresh mount namespace where the system is read-only, only that organisation's workspace is writable (as /workspace), no other organisation's folder exists, the environment carries no server secrets, and CPU, memory, file size and process count are capped. /api/status reports sandbox: bwrap when this is active.

Payments

Card details never touch BuddyBots: Stripe Checkout and the Stripe customer portal handle cards, invoices and cancellation. BuddyBots stores the Stripe customer id, subscription id, plan and period.

Email

Welcome, invite, "needs your OK", "task finished" and billing emails go through Resend. No marketing email without opt-in.

Your rights

• Export: Settings → Data gives a JSON export of your organisation (bots, memory, conversations, tasks, connectors without secrets, usage) and a zip of the workspace files.
• Delete: Settings → Data → Delete organisation removes every row and file; Stripe subscriptions are cancelled; the deletion is final after a 7-day grace period during which sign-in is blocked.
• Audit: Activity → Export gives every approval decision; the audit log (Settings → Audit) lists sign-ins, invites, plan changes, key changes and deletions.

Reporting a vulnerability

Email security@buddybots.app. We answer within 2 business days and do not pursue researchers who act in good faith.

Sub-processors

Anthropic, OpenAI, OpenRouter, Google, xAI, DeepSeek (model calls you choose), Composio (app catalogue and OAuth), Stripe (payments), Resend (email), the hosting provider of the region you pick.