Flockler
How to configure Flockler 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 Flockler social feeds in the Consenter Manager. Flockler'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. Flockler social media walls, grids and carousels embedded on the website (Flockler Commerce, Inc.).
What the service does in this scope. Flockler states that it does not store data about visitors and does not set cookies or tracking codes. When the embed is displayed, images and videos are served by the social media channels; Flockler embeds use YouTube's "no cookies" version by default.
⚠ Recommendation — content from social networks. Flockler itself sets no cookies, but images and videos are loaded from the social networks' servers, which receive the visitor's IP address. Whether those requests read or store device information depends on the network. Load the feed after Consenter consent (or with a click-to-load placeholder) unless your DPO or independent counsel confirms the networks' media requests need no consent.
Step 1 — Implement Flockler
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Unlock additional website features |
| Embed | Flockler display code |
| Loading | After Consenter consent / click-to-load (see ⚠) |
| Video sources | Keep YouTube "no cookies" default |
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 | Flockler; social networks receive requests as Individual Controllers |
| Personalisation model | No personalisation | — |
| Maximum storage duration | — | Flockler stores no visitor data |
| Processing location | United States (Flockler Commerce, Inc. 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