Privacy policy

Who we are

BuildBot is a product of Pando Solutions LLC, a New Jersey limited liability company doing business as Pando ("Pando", "we", "us"). Pando is the data controller for the personal data described here. BuildBot does not have its own legal entity.

This policy covers the marketing site at buildbot.me, the application at app.buildbot.me, and the BuildBot API.

What we collect

Account information

Your email address and password (stored only as a cryptographic hash), the name you give us, and optionally an organization name. If you join a workspace, we store your membership and role. If you invite someone, we store the email address you invited.

What you create

Everything you build in BuildBot is stored on our servers: agents, rules, skills, commands, hooks, MCP server definitions, projects, and workspaces. These are free-text fields, so they contain whatever you put in them — please don't paste API keys, credentials, or other people's personal data into them.

Conversations with the assistant

When you use the BuildBot assistant we store the full conversation: your messages, the model's replies and reasoning output, any tool calls it made, the model used, and token counts. This is what lets you reopen a session later and what we use to meter usage.

Files you upload

Documents you attach are stored in our file storage, along with their filename, type, and size. We also extract and store the text content so the assistant can read it.

Deployments and runs

If you deploy an agent to our managed cloud, we store a snapshot of the exact configuration deployed, the identifiers our AI provider assigns to it, each run session's status, and the tokens it consumed.

Billing information

Payments are handled entirely by Stripe. We never see or store your card number. We keep your Stripe customer and subscription identifiers, your plan, your credit balance, and a ledger of credit purchases and usage.

API keys

If you create an API key we store a SHA-256 hash of it and a short non-secret prefix so you can tell your keys apart, plus its scopes and when it was last used. We cannot recover the key itself — that's the point.

Technical data

Our hosting provider processes your IP address and an approximate country for every request, which we use to serve the site, apply rate limits, and decide whether to show a cookie banner.

Guest sessions

You can use BuildBot without signing up. To make that work, we create an anonymous account on our servers and a session cookie in your browser. We want to be clear about this, because it is easy to assume otherwise: guest work is stored in our database, not only in your browser. It is just not attached to an email address.

An anonymous account holds no identifying information beyond what you type into it. If you later sign up, we move that work onto your new account and delete the anonymous one. If you never sign up, we may delete inactive anonymous accounts and their contents.

How we use it

• To operate the product — saving your work, running the assistant, deploying and running agents.
• To authenticate you and keep accounts and workspaces separated.
• To meter usage and bill you correctly.
• To send transactional email: confirmations, password resets, workspace invitations, and billing notices.
• To keep the service secure and available — rate limiting, abuse prevention, and debugging failures.
• To understand aggregate traffic patterns on the marketing site.
• To comply with legal obligations.

We do not sell your personal data. We do not use your agent configurations, conversations, or uploaded documents to train AI models, and we do not permit our AI provider to do so either.

If you are in the EEA or UK, our legal bases are: performance of a contract for operating the product and billing you; legitimate interests for security, abuse prevention, and aggregate analytics where consent is not required; consent for cookie-based analytics; and legal obligation where the law requires retention.

AI processing

BuildBot is built on Anthropic's Claude. Two things send your data there, and you should know about both.

The assistant. When you chat with BuildBot, we send your messages, the agent configuration you are working on, and the extracted text of any documents you have attached to the Anthropic API. The response comes back to us and is stored in your session history.

Deployed agents. When you deploy an agent to our managed cloud, the agent's configuration is provisioned into Anthropic's managed agent infrastructure and each run executes there. The inputs you give a running agent, and everything it produces, pass through Anthropic.

We use Anthropic's commercial API, under which submitted data is not used to train their models. Anthropic may retain inputs and outputs for a limited period for trust-and-safety purposes. Your use of deployed agents is also subject to Anthropic's usage policies — see our Terms of Service.

Treat anything you send to the assistant or to a deployed agent as leaving our infrastructure. Don't send secrets, regulated data, or anyone else's personal data through it.

Sub-processors

These are the third parties that process personal data on our behalf. We update this list when it changes.

Supabase United States

Purpose — Authentication, database, file storage, and account emails

Data — Account identity, all workspace content, uploaded files

Vercel United States / global edge

Purpose — Hosting and content delivery for buildbot.me and app.buildbot.me

Data — Request metadata, IP address, approximate country

Anthropic United States

Purpose — Powers the BuildBot assistant and runs deployed agents

Data — Prompts, agent configurations, extracted document text, run output

Stripe United States

Purpose — Payment processing for subscriptions and credit packs

Data — Payment method, billing details, transaction records

Google Analytics 4 United States

Purpose — Marketing-site traffic measurement (consent-gated in the EEA/UK)

Data — Cookie identifier, page views, device and approximate location

Plausible Analytics European Union

Purpose — Cookieless aggregate traffic measurement

Data — Page views and referrers, no cookies or cross-site identifiers

Business customers who need a Data Processing Agreement can request one at privacy@buildbot.me.

Cookies and analytics

Strictly necessary cookies. The application sets session cookies to keep you signed in. These cannot be turned off — without them the product does not work. We also set a short-lived cookie recording whether your request came from the EEA or UK, so we know whether to show a consent banner.

Google Analytics 4. The marketing site uses GA4, which sets cookies and shares measurement data with Google. In the EEA and UK it is off by default and only runs if you accept it in the cookie banner; you can change your choice at any time from that banner. Outside the EEA and UK it runs by default — see the section below for how to opt out.

Plausible. We also use Plausible, which sets no cookies, collects no cross-site identifiers, and produces only aggregate counts.

Sharing and public links

We share your data with the sub-processors above, with other members of any workspace you join, and where we are legally required to. We may also transfer your data as part of a merger, acquisition, or sale of assets — you will be notified before that happens.

Share links deserve their own warning. When you create a share link for an agent or project, anyone with that link can view and fork it. Depending on the options you choose, it may be accessible without a password and without signing in. Content behind a share link is no longer private — only share what you are comfortable making public. You can revoke a share link at any time, though we cannot recall copies someone already made.

How long we keep it

• Account and workspace content — for as long as your account is open.
• Conversations, uploaded documents, and deployment snapshots — for as long as your account is open, or until you delete them.
• Anonymous guest accounts — deleted when converted to a real account, and periodically purged when inactive.
• Billing and credit ledger records — retained for at least seven years, because tax and accounting law requires it.
• Backups — deleted data can persist in encrypted backups for up to 30 days after removal from the live database.

When you ask us to delete your account, we remove your content within 30 days, except for the billing records noted above.

Your rights

You can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or port it elsewhere. You can also withdraw consent for analytics cookies at any time without affecting anything else.

To delete your account and its contents, email privacy@buildbot.me from the address on the account. We will confirm and complete the deletion within 30 days. Self-service deletion from account settings is on our roadmap; until it ships, email is the route, and we would rather say that than imply a button exists.

We respond to rights requests within 30 days and do not charge for them. If you are in the EEA or UK and are unhappy with our response, you may complain to your local data protection authority.

US state privacy rights

If you live in California, Colorado, Connecticut, Virginia, or another state with a comprehensive privacy law, you have the rights described above, plus the right not to be discriminated against for exercising them. Use the same email address to make a request.

We do not sell personal information for money. However, running Google Analytics may constitute "sharing" for cross-context behavioral advertising under California law. To opt out: use the cookie banner if you are shown one, install the Google Analytics opt-out add-on, enable Global Privacy Control in your browser, or email us. We honor Global Privacy Control signals where our consent tooling receives them.

Security

Data is encrypted in transit and at rest. Access between accounts and workspaces is enforced at the database level by row-level security, not only in application code. Passwords are hashed by our authentication provider and API keys are stored only as hashes. Access to production systems is limited to people who need it.

No system is perfectly secure. If you believe you have found a vulnerability, please report it to security@buildbot.me rather than disclosing it publicly, and we will work with you on it.

International transfers

We are based in the United States and most of our sub-processors operate there. If you use BuildBot from the EEA, UK, or Switzerland, your data is transferred to the United States. Those transfers rely on the European Commission's Standard Contractual Clauses (and the UK Addendum where applicable) in our agreements with each sub-processor.

Children

BuildBot is not intended for anyone under 16, and we do not knowingly collect personal data from children. If you believe a child has given us personal data, email us and we will delete it.

Changes

We will update this policy as the product changes. The date at the top always reflects the current version. For material changes — a new category of data, a new sub-processor, a new purpose — we will email registered users at least 14 days before the change takes effect.

Contact

Pando Solutions LLC (d/b/a Pando)
New Jersey, United States
Privacy: privacy@buildbot.me
Security: security@buildbot.me

See also our Terms of Service.