How This Briefing Works
This report opens with key findings, then maps the gaps between what Cloudflare Insights 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
Pre-Consent Activity
Cloudflare Insights was observed loading and executing before user consent was obtained on 39% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Unknown”
Requires claims extraction via CDT
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Cloudflare Insights
- →Audit Cloudflare Insights deployment to verify no server-side tracking state persistence after consent rejection
- →Disable Cloudflare Zaraz tag manager or restrict to consent-conditional client-side execution only
- →Review Cloudflare Bot Management integration to prevent behavioral data sharing with Insights analytics
- →Implement edge cache header controls to prevent visitor ID coordination across CDN responses
- →Establish contractual restrictions on Cloudflare network intelligence data sharing with advertising partners
If You're Evaluating Cloudflare Insights
- →Request Cloudflare CDN deployment without Insights analytics or require strict first-party data isolation
- →Require contractual guarantee that edge cache state does not persist visitor tracking after consent rejection
- →Verify Cloudflare deployment does not use TLS fingerprinting or HTTP/2 characteristics for visitor reconnection
- →Assess alternative CDN providers (Fastly without analytics, AWS CloudFront with restricted telemetry) for comparison
- →Demand pricing concessions reflecting CDN-only deployment without analytics or tag management integration
Negotiation Leverage
- →VRS 80 classification with 100% CAC subsidization justifies significant discount if Insights analytics is permanently disabled
- →100% legal tail risk from edge cache persistence demands indemnification for GDPR violations through server-side tracking bypass
- →Require contractual guarantee that CDN infrastructure does not persist visitor identification state beyond session lifetime
- →Request monthly attestation that Cloudflare network intelligence does not feed advertising partners or demand generation networks
- →Negotiate CDN-only deployment without Insights, Zaraz, or Bot Management behavioral data collection
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
Impact: Cloudflare Insights tracking embedded in CDN responses bypasses client-side consent controls through server-side state management.
Keystroke/mouse tracking
Impact: Mouse movements and scroll patterns captured via Cloudflare Bot Management integration, feeding engagement scoring models.
Full session replay
Impact: DOM capture enabled through Cloudflare Zaraz integration, recording visitor interactions across all CDN-served properties.
Identity stitching
Impact: Visitor IDs synchronized across all Cloudflare-protected domains via edge cache coordination and HTTP header state.
Ignoring CMP signals
Impact: CDN-level tracking persists after cookie rejection through server-side visitor identification and edge cache state management.
Device identification
Impact: TLS fingerprinting and HTTP/2 characteristics used to reconnect visitors across cookie deletion via CDN infrastructure visibility.
Long-lived identifiers
Impact: Edge cache state creates tracking persistence that survives cookie deletion, browser resets, and client-side privacy controls.
Container/loader (neutral)
Impact: Cloudflare Zaraz tag manager deploys tracking infrastructure at CDN edge, bypassing client-side consent management platforms.
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
211 detection signatures across scripts, domains, cookies, and network endpoints