Zemanta
Badge: ⚠️ Caution
This work is licensed under CC BY-SA 4.0
Zemanta
| Feld | Wert |
|---|---|
| Group / Parent Service | Native Advertising |
| Badge | ⚠️ Caution |
| Service Type | Sub-service |
| Sub-service / Relationship Note | Acquired by Outbrain Jul 2017; operates as Outbrain's programmatic DSP platform |
| Infrastructure Only? | No |
| Contact (DPO / Privacy) | [not documented] |
| Assessment Date | 06/08/2026 |
| Version | v2 (06/08/2026) | v1: 22/06/2026 |
Badge & Risk Assessment
- Badge: ⚠️ Caution
- Red Flags:
- RF1 — Own advertising / cross-service profiling
- RF2 — High-risk third-country exposure without meaningful mitigation RELATIONSHIP: Zemanta was acquired by Outbrain in July 2017 (press release: outbrain.com/blog, Jul 2017; covered by AdExchanger, The Drum, tech.eu). Zemanta continues to operate as a standalone DSP brand within the Outbrain group, providing cross-publisher native programmatic advertising capabilities. BADGE RATIONALE: Cross-publisher programmatic DSP with audience targeting (RF1); US company (Outbrain/Zemanta); US transfer (RF2). Privacy policy and DPA via Outbrain group.
- Risk Indicators:
- [not documented]
Reasoning & Sources
Framework Note (v2.2): FRAMEWORK NOTE (v2.2): RF2 (high-risk third-country exposure) is recorded here as a significant risk factor and lowers the domain E score. Under the revised framework, RF2 alone does not trigger Caution — the Caution badge for this service is driven by RF1 / RF3 / RF4 (as noted above). The US transfer risk (where applicable) is covered by DPF participation and/or SCCs, which GDPR treats as a compliant transfer mechanism.
Quellen:
- Outbrain acquisition announcement (outbrain.com/blog/outbrain-zemanta-native-programmatic
- Jul 2017)
- AdExchanger (adexchanger.com, 25 Jul 2017), tech.eu (25 Jul 2017)
- Loeb & Loeb legal representation disclosure.
Processing Purposes (Consenter)
- Receive personalised marketing offers
- Customise online ads (non-TCF)
Notification & Objection Status
- TPP Notified?: Not yet notified
- Decision Contested?: [not documented]
Review Required
- No DPO / privacy contact documented.
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.
Last updated on