Spotify
How to configure Spotify 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 implement different privacy configurations for Spotify content on a website and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Spotify embeds (tracks, playlists, podcasts) via iframe from open.spotify.com/embed/, or a plain link. Spotify AB is a Swedish company.
What the service does in this scope. Cookies associated with the Spotify embed include sp_landing, sp_ab, sp_t, sp_usid, sp_m and _ga. When a visitor is logged in to Spotify, the embed attempts to use the visitor's Spotify session.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Link to Spotify; no embed. |
| Configuration B — Higher risk | Embedded player loaded after Consenter consent (or click-to-load). |
Configuration A without website consent. A link sets nothing on your website; mention Spotify in the privacy policy.
Step 1 — Configure Spotify
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — | Unlock additional website features |
| 2 | Integration | Website code | Link | iframe embed |
| 3 | Loading | Consenter script blocking / click-to-load | — | After consent |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|
| Entry needed | No | Yes |
| Processing purposes | — | Unlock additional website features |
| Tracking method | No tracking | Third party tracking (crosssession, cross-website) |
| Identifier | No identifier | Device identifiers, Authentication-derived identifiers (logged-in visitors) |
| Data categories | — | Browsing and interaction data, Device characteristics, Device identifiers, IP address |
| Legal role of data recipient | — | Individual Controller |
| Personalisation model | — | No personalisation (on your site) |
| Maximum storage duration | — | Per Spotify cookie policy |
| Processing location | — | Sweden / per Spotify privacy policy; check for US transfers |
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