How This Briefing Works
This report opens with key findings, then maps the gaps between what Snov 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
Disclosure Gap
57 vendors detected on site, 18+ completely undisclosed
Consent Violation
26 vendors load pre-consent including ad tech (Adroll, Basis, DoubleClick)
Pre-Consent Activity
Snov was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Data Sale Misrepresentation
Multiple ad tech vendors (Adroll, Basis, TrafficJunky, DoubleClick) loading pre-consent enables behavioral advertising data flows that may constitute sale under CCPA
Undisclosed Party
Not in privacy policy
Claims vs. Observed Behavior
Disclosure Gap
“Privacy policy lists ~25 subprocessors”
57 vendors detected on site, 18+ completely undisclosed
Runtime scan vs privacy policy comparison
Consent Violation
“GDPR and CCPA compliant”
26 vendors load pre-consent including ad tech (Adroll, Basis, DoubleClick)
100% pre-consent rate in intel_detections for snov.io hostname
Data Sale Misrepresentation
“We DO NOT sell your data”
Multiple ad tech vendors (Adroll, Basis, TrafficJunky, DoubleClick) loading pre-consent enables behavioral advertising data flows that may constitute sale under CCPA
Ad tech vendors detected in runtime scan
Scraping Infrastructure
“Security-focused organization”
Brightdata, Zenrows, Scrapemagic scraping infrastructure vendors present on site
Runtime detection of scraping vendors
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Snov
- →Audit your privacy policy to ensure Snov.io and their undisclosed subprocessors are properly listed for GDPR Art 13 compliance
- →Review consent mechanisms for any Snov tracking deployed on prospect sites — 26 pre-consent vendors on their own site is a red flag
- →Request complete DPA and subprocessor list — compare against the 57 vendors detected at runtime to identify disclosure gaps
- →Assess data minimization — evaluate which Snov features actually require deployment versus what creates unnecessary data exposure
- →Document lawful basis for Snov's lead enrichment capabilities — legitimate interest claims may not cover the full scope of data processing
If You're Evaluating Snov
- →Request SOC2 report — Snov claims security focus but displays no certification, which is a critical gap for enterprise procurement
- →Conduct runtime audit of your test deployment to verify actual vendor footprint before production use
- →Compare their ~25 disclosed subprocessors against 57 detected vendors — the 18+ undisclosed gap is material
- →Assess whether competitors (Leadfeeder, Contactout, Dealfront) on snov.io create intelligence leakage risk for your prospect data
- →Evaluate alternatives with better compliance posture — note that most sales automation vendors have similar issues, so focus on subprocessor transparency
Negotiation Leverage
- →Subprocessor reconciliation: 57 vendors detected versus ~25 disclosed — 18+ completely undisclosed. Require complete enumeration of all third-party vendors and data recipients as a contract precondition.
- →Security certification requirement: No SOC2, ISO, or any security certification visible despite handling prospect contact data for 185,000+ companies. Require SOC2 Type II as a contract condition or negotiate significant liability indemnification.
- →Data arbitrage prohibition: Competitors Leadfeeder, Contactout, and Dealfront detected on snov.io suggest potential data flow overlap. Require contractual prohibition on sharing your prospect data with competing sales intelligence platforms.
- →BrightData relationship: BrightData (web scraping service) loads on snov.io. Require written explanation of this relationship and contractual guarantee that BrightData does not receive data from your account.
- →Pre-consent SLA: 26 vendors load before consent. Require contractual guarantee that Snov tracking deployed on prospect sites fires only after consent with zero pre-consent data collection.
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
Keystroke/mouse tracking
Full session replay
Ignoring CMP signals
Device identification
Long-lived identifiers
PII deanonymization
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
121 detection signatures across scripts, domains, cookies, and network endpoints