Contentsquare
How to configure Contentsquare at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service
Overview
This guide explains how to implement different privacy configurations for Contentsquare 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. The Contentsquare web tag (experience analytics, heatmaps, session replay).
What the service does in this scope. Contentsquare collects IP addresses, an online unique ID and behavioural data on how visitors interact with the site. It uses only first-party cookies, with a maximum lifetime of 13 months, for example _cs_id (13 months, user data), _cs_s (30 minutes, session) and _cs_c (consent state for session replay masking). By default, IP addresses are stored for no longer than three days; an IP-less mode avoids collecting the IP address. The cookieless option replaces cookies with session storage, which expires at the end of the session. Personal data is kept for up to 13 months by default.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk (⚠ no-consent option) | Exemption Mode for audience measurement, with IP-less mode and no session replay. Self-assessed exemption. |
| Configuration B — Medium risk | Cookieless (session storage) with session replay, loaded after consent. |
| Configuration C — Higher risk (default) | Standard first-party cookies (13 months), session replay, loaded after consent. |
⚠ Recommendation — Configuration A relies on a self-assessed exemption. Contentsquare's Exemption Mode is designed to let customers use its cookies without consent under the audience-measurement exemption. CNIL's formal evaluation programme has ended, so qualifying configurations must be described as a self-assessed exemption, not as CNIL-approved. Use A without consent only if your DPO or independent counsel confirms that your configuration meets the exemption conditions; in Germany, § 25 TDDDG contains no equivalent analytics exemption.
| Action | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk (default) |
|---|---|---|---|
| Storage technology | First-party cookies under Exemption Mode | Session storage (cookieless) | First-party cookies |
| IP address | IP-less mode | Stored ≤ 3 days (default) | Stored ≤ 3 days (default) |
| Session replay | Off | On (masked) | On |
| Loading | See ⚠ recommendation | After consent | After consent |
Step 1 — Configure Contentsquare
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk (default) |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service | Improve the service |
| 2 | Exemption Mode | Contentsquare project settings / Help Center activation | On | Off | Off |
| 3 | Cookieless | Project setting | Off | On | Off |
| 4 | IP-less mode | Project setting | On | Off | Off |
| 5 | Session replay and masking | Session Replay settings; personal-data masking APIs | Off | On, fully masked | On |
| 6 | Opt-out handling | _cs_optout cookie / opt-out API | Provide an opt-out | Consenter withdrawal | Consenter withdrawal |
| 7 | Retention | Contract (default 13 months; extensions on request) | 13 months | 13 months | 13 months (illustrative; may be extended) |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Contentsquare SAS is a French company. Check the storage region and sub-processors in your contract; where US sub-processors are used, list the United States as a potential access location.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk (default) |
|---|---|---|---|
| Processing purposes | Improve the service | Improve the service | Improve the service |
| Tracking method | First party tracking (cross-session) | First party tracking (single session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, IP address | Device identifiers, IP address |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers | Browsing and interaction data, Device characteristics, Device identifiers, IP address | Browsing and interaction data, Device characteristics, Device identifiers, IP address |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | No personalisation | No personalisation |
| Maximum storage duration | 13 months | 13 months | 13 months (or as extended) |
| Processing location | Per contract (EU); US if US sub-processors | Same | Same |
Privacy-policy follow-up
- Contentsquare as processor; mode used (exemption, cookieless or standard); cookies; IP handling; retention; for A, the opt-out mechanism and the basis for the self-assessed exemption.
Verification checklist
- A: no replay data captured; no IP collected; opt-out available.
- B/C: no Contentsquare requests before consent.
- Masking verified in replays.
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