Radioplayer
How to configure Radioplayer at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Unlock additional website features
Overview
This guide explains how to reflect the Radioplayer web player in the Consenter Manager. Radioplayer's consent handling is built into the player console rather than configured by the embedding website, so this guide uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. The Radioplayer web player (console) used by broadcasters, opened from the broadcaster's website (Radioplayer Worldwide Ltd, UK).
What the service does in this scope. The web player uses cookies that expire after 12 months; on load it initialises all cookies and removes those the listener does not permit. The player remembers volume, recently played and favourite stations and stores numeric identifiers to recognise the device. A broadcaster can integrate a TCF 2.0 CMP, in which case the player passes the listener's consents to ad providers in the player.
⚠ Recommendation — cookies before choice. Radioplayer's documentation states that all cookies are initialised when the player loads and removed afterwards if not permitted. Have your DPO or independent counsel review this behaviour, and link to the player from a Consenter-gated element if needed.
Step 1 — Implement Radioplayer
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Unlock additional website features |
| Integration | Link or pop-up to the Radioplayer console |
| Consent in the player | Radioplayer cookie dialog |
| Advertising | Requires a TCF consent signal; not currently supported by Consenter |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Unlock additional website features | Radio streaming |
| Tracking method | Third party tracking (crosssession, cross-website) | Player cookies on Radioplayer domains |
| Identifier | Device identifiers | Numeric device identifiers |
| Data categories | Browsing and interaction data, Device identifiers, IP address | — |
| Legal role of data recipient | Individual Controller | Radioplayer operates the console |
| Personalisation model | Group based (behaviour) | Recently played and favourites |
| Maximum storage duration | 12 months | — |
| Processing location | United Kingdom | UK company (UK adequacy decision applies) |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on