// Security by tool
Security for Bubble.io apps
Quick answer
The dominant hole in a Bubble app is not a Bubble bug: it is the default configuration. Privacy rules start EMPTY and the Data API often ships enabled, so, with no rule defined, every data type is accessible to any API request, with no login. API workflows also do not require authentication by default. The visitor does not even need your screen: they talk straight to the data API.
Bubble hides the database behind the interface, which gives a false sense that "you cannot access the data directly". You can, and it is the first place an attacker tests in a no-code app. The protection is defining a privacy rule per data type (deny by default, grant the minimum) and requiring auth on sensitive workflows.
What usually stays open in Bubble
The "open by default" pattern repeats across several points in Bubble. Each must be actively closed, one by one.
| Hole | Why it happens | Impact |
|---|---|---|
| Empty privacy rules | Born with no rule, everything open | Data accessible via Data API with no login |
| Data API enabled without restriction | Exposure per data type is on | Record enumeration via API |
| API workflow with no auth | Does not require auth by default | Anyone triggers the workflow |
| Sensitive data in a visible field | Field exposed in the returned object | PII leak in the API response |
How RET reviews a Bubble app
RET tests what the Data API returns for a request with no login, data type by data type, and confirms whether each privacy rule denies by default and grants only what is needed. It checks which API workflows trigger without auth and whether any sensitive field is riding in the response. Each finding ships with reproduction steps via the API itself.
For the first pass, the Promptbook guides checking privacy rules and the Data API. When there is customer data or a B2B sale, Risk Review reads the flows and says what to close first.
- Test what the Data API returns without authentication.
- Privacy rule per data type: deny by default, grant the minimum.
- Sensitive API workflows requiring auth; sensitive fields out of the response.
You may already be exposed if
Signals that call for a review of a Bubble app.
- You never configured privacy rules per data type.
- The Data API is on and you do not know what it returns without login.
- You have an API workflow that changes data and did not check "requires authentication".
- You store customer data and trust that "hiding the screen" protects the database.
Want to know whether this happens in your system?
Manual pentest for web applications, APIs and apps, from R$9,500, with the Sprint run within 7 business days. We refund 50% if we find no flaw.
Frequently asked questions
Is Bubble insecure?
Bubble has security features, but many are not on by default: privacy rules start empty and the Data API often ships enabled. The app is exposed by default configuration, not by a bug. Closing it means configuring a privacy rule per data type and requiring auth on workflows.
Does hiding the interface protect my data in Bubble?
No. The Data API talks straight to the database, without going through your screen. An attacker queries the API and ignores the interface. The real protection is the privacy rule, not the absence of a button on the screen.
How do I know what is exposed?
By testing the Data API with no login and seeing what comes back, per data type. It is the first test RET runs on a Bubble app, and the Promptbook guides you to do it yourself.
Who runs the review at RET?
Gabriel Lima Ferreira, founder and lead pentester, with an authorized scope and reproducible evidence via the API itself.