Security, Privacy, AI and CSR information for all Piano products now lives in one place. Explore our Compliance Center.
Analytics
English French
English French

How do I set up ePrivacy Exemption in Piano Analytics?

Please check our Compliance Center for additional content about Privacy concerns.

To set up the ePrivacy exemption, confirm that you're eligible, sign the legal documents with Piano, and tag your site so that visitors are measured in exempt mode until they consent. Validate the approach with your data protection officer (DPO) first.

Since July 4, 2025, the CNIL no longer publishes a list of pre-approved solutions, so you, as data controller, carry out a self-assessment.

  1. Check the eligibility criteria.

  2. Sign the Data Processing Agreement (DPA) and the exemption instruction document. Piano then activates the safeguards for your organization.

  3. Set up your tagging, using the exempt mode by default.

  4. Go to production only after your tagging is validated and the exemption is signed.

The exemption applies to your whole organization, so all sites share the same safeguards. To apply different terms to different sites, create a separate organization or split the existing one. Contact Piano Support to discuss your case.

Eligibility and scope

The exemption applies only if your implementation meets all of these criteria:

  • Purpose: audience measurement only, with no advertising use.

  • Data use: for your own use as publisher. You don't share the data with third parties or cross it with other processing.

  • Tracking scope: no cross-domain tracking.

  • Anonymous statistics: IP anonymization, no direct identifiers, and limited retention.

  • Opt-out: visitors can object to measurement through an opt-out page on your site, even without consent.

Applicability also depends on the supervisory authority that is competent for you as data controller. Validate it with your DPO.

The exemption lets you send analytics hits before consent in exempt mode, collect strictly necessary data when a visitor refuses cookies, and switch to opt-in once consent is given. It doesn't let you collect personal data without a legal basis or bypass consent for marketing or advertising, and you still need to justify every data point you collect.

Two documents must be in place before Piano activates the safeguards:

  1. Data Processing Agreement (DPA): covers Piano's role as data processor.

  2. Exemption instruction document: an annex to the DPA, signed through DocuSign. Use the personal email address of the signatory, not a generic one. Keep the signed PDF for your compliance records.

Once both are signed, Piano activates the organization-level safeguards and confirms they are ready.

Deploy exempt mode to production only after your tagging is validated and the exemption is signed. The signed contract is what supports you in an audit.

Safeguards applied by Piano

These safeguards apply to your entire organization:

  • IP anonymization: Piano removes the last octet of each IP address. City-level geolocation becomes less reliable, while region and country stay accurate. You can't exclude individual IP addresses, so exclude /24 ranges instead. See How can I exclude IP addresses in Piano Analytics?

  • Visitor ID masking: the visitor_id property is masked by default in the Data Model, so you can't use it to identify visitors. Piano still uses it internally, so visits and visitors metrics remain available. Analysis at the individual visitor level isn't available in exempt mode.

  • Data retention: data is purged automatically on a rolling 25-month basis. Export your data before the window closes if you need a longer history.

  • Additional masking: depending on your requirements, you can also mask connection_isp and visit_converted in Data Management > Data Model.

Privacy modes

Piano Analytics applies one mode to each visitor. The mode is stored in the first-party _pprv cookie and used on every event until it changes or the cookie is deleted.

Mode

When it applies

What is collected

Values

Exempt

The visitor arrives, ignores the banner, or refuses cookies.

Strictly necessary data only.

SDK: essential

Property: exempt

Opt-in

The visitor accepts.

All events and properties.

SDK: opt-in

Property: optin

Opt-out

The visitor uses your opt-out page.

Data is anonymized and excluded from your reports. Only mandatory storage is used.

SDK: opt-out

Property: optout

Extended opt-out

The visitor opts out, and you want anonymous aggregate reporting. Requires JS SDK 6.13.0 or later.

All events and properties, anonymized, with no visitor or visit ID.

SDK: enableExtendedOptout configuration

Property: extended-optout

For the full list of storage, events and properties per mode, see Consent rules by Consent Mode.

Tagging requirements

Hybrid measurement, which combines the exemption with consent-based collection, is the recommended setup. Visitors who ignore or refuse the banner stay measured in exempt mode, which preserves measurement for non-engaging users. Visitors who accept are measured in full, including marketing attribution. Your consent management platform (CMP) records the visitor's choice, and your tagging passes it to Piano Analytics:

Visitor action

Mode

No choice yet

Exempt

Refuses on the banner, including individual purposes

Exempt

Accepts

Opt-in

Uses the opt-out page

Opt-out

Make sure that:

  • Default mode: exempt is set as the default. The JavaScript SDK applies opt-in if you set nothing, so set window.pdl.consent.defaultPreset.PA to "essential" before loading the SDK. For other SDKs and the syntax to update the mode, see Consent management in the developer documentation.

  • Opt-out page: you provide an opt-out option somewhere on your site, such as a toggle in a "Cookie management" page linked from your footer. It doesn't have to be in the CMP itself.

  • Cookies: you don't delete cookies when a visitor refuses. Without the visitor cookie, every visit generates a new visitor ID and your visitor data becomes unreliable. The _pprv cookie must always be present, whatever the mode.

  • Exempt properties: you add custom properties to exempt mode only after your DPO or legal team validates that they are strictly necessary. Piano doesn't validate them for you, so be ready to justify each one in a CNIL audit.

Events recorded in exempt mode aren't converted to opt-in when a visitor accepts later. Only later events carry the opt-in mode.

Last updated: