MessengerPeople (Sinch Engage)
How to configure MessengerPeople (Sinch Engage) 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, Receive marketing offers
Overview
This guide explains how to reflect the Sinch Engage (formerly MessengerPeople) website widget in the Consenter Manager. The sources do not document configurable privacy settings for the widget, 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 Sinch Engage chat widget, used as an entry point from the website into messenger channels such as WhatsApp (MessengerPeople GmbH, Munich, part of the Sinch group).
What the service does in this scope. Sinch Engage offers widgets as chat entry points on websites. MessengerPeople documents a way to initialise the chat script only after a third-party cookie tool has given the go-ahead. Once a visitor clicks through to a messenger, the messenger operator (e.g. WhatsApp/Meta) processes data under its own terms.
⚠ Research gap. Cookie names and lifetimes of the widget were not found in public documentation. Inspect the widget in the browser before finalising the mapping.
Step 1 — Implement Sinch Engage
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Unlock additional website features; Receive marketing offers (if used for newsletters via messenger) |
| Loading | Initialise the widget script only after Consenter consent |
| Messenger channels | Disclose each channel operator (e.g. Meta for WhatsApp) in the privacy policy |
| Contract | DPA with MessengerPeople GmbH / Sinch |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Unlock additional website features | Chat entry point |
| Tracking method | First party tracking (single session) | Assumed; verify in the browser |
| Identifier | No identifier | Assumed; verify |
| Data categories | Browsing and interaction data, User-provided data | Chat entry |
| Legal role of data recipient | Processor | Provider on behalf of the operator |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Per cookie inspection | Not documented |
| Processing location | Per DPA | German entity of the Swedish Sinch group; check the DPA for US sub-processors |
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