How This Briefing Works
This report opens with key findings, then maps the gaps between what IDVisitors 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
IDVisitors was observed loading and executing before user consent was obtained on 60% of sites where it was detected.
Claims vs. Observed Behavior
consent
“Unknown - requires claims extraction via CDT”
Deploys identity resolution + pre-consent tracking for visitor deanonymization
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use IDVisitors
- →Disable IDVisitors tracking immediately - visitor identification without consent is indefensible
- →Request deletion of all historical visitor identification data
- →Audit current data: assess whether sensitive personal data (names, emails, companies) was processed
If You're Evaluating IDVisitors
- →Reject any deanon vendor with pre-consent deployment
- →Require consent-first architecture or contractual liability assumption: vendor pays 100% of GDPR penalties
- →Migrate to privacy-safe alternatives: consented lead capture (forms), account-based advertising (no visitor tracking), or firmographic enrichment from consented sources
Negotiation Leverage
- →IDVisitors combines consent bypass with identity resolution, creating GDPR Article 6 + Article 7 dual liability
- →Visitor identification processes personal data (names, companies) without consent, transparent disclosure, or legitimate interest documentation
- →Vendor must eliminate pre-consent tracking AND obtain explicit consent for identity resolution, or assume 100% regulatory penalty liability
- →Deanonymization works with consent-first architecture - pre-consent deployment is vendor choice that transfers liability to customer
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
Ignoring CMP signals
Impact: Identity resolution tracking loads before consent opportunity, creating per-visitor GDPR Article 7 violation. Combined with personal data processing (names, companies, contact info), elevates to Article 6 unlawful processing liability.
Device identification
PII deanonymization
Impact: Device fingerprinting and cross-site tracking resolve anonymous visitors to named individuals/companies. Creates personal data processing without consent, transparent disclosure, or legitimate interest assessment required by GDPR Article 6.
Container/loader (neutral)
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
138 detection signatures across scripts, domains, cookies, and network endpoints