How This Briefing Works
This report opens with key findings, then maps the gaps between what Intentdata 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
Intentdata was observed loading and executing before user consent was obtained on 6% of sites where it was detected.
Subprocessor Disclosure
Observed DoubleClick, Google Ads, GA4, HubSpot, Meta Pixel on site
Service Scope Mismatch
Marketing promotes contact-level identity resolution with PII (name, email, phone)
Undisclosed Party
Not in privacy policy
Undisclosed Sharing
Hidden data recipients
Claims vs. Observed Behavior
Subprocessor Disclosure
“Privacy policy mentions Contractors but provides no list”
Observed DoubleClick, Google Ads, GA4, HubSpot, Meta Pixel on site
Runtime scan of intentdata.io
Service Scope Mismatch
“Privacy describes web tracking and analytics”
Marketing promotes contact-level identity resolution with PII (name, email, phone)
Homepage: Contact-Level Intent Data identifies the actual person
Pre-Consent Tracking
“Claims to honor Do Not Track signals”
5.9% pre-consent tracking rate observed
Detection data from intel_detections
CCPA Opt-Out Link Broken
“Links to CCPA opt-out page in privacy policy”
https://www.intentdata.io/ccpa returns 404
Direct navigation test 2026-01-23
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Intentdata
- →Audit consent flow for contact-level data — ensure prospects consented to identity collection, not just aggregate analytics
- →Review data provenance — ask IntentData for documented consent chain for every contact they provide
- →Update your privacy policy to disclose IntentData as a source of contact-level personal data under GDPR Art 14
- →Consider GDPR Art 14 obligations — you must inform data subjects within one month when personal data is obtained from third parties
- →Assess whether competitors subscribe to the same IntentData topic categories targeting your prospect accounts
If You're Evaluating Intentdata
- →Request documented consent chain for contact-level data — person-level identification requires stronger legal basis than aggregate intent
- →Ask specifically how individual contacts are identified and whether consent is obtained at the contact level
- →Review data exclusivity terms — your prospect intent signals may be sold to competitors on the same platform
- →Compare against aggregate-only intent providers (Bombora) if contact-level identification creates excessive compliance burden
- →Negotiate data isolation ensuring your research signals do not inform competitor targeting through shared topic subscriptions
Negotiation Leverage
- →Consent provenance: IntentData provides contact-level identification. Require documented consent chain for all contacts provided, demonstrating valid legal basis under GDPR Art 6 for person-level tracking.
- →Data exclusivity: IntentData sells intent signals to multiple subscribers. Require contractual right to know if competitors subscribe to the same topic categories targeting your prospect accounts.
- →Subprocessor disclosure: Zero vendors named in privacy policy. Require complete enumeration of all data collection partners and processing infrastructure.
- →GDPR Art 14 compliance: Require IntentData to provide documentation sufficient for your Art 14 notifications to data subjects about third-party 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
Identity stitching
Ignoring CMP signals
Device identification
PII deanonymization
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
101 detection signatures across scripts, domains, cookies, and network endpoints
