Overview
Bubble is a no-code web application platform that enables users to build and deploy full-featured web applications without writing code. Applications built on Bubble are hosted on Bubble's infrastructure and served from bubbleapps.io or custom domains. Bubble's runtime JavaScript handles all application logic — form submissions, database reads/writes, user authentication, and interactive UI behavior — within the visitor's browser. This makes Bubble the underlying infrastructure of entire web applications rather than a single embedded widget.
What This Script Does
On pages built with Bubble, the Bubble runtime script handles:
- Application rendering: Delivers the complete application UI, rendering all visual elements, layouts, and dynamic content from the Bubble database
- User authentication: Manages login sessions using session cookies tied to Bubble's authentication system; authenticated users have session tokens stored in cookies or localStorage
- Data operations: Makes API calls to Bubble's backend for all data reads and writes, transmitting user-entered data to the Bubble database on the application's behalf
- Form processing: Captures form submissions and applies configured workflows (creating database records, sending emails, triggering external API calls)
- Workflow execution: Runs configured conditional logic, event triggers, and backend workflows in response to user interactions
As the application's infrastructure, Bubble processes all personal data that users enter into the application — the data model and privacy practices are entirely determined by the application developer.
Consent & Compliance
- Consent Category: Essential and Functional
- GDPR/ePrivacy: Bubble's runtime scripts are the application itself — blocking them renders the application non-functional. Authentication session cookies are strictly necessary. Privacy obligations for a Bubble-built application fall on the application developer: they are the data controller for any personal data collected through the application, and Bubble is the data processor. Ensure a DPA is in place with Bubble.
- CCPA: Personal data collected through Bubble applications is the application developer's responsibility to manage under CCPA.
Should You Block This Without Consent?
No. Bubble's runtime is the application infrastructure. Blocking it would make the application non-functional. Application developers building on Bubble are responsible for privacy compliance of their applications, including implementing appropriate consent mechanisms for any non-essential tracking or analytics tools added to their Bubble applications.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
bubble.ioEssentialFrequently Asked Questions
Is cookie consent needed for Bubble applications?
Generally not for core functionality. Bubble is classified as essential and functional since its scripts render the web application itself, handling UI logic, authentication, and database operations. However, if your Bubble app integrates third-party tracking tools, those specific integrations may still require consent under GDPR.
What cookies and data does Bubble use in the browser?
Bubble's runtime JavaScript manages the entire application experience including form submissions, database reads and writes, user authentication, and interactive UI behavior. It sets session cookies necessary for maintaining user login state and application functionality on bubbleapps.io or custom domains.
How does ConsentStack manage Bubble scripts?
ConsentStack identifies Bubble as the core application framework and categorizes it as essential and functional. Because Bubble powers the website's primary functionality, ConsentStack does not block it when visitors decline optional cookies. Any third-party tools loaded within the Bubble app are evaluated separately.
Related Vendors
Manage consent for Bubble
ConsentStack automatically detects and manages Bubble trackers so your site stays compliant with global privacy regulations.