How This Briefing Works
This dossier opens with key findings, then maps the gap between what Leadmagic 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 1 sites
vendor fires before consent
Briefing
Visitor identification technology deploying pre-consent tracking. Consent bypass (C09) in deanonymization context creates regulatory violations - converting anonymous browsing to identified profiles without user acknowledgment.
What This Means For You
Organizations using Leadmagic inherit deanonymization consent-timing liability. Privacy audits detecting pre-consent visitor identification create compliance exposure. Lead intelligence built on non-consented identity resolution produces legally questionable sales pipeline.
Risk Channel Breakdown
Distorts attribution data
Feeds competitor intelligence
Expands attack surface
C09 consent bypass - visitor identification begins before consent mechanism completion
Threat Indicators
Runtime-observed (BTI-C)
Ignoring CMP signals
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 Leadmagic'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
3 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
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →