Skip to main content

Privacy Policy

Last updated: 3 October 2026

This policy covers the hosted Broods service operated by BeeBlast B.V., Amsterdam, the Netherlands (KvK 98814737), which is the controller of the data described here. Reach us at business@beeblast.co. It is written to be read, not skimmed: every section says what we store and why.

What we store​

DataWhyWhere it comes from
Your name, email and sign-in identityTo run your account and contact youWorkOS, when you sign in
Organization members and rolesAccess controlYou
Agent configuration, environment variables, channel tokens, provider API keysTo run your agentsYou. Secrets are encrypted with AES-256-GCM before they are stored
Conversations, messages and attachments your agents processSo agents keep context and you can inspect runsYour users, through the API and connected channels
Workspace files, skills, hook and MCP bundlesYour agents' code and filesYou
Traces, logs and usage recordsDebugging, allowances and billingGenerated as agents run
Plan and payment statusBillingStripe. We never see your card number

We do not sell data and we do not use your conversations to train models.

Where it lives​

  • Configuration, conversations and usage records live in our database on servers hosted by Hetzner in the European Union.
  • Files, bundles and attachments live in private AWS S3 buckets in eu-west-1 (Ireland). Hosted MCP servers and MicroVM sandboxes run on AWS Lambda in the same region.
  • Traces and logs stay on our own observability stack. They carry your tenant id so only your organization can read them.

Who else touches it​

ServiceRoleWhat they get
WorkOSSign-in and organizationsEmail, name, sign-in identity
StripePaymentsEmail and billing details you enter on Stripe's pages
AWSFile storage, hosted MCP, MicroVM sandboxesFiles, bundles and whatever your code sends
HetznerHosting for the core, gateway and databaseEverything in the first table, encrypted at rest
Your model providersAnswering your agentsThe conversation context, sent with your own API key under your contract with them
Channels you connectDelivering messagesThe messages your agents send and receive on that channel
Sandbox providers you choose (E2B, Daytona, Vercel)Running commands outside AWSThe workspace files and environment variables you declare for that sandbox

Model providers, channels and third-party sandboxes only receive data when you connect them.

How long we keep it​

  • Everything stays until you delete it. Deleting a project removes everything under it on every stage. Deleting an organization removes all of its data. Neither can be undone.
  • Nightly database backups are kept for 30 days and then expire. Deleted data can still be in a backup until then.
  • Usage records needed for invoices are kept for as long as tax law requires.

Your rights​

You can see and change your data in the dashboard, export it through the API, and delete it yourself. For anything the dashboard does not cover, including a full export or a correction, email business@beeblast.co or use the Support page and we answer within 30 days. If you are in the EU or UK you can also complain to your data protection authority.

Security​

Secrets are encrypted at rest, API responses never return them, and uploaded code runs outside the core with the least access we can give it. The security guide has the details. Report a vulnerability through GitHub private vulnerability reporting.

Cookies​

The dashboard sets only the cookies it needs to keep you signed in. There is no advertising or cross-site tracking.

Changes​

We post changes here and email organization owners about material ones at least 14 days in advance.