How This Briefing Works
This report opens with key findings, then maps the gaps between what Lemlist 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
Lemlist was observed loading and executing before user consent was obtained on 50% of sites where it was detected.
Claims vs. Observed Behavior
marketing_surveillance
“Unknown - requires claims extraction”
C06+C07+C09+C13 detected - comprehensive marketing surveillance platform
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Lemlist
- →Audit Lemlist behavioral and recording scope - catalog surveillance capabilities deployed
- →Verify session recording extent on landing pages - full replay vs aggregated metrics
- →Enforce consent gate before Lemlist tracking initialization
- →Map persistence mechanisms - cookies, local storage, fingerprinting techniques
- →Document consent timestamp vs Lemlist execution for compliance records
If You're Evaluating Lemlist
- →Request Lemlist technical documentation of behavioral, recording, and persistence capabilities
- →Evaluate marketing automation platforms without session recording
- →Consider basic email tracking (opens/clicks) instead of comprehensive behavioral surveillance
- →Investigate consent-aware marketing automation alternatives
Negotiation Leverage
- →Lemlist deploys C06+C07+C09+C13 - vendor must explain comprehensive marketing surveillance
- →Demand complete disclosure of behavioral biometrics, session recording, and persistence mechanisms
- →Require consent-first operation - no pre-consent marketing tracking
- →Negotiate removal of session recording if not contractually specified
- →Establish liability terms for behavioral surveillance and consent violations
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
Long-lived identifiers
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
69 detection signatures across scripts, domains, cookies, and network endpoints