How This Briefing Works
This report opens with key findings, then maps the gaps between what Livedata 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
Livedata was observed loading and executing before user consent was obtained on 11% of sites where it was detected.
Claims vs. Observed Behavior
programmatic_tracking
“Unknown - requires claims extraction”
C08+C09 detected - cross-domain DSP with pre-consent execution
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Livedata
- →Audit Livedata cross-domain sync scope - map all domains participating in identity coordination
- →Enforce consent gate before Livedata DSP initialization
- →Document consent timestamp vs platform execution for compliance records
- →Verify programmatic bidding works with delayed post-consent loading
If You're Evaluating Livedata
- →Request Livedata technical documentation of cross-domain sync and consent integration
- →Evaluate contextual programmatic platforms eliminating identity tracking
- →Consider supply-path optimization to reduce identity resolution dependencies
- →Investigate DSP alternatives with consent-first architecture
Negotiation Leverage
- →Livedata deploys C08 cross-domain sync + C09 consent bypass - vendor must explain identity coordination
- →Demand disclosure of all domains participating in identity synchronization
- →Require consent-aware initialization capabilities - no pre-consent DSP execution
- →Negotiate opt-out of cross-domain sync if contextual targeting sufficient
- →Establish liability terms for cross-domain tracking and consent violations
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.
Identity stitching
Ignoring CMP signals
IOC Manifest
Indicators of compromise across 4 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
82 detection signatures across scripts, domains, cookies, and network endpoints