How This Briefing Works
This dossier opens with key findings, then maps the gap between what Vidyard 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 5 sites
vendor fires before consent
Briefing
Vidyard operates as a video hosting and analytics platform exhibiting consent bypass when video player tags initialize before host site consent collection. Counselor impact stems from tag-based deployment enabling pre-consent tracking activation.
What This Means For You
Revenue teams using Vidyard face consent liability when video player tags fire before user authorization. Video engagement data (watch time, interaction points) captured pre-consent creates compliance exposure.
Risk Channel Breakdown
Distorts attribution data
Feeds competitor intelligence
Expands attack surface
Video player tags initialize before consent mechanisms activate, enabling video engagement tracking before user authorization.
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 Vidyard'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 →