How This Briefing Works
This dossier opens with key findings, then maps the gap between what Liquidm 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 0 sites
vendor fires before consent
Briefing
Liquidm is a demand-side platform detected via static signature matching. No active behavioral threats were observed during scanner analysis. DSPs typically deploy extensive cross-domain tracking infrastructure for programmatic ad targeting.
What This Means For You
No measurable behavioral risk from current detection data. DSPs inherently operate cross-domain tracking infrastructure for bid optimization and audience matching. Runtime analysis is needed to assess actual behavioral footprint.
Risk Channel Breakdown
Distorts attribution data
Feeds competitor intelligence
Expands attack surface
Consent violations
Claims vs. Reality
BLACKOUT analyzed Liquidm's public claims against observed runtime behavior and identified 1 contradiction.
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
2 for current users · 1 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
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →