How This Briefing Works
This report opens with key findings, then maps the gaps between what LogRocket discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Claims vs. Observed Behavior
pending
“Unknown”
Requires claims extraction via CDT
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use LogRocket
- →Audit session replay data for PII exposure—forms, API responses, console logs all captured
- →Extract cross-session tracking evidence showing fingerprinting persistence
- →Map engineering insights to competitor product feature releases
If You're Evaluating LogRocket
- →Quantify PII exposure from form inputs and API responses in session replays
- →Calculate engineering intelligence monetization (your bugs, their insights revenue)
- →Document GDPR Article 32 violations from inadequate security in replay data storage
Negotiation Leverage
- →LogRocket session replays contain PII—forms, API responses, console logs captured in full
- →100/100 CAC subsidization through anonymized engineering intelligence syndication
- →Cross-domain sync (C08) stitches sessions across all properties—comprehensive surveillance
- →Fingerprinting (C10) persists identity despite user privacy actions—consent bypass documented
- →Redux state capture exposes application architecture and business logic to competitors
- →90/100 legal exposure—GDPR Article 5 violations from excessive data capture certain
- →Evidence pack includes session replays showing PII exposure and fingerprinting proof
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Evasion infrastructure, auditor bypass
Impact: Session recording bypasses browser privacy controls through DOM mutation observation
Keystroke/mouse tracking
Impact: Mouse movement, scroll patterns, and interaction timing captured for rage click detection
Full session replay
Impact: Pixel-perfect replay captures all screen content including PII in forms and API responses
Identity stitching
Impact: Session stitching across domains and applications creates comprehensive user journey capture
Device identification
Impact: Device fingerprinting persists session identity across cookie deletion and privacy modes
Long-lived identifiers
Impact: Redux state and local storage capture enables session reconstruction months later
Container/loader (neutral)
Impact: Dynamic instrumentation adapts capture to application changes without redeployment
IOC Manifest
Indicators of compromise across 5 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
206 detection signatures across scripts, domains, cookies, and network endpoints