Sleeknote
How to configure Sleeknote 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 Sleeknote 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. Sleeknote on-site pop-ups and sign-up campaigns (Sleeknote ApS, Denmark).
What the service does in this scope. Sleeknote sets _sn_m (persistent, 1 year, classified as marketing, can be opted out), which stores geo location if geo-targeting is used and the IP address if IP targeting is used, and SNS (session cookie, Unix timestamp); SiteData is held in session storage. Sleeknote's update made it easier to disable visitor tracking. The customer is controller and Sleeknote the processor; EU customers sign a DPA.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Campaigns without geo or IP targeting; visitor tracking disabled; after consent. |
| Configuration B — Higher risk | Campaigns with geo and IP targeting and visitor analytics (_sn_m); after consent. |
No configuration without prior consent. Even without targeting, Sleeknote sets a session cookie and session storage; whether these are strictly necessary for a marketing pop-up is not established by the sources.
Step 1 — Configure Sleeknote
| # | 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 | Visitor tracking | Sleeknote analytics and consent settings | Disabled | Enabled |
| 3 | Geo / IP targeting | Campaign targeting options | Off | On |
| 4 | Loading | Consenter script blocking | After consent | After consent |
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 (single session) | First party tracking (cross-session) |
| Identifier | No identifier | Device identifiers, IP address |
| Data categories | Browsing and interaction data, User-provided data (on submission) | Browsing and interaction data, Device identifiers, IP address, Non-precise location data, User-provided data, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | Group based (behaviour) |
| Maximum storage duration | Session | 1 year (_sn_m) |
| Processing location | Per DPA | Per DPA |
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