Permissions and data safety
Buildprint is designed to give you full control over what agents can and cannot do with your Bubble app. This guide explains how permissions work and what is protected.
Responsible agent use
Buildprint is an AI powered tool. As with all AI powered tools, outputs are non-deterministic. You are ultimately responsible for the agents that you supervise. You can and should monitor and stop in progress conversations at any time if an agent deviates from the action you are looking for. Buildprint is not liable for any unexpected actions of your agents.
Plan mode vs Build mode
By default, agents operate in Plan mode. In Plan mode, agents can view your app's structure, workflows, database schema, and logs, but cannot make any changes.
When you switch to Build in the chat composer, agents can modify your app — creating workflows, updating fields, changing settings, and more. Edits are applied to whichever versions you’ve selected in the version picker.
Even with Build mode enabled, all database interactions remain read-only. Agents can query your database to answer questions, but cannot create, modify, or delete Things.
Bubble collaborator permissions
Buildprint accesses your app through a Bubble collaborator account. The permissions on that collaborator account act as a hard boundary — agents can never exceed them.
You can use Bubble’s collaborator permissions to restrict what Buildprint can access. For example, you might limit database access to the test version only, or restrict access to certain pages.
Tightening collaborator permissions will limit what Buildprint agents can do. If the collaborator has restricted access, agents may not be able to read or modify parts of your app that fall outside those permissions, even when you allow it in Buildprint.
What agents cannot do
Regardless of permissions, there are things agents are never able to do:
Edit database Things - All database interactions are strictly read-only. Agents can view your schema and query data, but cannot create, update, or delete any records.
Merge branches or deploy to live - Agents cannot merge Bubble branches or push changes to your live app. Deployment always stays in your control.
Access private API keys or plugin secrets - Private values in your API Connector and plugin secrets are inaccessible to Buildprint. These values are never read or stored.
Data safety
Buildprint does not store your API Connector private keys, plugin secrets, or other sensitive credentials. These values are filtered out and never saved to Buildprint’s systems.
Your Bubble database data is fetched on-demand when agents need it to answer a question — it is not permanently stored or cached. You control which projects and versions agents can access when generating MCP tokens or working in conversations.
Buildprint does not train AI models on your apps or responses, and does not use model providers that train their models using your inputs/outputs.
Data hosting
We do not make any formal guarantees around data hosting location. Currently, streamed logs are hosted in the US when advanced logging is enabled. Your Bubble app logic may pass through the US or the EU.