Piano Analytics (formerly AT Internet)
How to configure Piano Analytics (formerly AT Internet) 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, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for Piano Analytics and how to reflect them in the Consenter Manager. It covers the TPP entries "AT INTERNET" and "Piano" (analytics), and the alias "XiTi".
- 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 Piano Analytics JavaScript SDK on a website. Other Piano products (Composer, Audience/DMP) are out of scope.
What the service does in this scope. Piano Analytics uses privacy modes set per visitor from the CMP: opt-in (consent; full collection and identifiers), exempt/Essential (no consent; only properties classified as strictly necessary are sent), opt-out (no audience data; only a passage signal) and Extended opt-out (events without visitor ID). A _pcid cookie may hold an identifier usable by other Piano products, which Piano Analytics does not use in Extended opt-out mode.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk (⚠ no-consent) | exempt (Essential) mode for visitors who have not consented, with opt-out link. Self-assessed exemption. |
| Configuration B — Medium risk | opt-in mode after consent; no user ID or personal data. |
| Configuration C — Higher risk | opt-in mode after consent, with user ID and personal data properties. |
⚠ Recommendation — Configuration A relies on a self-assessed exemption. Piano documents an exempt mode for the consent exemption and published a configuration guide for the former CNIL programme. That programme has ended, so qualifying configurations must be described as a self-assessed exemption, not as CNIL-approved. In Germany, § 25 TDDDG contains no equivalent audience-measurement exemption. Use A without consent only after review by your DPO or independent counsel.
Step 1 — Configure Piano Analytics
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service | Improve the service; Support marketing analytics |
| 2 | Privacy mode | SDK consent API (pa.consent.setMode / setByPurpose) from the CMP | exempt before consent; opt-out on refusal | opt-in after consent | opt-in after consent |
| 3 | Exempt property list | Organisation privacy settings (strictly necessary properties) | Default list only | — | — |
| 4 | User ID / personal data properties | Tagging | Not sent | Not sent | Sent |
| 5 | Extended opt-out | enableExtendedOptout at initialisation | Optional for refusers | Optional | Optional |
| 6 | Data retention | Privacy configurations | Shortest suitable | Default | Default |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Piano Software, Inc. is a US company; it can be required to disclose data in its possession, custody or control regardless of storage location. The United States is listed as a potential access location.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk |
|---|---|---|---|
| Processing purposes | Improve the service | Improve the service | Improve the service, Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, IP address | Device identifiers, IP address, Authentication-derived identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address, Non-precise location data | As B, plus Authentication-derived identifiers, Users' profiles |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | No personalisation | No personalisation |
| Maximum storage duration | Per privacy configuration | Per privacy configuration | Per privacy configuration |
| Processing location | EU (per contract); United States as potential access location | Same | Same |
Privacy-policy follow-up
- Piano as processor; privacy modes in use; for A, the exemption basis and opt-out link; cookies; retention; potential access by US authorities.
Verification checklist
- Before consent: requests carry
visitor_privacy_mode = exempt(A) or no requests (B, C). - After refusal: opt-out mode applied.
- C: user IDs only after consent.
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