How This Briefing Works
This report opens with key findings, then maps the gaps between what Clarity discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Compliance Claim vs Reality
69.2% of 169 detections occur before user consent across 133 sites
Pre-Consent Activity
Clarity was observed loading and executing before user consent was obtained on 69% of sites where it was detected.
Undisclosed Subprocessors
TrustRadius loads pre-consent on vendor site; Google services (Analytics, Ads, AdManager) also present
Security Transparency
Explicitly refuses to provide SOC2, pen-test, or third-party security certifications
Undisclosed Party
Not in privacy policy
Claims vs. Observed Behavior
Compliance Claim vs Reality
“GDPR & CCPA ready, GDPR-compliant”
69.2% of 169 detections occur before user consent across 133 sites
intel_detections pre_consent analysis for vendor_slug=clarity
Undisclosed Subprocessors
“Only Microsoft Azure and MIOL disclosed as data processors”
TrustRadius loads pre-consent on vendor site; Google services (Analytics, Ads, AdManager) also present
Runtime scan of clarity.microsoft.com
Security Transparency
“Data encryption and Azure security mentioned”
Explicitly refuses to provide SOC2, pen-test, or third-party security certifications
FAQ: Currently, we are not able to provide these third-party reports
DNT Non-Compliance
“Supports GPC for opt-out”
Does NOT honor browser Do-Not-Track signals
FAQ: Clarity does not currently respond to browser DNT signals
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Clarity
- →Audit your consent implementation — 69.2% pre-consent rate industry-wide means your deployment likely records sessions before users consent
- →Implement Clarity's cookie consent mode to delay all tracking until consent is obtained — this is not enabled by default
- →Review your privacy policy to disclose Clarity as a session recording tool capturing DOM state, clicks, and scroll behavior — not just 'analytics'
- →Mask sensitive form fields since Clarity has no SOC2 certification to verify data handling security
- →Test GPC signal handling on your implementation — verify Clarity respects Global Privacy Control headers
If You're Evaluating Clarity
- →Recognize that 'free' means Microsoft benefits from your users' behavioral data — there is no free analytics
- →Require written confirmation of how Clarity's consent mode works before any deployment
- →Request Microsoft complete your security questionnaire since SOC2 certification is unavailable for Clarity
- →Verify your legal team accepts Microsoft's standard DPA terms for session recording data processed through Clarity
- →Consider paid alternatives (Hotjar, FullStory) if your vendor approval process requires security certifications
Negotiation Leverage
- →Consent-first deployment: 69.2% pre-consent rate industry-wide. Require your implementation team to configure Clarity's cookie consent mode to delay all tracking until after affirmative consent, verified by runtime testing before launch.
- →Security documentation gap: Clarity explicitly refuses SOC2 or third-party security certifications. Require Microsoft to complete your security questionnaire and provide alternative assurance documentation before vendor approval.
- →Data use restrictions: As a free product, Microsoft benefits from behavioral data. Review Microsoft's DPA terms to understand exactly how session recording data feeds into their advertising and AI products, and negotiate restrictions where possible.
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Full session replay
Ignoring CMP signals
Device identification
PII deanonymization
IOC Manifest
Indicators of compromise across 5 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
15 detection signatures across scripts, domains, cookies, and network endpoints
