Juicer
How to configure Juicer 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 Juicer social feeds in the Consenter Manager. Juicer's embeds have no privacy settings to choose between, 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. Juicer (Juicer.io / Juicer Social) social media feeds embedded on the website.
What the service does in this scope. Juicer states that it does not track individuals who view Juicer feeds on webpages. When a feed is embedded, viewers are served static image and video files directly from the social media networks' servers; Juicer does not transfer personal data to the networks, but what the networks record is subject to their privacy policies. Juicer offers a DPA and SCCs.
⚠ Recommendation — content from social networks. Juicer itself does not track feed viewers, but media is loaded from the social networks' servers, which receive the visitor's IP address. Load the feed after Consenter consent (or with a click-to-load placeholder) unless your DPO or independent counsel confirms these requests need no consent.
Step 1 — Implement Juicer
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Unlock additional website features |
| Embed | Juicer embed code or WordPress plugin |
| Loading | After Consenter consent / click-to-load (see ⚠) |
| Contract | Juicer DPA |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Unlock additional website features | Social feed display |
| Tracking method | Third party tracking (single session, cross-website) | Media requests to social networks |
| Identifier | IP address | Media requests |
| Data categories | IP address, Device characteristics | Server requests |
| Legal role of data recipient | Processor | Juicer; social networks as Individual Controllers |
| Personalisation model | No personalisation | — |
| Maximum storage duration | — | Juicer does not track viewers |
| Processing location | United States | Juicer and social networks; the US CLOUD Act |
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