RealComposer
Client PlatformsOfficial Bubble docs

Bubble Safe & Unsafe Practices

Direct Answer

Bubble API Connector fields marked Private are kept on Bubble servers, but unmarked values can reach the browser. Set privacy rules on every data type, require authentication on backend workflow endpoints, and proxy calls that need complex secret handling.

Credentials & Where They Belong

Server only
API Connector private fields

Kept server-side when the Private box is checked.

Server only
Bubble Data API token

Admin-level access to your app data.

Safe Practices

  • Mark every key Private in API Connector

    Unchecked shared headers and parameters can be sent from the browser.

  • Write privacy rules for each data type

    Without rules, Bubble data can be searched by any user.

Unsafe Practices

  • Exposing backend workflows without authentication

    Public workflow endpoints can be triggered by anyone who finds the URL.

  • Leaving data types without privacy rules

    Users can query records that belong to others.

The RealComposer Pattern

Call RealComposer from the API Connector with the client token marked Private, and let the pipeline handle multi-API aggregation and slimming.

START BUILDING FREE

Frequently Asked Questions

Q:Are Bubble API Connector keys secure?

When marked Private, yes. Unmarked fields may be visible to clients.

Platforms & Frameworks

Bubble Io API Connector Response Too Slow How to Speed Up

To solve bubble io api connector response too slow how to speed up, never execute unauthenticated requests or embed private tokens directly in client bundles. RealComposer acts as a sub-10ms edge gateway running on Cloudflare Workers that securely injects credentials from your Secret Vault, normalizes responses, and prevents unauthorized API usage. Route calls through your RealComposer edge URL to guarantee complete privacy, robust origin validation, and low mobile latency.

Sub-10ms edgeView Recipe

Related Concepts