Twitch
How to configure Twitch 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, Customise online ads
Overview
This guide explains how to implement different privacy configurations for Twitch 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. Twitch embedded video, clips and chat (Twitch Interactive, Inc., an Amazon company, US).
What the service does in this scope. Twitch embeds require a parent parameter naming the embedding domain; without it, playback shows an error directing viewers to Twitch. Twitch confirmed that the embedded player serves ads. Twitch's cookie notice describes the cookies it stores on devices.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Link to the Twitch channel; no embed. |
| Configuration B — Higher risk | Embedded player (with ads) loaded after Consenter consent. |
Step 1 — Configure Twitch
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — | Unlock additional website features; Customise online ads |
| 2 | Integration | Website code | Link | player.twitch.tv iframe or JS embed with parent |
| 3 | Loading | Consenter script blocking / click-to-load | — | After consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Twitch is a US enterprise subject to the US CLOUD Act; list the United States.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|
| Entry needed | No | Yes |
| Processing purposes | — | Unlock additional website features, Customise online ads |
| Tracking method | No tracking | Third party tracking (crosssession, cross-website) |
| Identifier | No identifier | Device identifiers, Authentication-derived identifiers (logged-in viewers) |
| Data categories | — | Browsing and interaction data, Device characteristics, Device identifiers, IP address, Users' profiles |
| Legal role of data recipient | — | Individual Controller |
| Personalisation model | — | Profile based |
| Maximum storage duration | — | Per Twitch cookie notice |
| Processing location | — | United States |
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