Bubble Subprocessors List (November 2026): Changes and History
Bubble names 61 subprocessors on its published list. Read from the vendor's own page and re-checked daily.
Named rows include _tt_enable_cookie, CookieScriptConsent, and meta_u1main. We keep Bubble's DPA on file, along with its privacy policy and trust page.
Bubble subprocessors (November 2026)
| # | Subprocessor | Purpose | Location |
|---|---|---|---|
| 1 | _tt_enable_cookie | This cookie is used to remember the user's preferences regarding the use of cookies on the website. | — |
| 2 | CookieScriptConsent | This cookie is used by Cookie-Script.com service to remember visitor cookie consent preferences. It is necessary for Cookie-Script.com cookie banner to work properly. | — |
| 3 | meta_u1main | — | — |
| 4 | meta_live_u2main | — | — |
| 5 | meta_live_u2main.sig | — | — |
| 6 | __cf_bm | This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. | — |
| 7 | __session | This cookie is used to maintain an anonymized user session by the server. | — |
| 8 | li_gc | Used to store guest consent to the use of cookies for non-essential purposes | — |
| 9 | cf_clearance | This cookie is used by the CloudFlare service to identify trusted web traffic and override any security restrictions based on the visitor's IP address. It is essential for supporting a website's security features and in providing protection against malicious visitors. | — |
| 10 | VISITOR_PRIVACY_METADATA | This cookie is used to store the user's consent and privacy choices for their interaction with the site. It records data on the visitor's consent regarding various privacy policies and settings, ensuring that their preferences are honored in future sessions. | — |
| 11 | AWSALBCORS | For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSALBCORS (ALB). | — |
| 12 | __cflb | This cookie is used for load balancing and for identifying trusted web traffic. It helps in ensuring consistent service and user experience by managing traffic and routing users to specific servers. | — |
| 13 | _ga | This cookie name is associated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners. | — |
| 14 | _ga_5Q4JP8E2X4 | This cookie is used by Google Analytics to persist session state. | — |
| 15 | _ga_BFPVR2DEE2 | This cookie is used by Google Analytics to persist session state. | — |
| 16 | _ga_CEPZJCHM3K | This cookie is used by Google Analytics to persist session state. | — |
| 17 | _ga_CMMEJQJJ8J | This cookie is used by Google Analytics to persist session state. | — |
| 18 | _ga_Y168TZXEQ5 | This cookie is used by Google Analytics to persist session state. | — |
| 19 | _ttp | This cookie is used to track user interaction and behavior on the website for site performance and usage analysis. This information is used to improve the user experience and optimize the website's functionality. | — |
| 20 | ajs_anonymous_id | These cookies are generally used for Analytics and help count how many people visit a certain site by tracking if you have visited before. This cookie has a lifespan of 1 year. | — |
| 21 | analytics_session_id | This cookie tracks user behavior throughout the session on the website, collecting data such as how long a visitor stays on a page and what links they click on. This information is used to improve user experience and website performance. | — |
| 22 | analytics_session_id.last_access | This cookie is used to store the time of the last access by a user in an analytics session, helping in understanding user engagement and the effectiveness of the website content. | — |
| 23 | m | This cookie is generally used for performance and optimization of payment processing services, facilitating caching of content on the browser to make pages load faster. | — |
| 24 | GAESA | This cookie is typically associated with the collection and analysis of statistical data to improve site performance. It may track details such as the number of visitors, the source of the visit, and the pages visited in an anonymous form. | — |
| 25 | MUID | This cookie is widely used my Microsoft as a unique user identifier. It can be set by embedded microsoft scripts. Widely believed to sync across many different Microsoft domains, allowing user tracking. | — |
| 26 | _gcl_au | Used by Google AdSense for experimenting with advertisement efficiency across websites using their services | — |
| 27 | _uetsid | This cookie is used by Bing to determine what ads should be shown that may be relevant to the end user perusing the site. | — |
| 28 | _uetvid | This is a cookie utilised by Microsoft Bing Ads and is a tracking cookie. It allows us to engage with a user that has previously visited our website. | — |
| 29 | _fbp | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers | — |
| 30 | bcookie | This is a Microsoft MSN 1st party cookie for sharing the content of the website via social media. | — |
| 31 | lidc | This is a Microsoft MSN 1st party cookie that ensures the proper functioning of this website. | — |
| 32 | guest_id | This cookie is set by Twitter to identify and track the website visitor. | — |
| 33 | guest_id_ads | This cookie is associated with Twitter's advertising services. It is used to identify and track the website visitor to display personalized ads based on the user's preferences and interaction with the website. | — |
| 34 | guest_id_marketing | This cookie is used to identify a visitor across visits and devices. It allows the website to present the visitor with relevant advertisement based on the visitor's preferences. | — |
| 35 | personalization_id | This cookie carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website. | — |
| 36 | VISITOR_INFO1_LIVE | This cookie is set by Youtube to keep track of user preferences for Youtube videos embedded in sites;it can also determine whether the website visitor is using the new or old version of the Youtube interface. | — |
| 37 | YSC | This cookie is set by YouTube to track views of embedded videos. | — |
| 38 | __stripe_mid | This cookie is set by Stripe to distinguish users and enable secure payment processing during interactions with the website. | — |
| 39 | __stripe_sid | This cookie is set by Stripe to manage and process payments securely, allowing temporary storage of session related information during a users visit to the website. | — |
| 40 | _cfuvid | This cookie is used for purposes of tracking users across sessions to optimize user experience by maintaining session consistency and providing personalized services. | — |
| 41 | ttcsid | — | — |
| 42 | ttcsid_CRGSJIJC77UAMBH9S77G | — | — |
| 43 | ttcsid_D6UMEIRC77U8BUJPT1G0 | — | — |
| 44 | EXP_4ddc8ad920_identity | — | — |
| 45 | __birdie_snippet_status | — | — |
| 46 | _twpid | — | — |
| 47 | _twsid | — | — |
| 48 | bubble-certifications_u1main | — | — |
| 49 | bubble-certifications_live_u2main | — | — |
| 50 | bubble-certifications_live_u2main.sig | — | — |
| 51 | CrossDomainCookieScriptConsent_239 | — | — |
| 52 | flusk_u1main | — | — |
| 53 | flusk_live_u2main | — | — |
| 54 | flusk_live_u2main.sig | — | — |
| 55 | muc_ads | — | — |
| 56 | __Secure-ROLLOUT_TOKEN | — | — |
| 57 | __Secure-YNID | — | — |
| 58 | editor_visits_count | — | — |
| 59 | _vb | — | — |
| 60 | birdie_session_sqs7i0ne | — | — |
| 61 | __cf_ob | — | — |
Get an email when Bubble changes its subprocessors
ClauseTrail re-checks this list every day and tells you exactly who was added or removed — including when a vendor starts sending data to an AI provider. The first vendors are free.
Key DPA terms at Bubble
What Bubble's data processing agreement commits to, with the sentence each answer comes from. SCCs or the Data Privacy Framework: what's the difference?
- Breach notification
-
Without undue delay, with no set deadline
“Bubble shall notify Customer of a Personal Data Breach without undue delay after becoming aware of the occurrence thereof.”
DPA, bubble.io ↗ - Notice of a new subprocessor
-
30 days ahead
“Bubble will notify Customer of the engagement (including the name and location of the relevant Subprocessor and the activities it will perform) by updating the Subprocessor Site or by other written means at least thirty (30) days before such Subprocessor Processes Customer Personal Data.”
DPA, bubble.io ↗ - Transfers outside the EU
-
Standard contractual clauses and the EU–US Data Privacy Framework
“"SCCs" means the standard contractual clauses approved by the European Commission pursuant to implementing Decision (EU) 2021/914.”
“Where Bubble is certified under a scheme (such as the EU–U.S. Data Privacy Framework, UK Extension and/or Swiss–U.S. Data Privacy Framework (as applicable)) that benefits from an adequacy decision of the EU Commission, UK Government and/or Swiss authorities (as applicable), Bubble will rely on such scheme and corresponding adequacy decision for transfers of Customer Personal Data.”
DPA, bubble.io ↗ - Customer data after the contract ends
-
Deleted or returned when the contract ends
“Upon expiration or earlier termination of the Agreement, Bubble shall return and/or delete all Customer Personal Data in Bubble's care, custody or control in accordance Customer's instructions as to the post-termination return and deletion of Customer Personal Data expressed in the Agreement, or subject to Section 13.5, Customer's further instructions.”
DPA, bubble.io ↗ - Audit rights
-
Once a year
“Bubble need not cooperate with any audit (a) performed by any individual or entity who has not entered into a non-disclosure agreement with Bubble on terms acceptable to Bubble in respect of information obtained in relation to the audit; (b) outside normal business hours; or (c) on more than one (1) occasion in any calendar year during the term of the Agreement, except for any additional audits that Customer is required to perform under Data Protection Laws.”
DPA, bubble.io ↗
Certifications at Bubble
What Bubble's trust page lists, with the text each one comes from. SOC 2 Type I or Type II: what's the difference?
- SOC 2 Type II
-
Active
“Bubble complies with the SOC 2 Type II standard for security”
Trust page, bubble.io ↗
Documents we track for Bubble
- DPA
- checked November 17, 2026 changed November 13, 2026 bubble.io ↗
- Privacy policy
- checked November 17, 2026 changed November 13, 2026 bubble.io ↗
- Subprocessor list
- checked November 17, 2026 changed November 15, 2026 bubble.io ↗
- Trust page
- checked November 16, 2026 bubble.io ↗
Change history
Tracking since September 28, 2026. No change has been published since; additions, removals and document changes will appear here as they're published.
Bubble subprocessors FAQ
- How many subprocessors does Bubble use?
- Bubble lists 61 subprocessors on its published list, including _tt_enable_cookie, CookieScriptConsent, meta_u1main, meta_live_u2main, and meta_live_u2main.sig and 56 more.
- How quickly does Bubble report a personal data breach to customers?
- According to its DPA, Bubble reports a personal data breach to customers without undue delay, with no set deadline: “Bubble shall notify Customer of a Personal Data Breach without undue delay after becoming aware of the occurrence thereof.”
- How much notice does Bubble give before adding a subprocessor?
- Bubble's DPA gives 30 days' notice of a new subprocessor, the time customers have to object: “Bubble will notify Customer of the engagement (including the name and location of the relevant Subprocessor and the activities it will perform) by updating the Subprocessor Site or by other written means at least thirty (30) days before such Subprocessor Processes Customer Personal Data.”
- How does Bubble transfer personal data outside the EU?
- Bubble's DPA relies on standard contractual clauses and the EU–US Data Privacy Framework: “"SCCs" means the standard contractual clauses approved by the European Commission pursuant to implementing Decision (EU) 2021/914.”
- Does Bubble have a SOC 2 Type II report?
- Yes. Bubble's trust page lists a SOC 2 Type II report: “Bubble complies with the SOC 2 Type II standard for security”
- Which security certifications does Bubble list?
- Bubble's trust page lists SOC 2 Type II.
- When was Bubble's subprocessor list last checked?
- ClauseTrail last checked Bubble's subprocessor list on November 17, 2026 and last saw it change on November 15, 2026. Lists are re-checked daily.
- How do I find out when Bubble adds or removes a subprocessor?
- ClauseTrail monitors Bubble's subprocessor list, DPA, privacy policy and terms and emails you the exact change — who was added or removed and what the page said before and after. The first vendors are free.