How This Briefing Works
This dossier opens with key findings, then maps the gap between what RevenueHero 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 6 sites
vendor fires before consent
Briefing
Scheduling platform for sales engagement. Combines cross-domain sync with consent bypass to maintain visitor identity across properties. Creates Broker risk through cross-domain exposure and Counselor liability from pre-consent activation.
What This Means For You
Sales teams gain scheduling automation but expose visitor identity through cross-domain sync (Broker). Legal teams face consent bypass liability from immediate activation. RevOps must audit cross-domain data flow to prevent scheduling behavior leakage.
Risk Channel Breakdown
Distorts attribution data
Cross-domain visitor sync potentially exposes scheduling behavior and sales engagement to partners with domain access
Expands attack surface
Identity synchronization initiates before consent, establishing cross-domain tracking without legal basis
Threat Indicators
Runtime-observed (BTI-C)
Identity stitching
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 RevenueHero'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 · 3 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 →