CleverPush
How to configure CleverPush at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Receive marketing offers, Receive personalised marketing offers
Overview
This guide explains how to implement different privacy configurations for CleverPush web push notifications and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. CleverPush web push notifications (CleverPush GmbH, Hamburg, Germany).
What the service does in this scope. To subscribe, the visitor confirms the browser's permission request; CleverPush documents the registration and stores the time of registration and a push token or device ID. CleverPush also statistically evaluates whether and when notifications were displayed and clicked, and stores the topic on which push notifications were activated; the legal basis it names is consent, Art. 6(1)(a) GDPR. Browser storage entries include cleverpush-subscription-status (which CleverPush classifies as technically necessary so that a declining user is not asked again) and cleverpush-subscription-id (subscribers only). Customer data is stored in Germany.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Push subscription with topic selection only; no segmentation by behaviour; script after consent. |
| Configuration B — Higher risk | Push subscription with behavioural segmentation/tags; script after consent. |
⚠ Recommendation — status entry before consent. CleverPush classifies
cleverpush-subscription-statusas technically necessary. Whether this storage access qualifies under § 25(2) TDDDG before any subscription is not confirmed by the sources. Load the CleverPush script after Consenter consent unless your DPO or independent counsel confirms otherwise.
Step 1 — Configure CleverPush
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Receive marketing offers | Receive marketing offers; Receive personalised marketing offers |
| 2 | Loading | Consenter script blocking | After consent | After consent |
| 3 | Opt-in | Browser permission prompt | Required | Required |
| 4 | Segmentation | CleverPush channel settings | Topics only | Tags / behavioural segments |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Receive marketing offers | Receive marketing offers, Receive personalised marketing offers |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Device identifiers, Browsing and interaction data | Device identifiers, Browsing and interaction data, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | Group based (properties) | Group based (behaviour) |
| Maximum storage duration | For the duration of the subscription | For the duration of the subscription |
| Processing location | Germany | Germany |
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