How This Briefing Works
This report opens with key findings, then maps the gaps between what Screenshotone 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
Pre-Consent Activity
Screenshotone was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
visual_surveillance
“Pending claims extraction”
Runtime shows visual capture active before consent with behavioral tracking
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Screenshotone
- →Audit screenshot trigger timing against consent framework
- →Map visual capture scope and content sensitivity
- →Document session recording integration with screenshot infrastructure
- →Verify DPA covers visual data capture and privacy requirements
If You're Evaluating Screenshotone
- →Require consent-first screenshot activation with visual capture disabled pre-consent
- →Demand disclosure of visual data retention and processing methodology
- →Negotiate liability provisions covering visual privacy violations
- →Evaluate screenshot alternatives with consent-aware triggering
Negotiation Leverage
- →C06+C07+C09 visual surveillance: Demand DPA rewrite requiring consent before ANY visual capture
- →Request written confirmation of consent-gated screenshot activation
- →Require audit rights covering visual data handling and retention
- →Negotiate data retention limits for screenshot and visual capture data
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.
Keystroke/mouse tracking
Full session replay
Ignoring CMP signals
IOC Manifest
Indicators of compromise across 3 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
77 detection signatures across scripts, domains, cookies, and network endpoints