How This Briefing Works
This dossier opens with key findings, then maps the gap between what CrazyEgg discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection evidence underneath. BLACKOUT observes runtime browser behavior and cites the regulations that address each pattern — legal determinations are your counsel's call.
At a Glance
across 23 sites
vendor fires before consent
2 HIGH
Briefing
Crazy Egg is a heatmap and session recording vendor founded in 2006, detected on 13 sites with a 58.8% pre-consent loading rate. While claiming GDPR compliance and anonymous data collection, the vendor's own website deploys 20+ third-party vendors while only disclosing 5 in their cookie policy. Key finding: significant vendor disclosure gap and reliance on undisclosed identity resolution partners (Intentdata, Semcasting, Rockerbox). Organizations using Crazy Egg should audit consent timing and verify third-party data flows match their privacy disclosures.
What This Means For You
YOUR heatmap and session recording data collected through Crazy Egg may flow to intent data brokers detected on their own site. YOUR visitor behavior — click patterns, scroll depth, form interactions — constitutes demand signal intelligence that Intentdata, Semcasting, and Rockerbox could monetize. YOUR privacy policy likely lists Crazy Egg as an analytics tool while 12+ undisclosed vendors operate in their ecosystem. With a 58.8% pre-consent rate, YOUR consent mechanism may not protect YOUR visitors from tracking before they make a choice.
Risk Channel Breakdown
Session recordings and heatmaps capture granular user behavior, but the pre-consent loading pattern means behavioral data is collected before users can object. This corrupts consent-based analytics segmentation and inflates engagement metrics with non-consented sessions.
Integration with Intentdata, Semcasting, and Rockerbox suggests behavioral data may be enriched with intent signals or fed into advertising ecosystems. Competitor intelligence derived from your visitor behavior could flow through these undisclosed pipes.
Session recordings capture keystrokes, form inputs, and navigation patterns. At 58.8% pre-consent, this creates PII exposure before consent gatekeeping. The 20+ third-party vendor load expands attack surface significantly.
GDPR claim conflicts with 58.8% pre-consent deployment pattern. Cookie policy discloses 5 vendors but 20+ are observed. No subprocessor list published. This creates material misrepresentation risk for clients relying on CrazyEgg's compliance claims.
Threat Indicators
Runtime-observed (BTI-C)
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Full session replay
Identity stitching
Ignoring CMP signals
Device identification
Container/loader (neutral)
Claims-vs-Reality (BTI-X)
Not in privacy policy
Hidden data recipients
False certification claims
CMP vendor list vs runtime
Per-code narrative explanations of what each detected behavior means for your organization
Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →
Claims vs. Reality
BLACKOUT analyzed CrazyEgg's public claims against observed runtime behavior and identified 3 contradictions.
"Cookie policy lists Google Analytics, Facebook, DoubleClick, Drip, CloudFlare"
20+ vendors detected including Airtable, HubSpot, Intentdata, Semcasting, Rockerbox, Dreamdata, Peer39
2 more gaps — with regulatory citations and evidence pointers — available with subscription.
Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →
What To Do
4 for current users · 4 for evaluators
contractual leverage points
Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →
Supply Chain & Pairings
Claims 5, observed 5
googletagmanager, googleanalytics4, linkedinads…
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →