Microsoft Clarity
How to configure Microsoft Clarity 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, Personalise the website
Overview
This guide explains how to implement different privacy configurations for Microsoft Clarity 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. This guide covers the Microsoft Clarity tracking script on a website (session recordings, heatmaps, insights), with Consenter passing consent to Clarity through the Consent API v2 (consentv2).
Out of scope. Clarity for mobile apps; custom identifiers set through the Clarity client API (custom-id), which would link recordings to known users and require separate assessment.
What the service does in this scope. Clarity captures how the page renders and user interactions such as mouse movements, clicks and scrolls. It sets the first-party cookies _clck (Clarity user ID, persisted per site) and _clsk (session), and, when advertising storage is granted, Microsoft cookies including MUID ("Identifies unique web browsers visiting Microsoft sites … used for advertising, site analytics, and other operational purposes").
Legal role. Microsoft states that Clarity "operates as a data controller". Clarity customers in the EU contract with Microsoft Ireland Operations Limited (MIOL).
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Script loads after analytics consent; ad_Storage denied (no MUID); Strict masking. |
| Configuration B — Higher risk (default settings) | Script loads after consent; ad_Storage and analytics_Storage granted (MUID set); Balanced masking (default). |
No configuration without prior consent. Microsoft requires a valid consent signal for visitors from the EEA, the UK and Switzerland. When consent is denied, Clarity continues to run without cookies and still sends /collect calls. Recording sessions without consent still processes personal data, and Microsoft does not document this mode as a consent-free configuration. In both configurations below, Consenter blocks the script until consent.
| Action | Configuration A — Lower risk | Configuration B — Higher risk (default settings) |
|---|---|---|
| Cookies by default (Settings > Setup) | Off | Off |
| Script loading | Blocked until consent | Blocked until consent |
consentv2 after consent | analytics_Storage: "granted", ad_Storage: "denied" | analytics_Storage: "granted", ad_Storage: "granted" |
| Masking mode | Strict | Balanced (default) |
| Consenter Manager entries | One entry (Microsoft as Individual Controller) | One entry (Microsoft as Individual Controller) |
Step 1 — Configure Microsoft Clarity
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Higher risk (default settings) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Personalise the website (only if insights are used to adapt the site) |
| 2 | Setting cookies by default | Settings > Setup, turn off setting cookies by default | Off | Off |
| 3 | Script loading | Consenter script blocking for the Clarity entry | Blocked until consent | Blocked until consent |
| 4 | Consent signal | window.clarity('consentv2', {analytics_Storage, ad_Storage}) | Analytics granted, ads denied | Both granted |
| 5 | Masking mode | Settings > Masking > Masking mode | Strict — entire content masked | Balanced (default) — numbers, email addresses and input content masked |
| 6 | Element-level masking | Settings > Masking > Mask by element | Add elements containing personal data | Optional |
| 7 | Data retention | Not configurable. Recordings 30 days; labelled or favourited sessions 13 months; heatmaps and click data 13 months | Fixed | Fixed |
| 8 | Withdrawal | consentv2 with both values "denied"; Clarity stops writing cookies for that user | Configure and test | Configure and test |
Configuration A — Lower risk
- Intended use: UX analysis with minimal content capture.
- Resulting processing: interaction data and page structure; text content masked;
_clckand_clskonly. - Why lower risk: no Microsoft advertising identifier; page text not captured.
- Remaining risk: Microsoft is controller of the data; retention is fixed.
Configuration B — Higher risk (default settings)
- Intended use: UX analysis with readable page content and the Microsoft Advertising link.
- Resulting processing: as A, plus non-sensitive page text, and
MUIDand related third-party cookies used across Microsoft sites. - Why higher risk: a cross-site Microsoft identifier is set and more page content is captured.
Step 2 — Map the configuration in the Consenter Manager
Processing location (applies to all entries). EU customers contract with MIOL. Clarity data is stored in Microsoft Azure. Microsoft Corporation is a US company and can be required to disclose data in its possession, custody or control regardless of storage location. The United States is listed as a potential processing and access location.
Configuration A — Lower risk
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Improve the service | Session recordings and heatmaps for UX analysis. |
| Tracking method | First party tracking (cross-session) | _clck persists the Clarity user ID per site. |
| Identifier | Device identifiers, IP address | _clck user ID; IP address with each request. |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address, Aggregated site statistics | Interactions and rendering; heatmaps. |
| Legal role of data recipient | Individual Controller | Clarity "operates as a data controller". |
| Personalisation model | No personalisation | — |
| Maximum storage duration | 13 months | Heatmaps and labelled sessions; recordings 30 days. |
| Processing location | EU contracting entity (MIOL); Microsoft Azure; United States as potential processing and access location | See note above. |
Configuration B — Higher risk (default settings)
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Improve the service; Personalise the website (if applicable) | As used by the operator. |
| Tracking method | Third party tracking (crosssession, cross-website) | MUID identifies browsers across Microsoft sites. |
| Identifier | Device identifiers, IP address | _clck, MUID. |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address, Aggregated site statistics | As A, with less masking. Add "User-provided data" only if unmasked elements display content the visitor entered. |
| Legal role of data recipient | Individual Controller | — |
| Personalisation model | No personalisation | Select "Group based (behaviour)" only if Clarity insights drive site variants. |
| Maximum storage duration | 13 months | — |
| Processing location | As A | See note above. |
Privacy-policy follow-up
- Microsoft (MIOL / Microsoft Corporation) as independent controller; session recording and heatmaps; cookies
_clck,_clskand, for B,MUIDand related Microsoft cookies; masking applied; retention 30 days / 13 months; consent under ePrivacy / TDDDG and GDPR legal basis stated separately; US transfer and potential access by US authorities.
Verification checklist
- Before consent: no request to
clarity.ms; no_clck,_clskorMUID. - After consent (A):
_clck/_clskset; noMUID. - Masking: recordings reviewed for unmasked personal data.
- Withdrawal: cookies no longer written after
consentv2denied.
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