Cookie policy

Latest updated at: 17 July 2023

Introduction

BubblyDoo and third parties use cookies on our website. We use cookies for essential, functional, analytical and marketing purposes and to improve your experience of our website.

Cookies are small text files that are saved on your computer by our website. These text files sometimes contain information that can uniquely identify your browser or device.

We use pixels, tags and cookies on our website.

We do not run advertisements on our website and do therefore not use the IAB TCF framework.

Contact information

Bubbly-Doo BV, with company seat at Sint-Pietersvliet 7, 2000 Antwerpen, Belgium and registered with company number 0727.776.548, RPR Antwerp, department Antwerp.

BubblyDoo is reachable for any data processing-related questions at:

Bubbly-Doo BV
Sint-Pietersvliet 7, 2000 Antwerp
Belgium
hello@bubbly-doo.com

Our privacy policy

This cookie policy is complementary to our privacy policy, which you can find here: privacy policy.

Why do we use cookies?

There are different types of cookies that are used for specific purposes or functionality. We use cookies for these purposes:

• To let our website function correctly (”functional cookies”), some of which are essential
• To analyze your behavior in both aggregated and non-aggregated ways (”analytical cookies”)
• To promote our products (”marketing cookies” and “marketing conversion tracking cookies”)
• To show you 3rd-party content (”social media cookies”)

How can I configure my cookies and consent?

When you visit our website in a jurisdiction where opt-in is required, you will be asked to configure your consent preferences on your first visit. No non-essential cookies will be set without consent.

In the footer of our website, you can find a button to view and change your consent at all time.

Consent record

Our consent manager stores values to determine which cookies can be set, which 3rd-party scripts can be loaded, and which data processing can be done.

This record is saved together with an order, user or other stored information.

We use this record to determine your consent for future actions, like if we can send you marketing emails and if we can use your personal data for analytical purposes.

We will refer to the values in the Consent Record in this document, using consentRecord.services.

Functional cookies

bubblyLocale (essential)

Summary: Redirecting the user to the BubblyDoo website in the correct locale.

This is the locale of the website in ISO 639-1 code. For example, nl-BE, es-ES, etc.

This is used to redirect the user to the correct locale when a domain name has multiple locales.

Our server will first guess your locale based on your Accept-Language header, and set the bubblyLocale cookie accordingly.

For example, when a user with an English-language phone goes to bubblydoo.be, we don’t know if we should redirect them to bubblydoo.be/fr or bubblydoo.be/nl. When the user has accessed bubblydoo.be/fr before, they will have a bubblyLocale cookie set to fr-BE, and we know we can redirect them to bubblydoo.be/fr. If it’s not set, it will default to bubblydoo.be/nl.

This cookie is set on all BubblyDoo domains to make adding new locales/dialects to existing domains possible.

First Party

_bubblySession (essential when logged in)

Summary: Keeping the user logged in

This is a session cookie, which is a randomly generated key that is mapped to a user id on the server.

This is only used to remember which user is logged in.

First Party

localStorage.cart (essential)

The items you have saved in your cart.

First Party

localStorage.bubblyConsent (essential)

Consent settings of the user.

First Party

localStorage._ph_opt_in_out_* (essential)

For keeping consent in PostHog. Simple 0/1 value.

Third Party

bubblyFeatureFlags (essential)

Your current feature flag values. These are saved to a cookie to make sure they stay consistent throughout your session.

The server will immediately assign your feature flags on the first load.

First Party

bubblyDistinctId

Summary: Unique identifier for PostHog

This is the distinct id of the visitor and is used together with PostHog to reload your feature flag values, and to identify you at PostHog.

When a user visits the website and does not have a bubblyDistinctId, it will be initialized to a randomly generated UUID on consent.

First Party

Consent Record key: consentRecord.services.bubblydooDistinctId

Analytical cookies

_bubbly_document_referrer

This is the value copied from document.referrer

First Party

Consent Record key: consentRecord.services.bubblydooAttribution

_bubbly_saved_usps

These are the saved URL query parameters, which for now include:

• utm_term
• utm_content
• utm_source
• utm_medium
• utm_campaign

First Party

Consent Record key: consentRecord.services.bubblydooAttribution

_bubbly_attributions

This is used to keep track of the entrypoints by which the user has come to the BubblyDoo website. For example, when the user first clicks on a Facebook ad, then on a Google ad, and then clicks on a BubblyDoo newsletter, this information will be stored in this cookie.

The list has the following fields:

• source: a string like facebook or google-ads
• time: a timestamp
• hash: a hashed unique click id, used to deduplicate refreshes
• data: associated data, includes utm tags, and a hasClickId when available
• lastClickHash: the hash of the last click
• clicks: how many times this attribution was “clicked”

It is used on the backend to analyze which order came from which ad.

First Party

Consent Record key: consentRecord.services.bubblydooAttribution

_ga, _ga_*, _gat, _gid, _gac_* (Google Analytics 4)

These cookies are set by Google Analytics 4.

Loaded across the whole website (needs consent)

Many events are tracked on the frontend for analytical purposes, but it is also integrated with Google Ads.

The cookies can be considered analytical if the user has only consented to the analytical usage. (consentRecord.services.googleAnalyticsAnalyticalStorage)

Third Party

Consent Record key: consentRecord.services.googleAnalyticsScript

ph_phc_* (PostHog)

For keeping track of the current user and active feature flags.

Third Party

Consent Record key: consentRecord.services.posthogCookieStorage

Marketing conversion tracking cookies

_bubbly_saved_click_ids

This is a map of click ids, e.g. the TikTok click id (ttclid) and Pinterest click id (epik) and Meta click id (fbclid), when found on the URL. These values are sent to the respective ad platforms, like the TikTok Events API, Pinterest Conversion API and Facebook Conversion API.

It is not directly used by the server but is transferred to the api server using query parameters.

Third Party

Consent Record key: consentRecord.services.<service>Attribution

Personal data: Marketing conversion tracking data

_fbp

A random but unique identifier for the browser, using the same format as the _fbp that Facebook Pixel generates.

Generated by https://github.com/hansottowirtz/set-fb-cookies

It is not directly used by the server but is transferred to the api server using query parameters.

Third Party

Consent Record key: consentRecord.services.metaAttribution

Personal data: Marketing conversion tracking data

_fbc

The Facebook click id, taken from fbclid in the URL.

Generated by https://github.com/hansottowirtz/set-fb-cookies

It is not directly used by the server but is transferred to the api server using query parameters.

Third Party

Consent Record key: consentRecord.services.metaAttribution

Personal data: Marketing conversion tracking data

Marketing cookies

_ga, _ga_*, _gat, _gid, _gac_* (Google Analytics 4)

These cookies are set by Google Analytics 4.

Many events are tracked on the frontend for analytical purposes, but it is also integrated with Google Ads.

The cookies can be considered marketing if the user has only consented to the marketing usage (consentRecord.services.googleAnalyticsAdStorage)

Third Party

Consent Record key: consentRecord.services.googleAnalyticsScript

_fbp, _fbc (Meta/Facebook Pixel)

Some non-essential conversions are measured using the Meta Pixel.

The Meta Pixel is responsible for matching the customer profile on the website to the customer profile on Meta. This is most done with the Facebook click id (fbclid in the URL).

Third Party

Consent Record key: consentRecord.services.metaPixel or consentRecord.services.metaAttribution

Social media cookies

Trustpilot widgets (3rd party script)

Loaded across the whole website

TP.uuid

Trustpilot widget’s randomly generated uuid

Third Party

Consent Record key: consentRecord.services.trustpilotWidgets

OptanonConsent

Trustpilot widgets’s consent string

Third Party

Consent Record key: consentRecord.services.trustpilotWidgets

OptanonAlertBoxClosed

Trustpilot widget’s date

Third Party

Consent Record key: consentRecord.services.trustpilotWidgets

tp-b2b-access-token

Trustpilot widget’s access token

Third Party

Consent Record key: consentRecord.services.trustpilotWidgets