The Blue Billywig player uses cookies and browser storage to remember viewer preferences and measure how videos are watched. This article explains which cookies are set, what they are used for, and how you can configure the player’s cookie behaviour, so you can keep your website compliant with cookie legislation such as the EU ePrivacy Directive (the “Cookie Law”) and the General Data Protection Regulation (GDPR).
1.0 | What is a cookie?
A cookie is a small piece of text that a website stores in your browser. The next time the same browser visits the site, the cookie is sent back, so the website can recognise the visitor or recall a previous choice (for example, a preferred volume level).
Cookies are often grouped into two categories:
- Functional cookies – necessary for a feature to work properly. For the video player this means remembering viewer preferences such as volume or selected subtitle language.
- Tracking cookies – collect data about viewing behaviour to feed analytics or personalise advertisements.
In addition to cookies, the player also uses browser local storage, which works similarly to cookies but the data stays in the browser and is not sent back to a server with every request.
2.0 | Which cookies and storage does the player use?
The table below lists all cookies and local storage items set by the Blue Billywig player.
| Name | Storage type | Category | Purpose | Duration |
|---|---|---|---|---|
uuid | Cookie | Tracking | A unique identifier used to count how many different visitors have watched your videos. Required for unique-visitor statistics in the Analytics module. | 365 days |
bb_uuid | Local storage | Tracking | Same unique identifier as above, stored in local storage as a fallback when cookies are read more reliably from there. | Persistent (until cleared) |
bb_test_cookies | Cookie | Technical | A temporary cookie set when the player loads to check whether the browser accepts cookies at all. It is removed immediately afterwards. | Session |
userSelectedAsset | Local storage | Functional | Remembers the video quality level the viewer selected so it is applied automatically on the next visit. | Persistent (until cleared) |
masterMute | Local storage | Functional | Remembers whether the viewer muted the player. | Persistent (until cleared) |
masterVolume | Local storage | Functional | Remembers the volume level the viewer last used. | Persistent (until cleared) |
| Google IMA SDK cookies | Third-party cookies | Tracking | Set by Google when the player loads personalised video advertisements via the IMA SDK. The number and names of these cookies are determined by Google. | Varies |
Under GDPR and the ePrivacy Directive, tracking cookies and third-party advertising cookies generally require explicit user consent (opt-in) before they are set. Functional cookies that are strictly necessary for a feature to work can often be placed without consent, but you should document them in your privacy or cookie policy.
3.0 | Cookie configuration options
The player offers three cookie modes. You set the mode on the playout that powers the embedded player.
3.1 | Enable cookies (default)
Both functional and tracking cookies are placed. This includes the uuid / bb_uuid visitor identifier and any cookies set by the Google IMA SDK for personalised advertisements.
Use this mode only when your visitors have given valid consent for all cookie categories, or when you have established a legitimate interest basis for tracking.
3.2 | Only disable tracking cookies
Only functional cookies and local storage items are placed (userSelectedAsset, masterMute, masterVolume). The visitor identifier (uuid / bb_uuid) is not set, and personalised advertising cookies are not placed.
Statistics remain available in the Analytics module, but unique visitor counts will be less accurate because visitors can no longer be recognised across sessions.
Use this mode when visitors have consented to functional cookies only, or when you want to offer a privacy-friendly default while still providing a fully functional player experience.
3.3 | Disable cookies
No cookies or local storage items are set by the player at all. The player also uses Blue Billywig’s own ad serving instead of the Google IMA SDK, so no third-party advertising cookies are placed either.
When cookies are completely disabled, interactive video features that rely on local storage (for example, branching logic that remembers a viewer’s earlier choices) will not work correctly.
Use this mode when visitors have refused all non-essential cookies, or when you need to comply with a strict cookie-free environment.
4.0 | How to configure the cookie setting
- In the Blue Billywig dashboard, go to Media Library → Playouts.
- Open the playout you want to configure.
- Go to the Miscellaneous tab.
- Find the Cookies dropdown and select the desired option:
- Enable cookies – functional and tracking cookies are placed (default).
- Only disable tracking cookies – only functional cookies and preferences are stored.
- Disable cookies – no cookies or local storage items are set.
- Save the playout. The change takes effect immediately for any player using this playout.
5.0 | Compliance guidance
The table below gives a practical overview of what each cookie mode means for your obligations.
| Scenario | Recommended mode |
|---|---|
| Visitor has consented to all cookies | Enable cookies |
| Visitor has consented to functional cookies only | Only disable tracking cookies |
| Visitor has refused all non-essential cookies | Disable cookies |
| You embed the player before obtaining consent | Disable cookies (switch to the appropriate mode after consent is given) |
What you need to do as a client:
- List player cookies in your cookie policy. Include at least the
uuidcookie (category: tracking/analytics, duration: 365 days) and any Google IMA SDK cookies (category: advertising) if you use video ads. - Connect your Consent Management Platform (CMP) to the player. Blue Billywig supports the IAB Transparency and Consent Framework (TCF). When TCF is integrated, the player automatically adjusts its cookie mode based on the consent signal your CMP provides; no manual intervention needed. See Legitimate Interest Disclosure Statement for more information.
- Do not set tracking cookies before consent is given. Configure a default playout with cookies disabled or tracking cookies disabled, and switch to the “Enable cookies” mode only after valid consent has been obtained.
- Test your setup. Use your browser’s developer tools (Application → Cookies / Local Storage) to verify that only the cookies matching the selected mode are present.