How This Briefing Works
This dossier opens with key findings, then maps the gap between what Phoneburner 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
Phoneburner deploys tracking scripts that activate before consent collection to link website visitors to outbound calling workflows. Pre-consent tracking enables call attribution and lead routing without lawful basis.
What This Means For You
Sales loses website-to-call attribution if Phoneburner tracking is gated. Lead routing automation may degrade without visitor behavior signals. Call campaign effectiveness measurement becomes less accurate. However, retention creates minimal regulatory exposure compared to behavioral surveillance vendors - primary concern is consent violation rather than data commercialization.
Risk Channel Breakdown
Distorts attribution data
Feeds competitor intelligence
Expands attack surface
Pre-consent tracking activation violates GDPR consent requirements and ePrivacy Directive cookie rules.
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 Phoneburner'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
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
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →