Set up your bannerConfigure Your ToolsSession Recording and Heatmaps

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
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 riskCookieless (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.

ActionConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk (default)
Storage technologyFirst-party cookies under Exemption ModeSession storage (cookieless)First-party cookies
IP addressIP-less modeStored ≤ 3 days (default)Stored ≤ 3 days (default)
Session replayOffOn (masked)On
LoadingSee ⚠ recommendationAfter consentAfter consent

Step 1 — Configure Contentsquare

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk (default)
1Processing purposesOperator decisionImprove the serviceImprove the serviceImprove the service
2Exemption ModeContentsquare project settings / Help Center activationOnOffOff
3CookielessProject settingOffOnOff
4IP-less modeProject settingOnOffOff
5Session replay and maskingSession Replay settings; personal-data masking APIsOffOn, fully maskedOn
6Opt-out handling_cs_optout cookie / opt-out APIProvide an opt-outConsenter withdrawalConsenter withdrawal
7RetentionContract (default 13 months; extensions on request)13 months13 months13 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 fieldConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk (default)
Processing purposesImprove the serviceImprove the serviceImprove the service
Tracking methodFirst party tracking (cross-session)First party tracking (single session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers, IP addressDevice identifiers, IP address
Data categoriesAggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiersBrowsing and interaction data, Device characteristics, Device identifiers, IP addressBrowsing and interaction data, Device characteristics, Device identifiers, IP address
Legal role of data recipientProcessorProcessorProcessor
Personalisation modelNo personalisationNo personalisationNo personalisation
Maximum storage duration13 months13 months13 months (or as extended)
Processing locationPer contract (EU); US if US sub-processorsSameSame

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

On this page