glomex
How to configure glomex 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 reflect the glomex player in the Consenter Manager. The glomex player has no privacy settings of its own, 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 glomex embed player and Media Exchange Service (glomex GmbH, Unterföhring, Germany; a subsidiary of ProSiebenSat.1 Media SE).
What the service does in this scope. The glomex player is compliant with IAB TCF 2.2, automatically retrieves consent from the website's CMP and works with a specific set of technology vendors; window.__tcfapi must be available before the player is added to the page. glomex and the publisher, or glomex and advertising partners, may be responsible for processing depending on the activity.
Note on consent signals. The glomex player requires a TCF consent signal. Consenter does not currently support TCF communication, so this guide does not cover configuring the signal; load the player only after consent in Consenter and expect monetisation to be limited.
Step 1 — Implement glomex
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Unlock additional website features; Customise online ads |
| Loading | After Consenter consent |
| Vendors | Disclose glomex's vendor list in the privacy policy |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Unlock additional website features, Customise online ads | Video content and monetisation |
| Tracking method | Third party tracking (crosssession, cross-website) | Player and ad vendors |
| Identifier | Device identifiers | Ad vendors |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address, Users' profiles | Player and ad vendors |
| Legal role of data recipient | Joint Controller | glomex and publisher may be jointly responsible; ad partners as Individual Controller |
| Personalisation model | Profile based | Advertising |
| Maximum storage duration | Per glomex vendor list | Not documented |
| Processing location | Germany; add the United States for US ad vendors | German company; vendors per glomex list |
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