Built to be trusted.

Every project, agent, file, and event is owned by your account. Row-level security is enabled on every table, and every server query is additionally scoped to the signed-in user — so no other customer can ever see your work, by policy and by code.

Privileged database keys live only in server-side environment variables and are used exclusively inside our API routes. The browser only ever holds a scoped, public key. Sensitive operations always validate your session before responding.

When you ship a project to GitHub, the token you provide is used for that single push and then discarded — we never persist it. We store only the resulting public repository URL. The same principle applies across the product: we hold the minimum, for the shortest time.

Payments run through Stripe’s hosted checkout — card details go straight to Stripe and never reach our servers. Subscription changes arrive as cryptographically signature-verified webhooks; a request without a valid signature is rejected outright.

The constitution the swarm obeys bakes in the same standards on your generated apps: row-level security on every table, secrets read only from the environment, service keys kept server-side, and input validated on every route. Security is the default output, not an afterthought.

Export any project as a zip or push it straight to your own GitHub. There is no runtime lock-in and no license strings attached. Delete a project or your account at any time and its data is removed.

We collect product analytics — what kinds of apps are built, which templates and features get used, how far projects travel down the pipeline — so we can make BuildSwarm better. This never includes your card details, and access tokens are still used once and never stored. Aggregate usage is visible only to our operators, never to other customers.

Responsible disclosure

Found something? Email security@shiftpro.ai and we will respond quickly. We appreciate every report and will credit you if you would like.