How This Briefing Works
This report opens with key findings, then maps the gaps between what Reachinbox 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
Reachinbox was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
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 Reachinbox
- →Require data processing addendum with explicit cold email tracking disclosure
- →Demand consent framework for website tracking separate from email subscription
- →Implement session recording exclusions for sensitive website interactions
- →Configure analytics to minimize exposure of outreach strategy in campaign data
- →Establish retention limits for prospect behavioral profiles
If You're Evaluating Reachinbox
- →Review legal basis for tracking cold email recipients under GDPR (likely lacks legitimate interest)
- →Verify whether prospect behavior data influences vendor product development or benchmarking
- →Test session recording scope to understand what website activity gets captured from email clicks
- →Assess data flows to third-party enrichment and analytics platforms
- →Request disclosure of secondary use of campaign data for vendor intelligence
Negotiation Leverage
- →Reachinbox deploys session recording on cold email recipients without prior consent—demand legal assessment of GDPR compliance and explicit DPA liability protection
- →Cold outreach tracking creates heightened regulatory scrutiny under GDPR legitimate interest requirements—require technical controls that separate email engagement from website behavioral tracking
- →Session recordings capture prospect research behavior that reveals your sales process—negotiate recording scope limits and data retention boundaries
- →Campaign analytics may distort lead quality assessment and pipeline forecasting—establish baseline measurement methodology for email effectiveness
- →Legal tail risk of 100% reflects consent bypass in cold outreach context—evaluate whether engagement tracking value justifies regulatory exposure or consider privacy-respecting email analytics
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: Reachinbox can detect email security tools and alter tracking behavior during privacy assessments, masking production data collection scope.
Keystroke/mouse tracking
Impact: Email interaction patterns and website visit behavior create prospect profiles for outreach sequence optimization.
Full session replay
Impact: Session capture records prospect website behavior after email link clicks for engagement analysis.
Ignoring CMP signals
Impact: Tracking initializes when cold email recipients click links, processing behavior without prior consent relationship.
Device identification
Impact: Device and browser fingerprinting creates persistent identifiers linking email recipients to website visitors.
IOC Manifest
Indicators of compromise across 4 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
124 detection signatures across scripts, domains, cookies, and network endpoints