Set up your bannerConfigure Your ToolsAnalytics

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".

  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 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.

ConfigurationSummary
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 riskopt-in mode after consent; no user ID or personal data.
Configuration C — Higher riskopt-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 areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the serviceImprove the service; Support marketing analytics
2Privacy modeSDK consent API (pa.consent.setMode / setByPurpose) from the CMPexempt before consent; opt-out on refusalopt-in after consentopt-in after consent
3Exempt property listOrganisation privacy settings (strictly necessary properties)Default list only——
4User ID / personal data propertiesTaggingNot sentNot sentSent
5Extended opt-outenableExtendedOptout at initialisationOptional for refusersOptionalOptional
6Data retentionPrivacy configurationsShortest suitableDefaultDefault

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 fieldConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk
Processing purposesImprove the serviceImprove the serviceImprove the service, Support marketing analytics
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers, IP addressDevice identifiers, IP address, Authentication-derived identifiers
Data categoriesAggregated site statistics, Browsing and interaction data, Device characteristicsAggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address, Non-precise location dataAs B, plus Authentication-derived identifiers, Users' profiles
Legal role of data recipientProcessorProcessorProcessor
Personalisation modelNo personalisationNo personalisationNo personalisation
Maximum storage durationPer privacy configurationPer privacy configurationPer privacy configuration
Processing locationEU (per contract); United States as potential access locationSameSame

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

On this page