How This Briefing Works
This report opens with key findings, then maps the gaps between what Clay 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
Undisclosed Data Recipients
44+ third-party vendors detected on clay.com, including 15+ advertising/tracking vendors completely absent from disclosures
Pre-Consent Activity
Clay was observed loading and executing before user consent was obtained on 30% of sites where it was detected.
Pre-Consent Tracking
28.2% of detected vendor loads occur before consent, including 13 vendors loading pre-consent
Data Broker Disclosure
Data broker status combined with 150+ enrichment providers creates significant secondary use risk for individuals whose data flows through Clay
Undisclosed Party
Not in privacy policy
Claims vs. Observed Behavior
Undisclosed Data Recipients
“Subprocessor list at trust.clay.com discloses 34 vendors”
44+ third-party vendors detected on clay.com, including 15+ advertising/tracking vendors completely absent from disclosures
Runtime scan detected Meta Pixel, DoubleClick, Google Ads, LinkedIn, RB2B, Amazon Advertising, Adform, Jivox, Sojern, Peer39, HockeyStack, TrenDemon, Dreamdata, Factors.ai - none appear in subprocessor list
Pre-Consent Tracking
“GDPR/CCPA compliant per trust center”
28.2% of detected vendor loads occur before consent, including 13 vendors loading pre-consent
Pre-consent vendors: Amazon Advertising, DoubleClick, Google Ads, GA4, LinkedIn, Loom, Mapbox, Meta Pixel, Segment, Amazon Sell, Sequel, Typeform, Verisoul
Data Broker Disclosure
“Clay is transparent about being a data broker (Section 13 of privacy policy)”
Data broker status combined with 150+ enrichment providers creates significant secondary use risk for individuals whose data flows through Clay
Privacy policy Section 13: Yes. Clay is a data broker and complies with the state law obligations that apply to data brokers
DNT/GPC Non-Compliance
“Privacy policy Section 10 states no DNT/GPC support”
Clay explicitly does not honor Do-Not-Track or Global Privacy Control signals
Section 10: we do not currently respond to DNT browser signals or any other mechanism that automatically communicates your choice not to be tracked online
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Clay
- →Audit what data you send to Clay and ensure you have proper consent basis for each enrichment type
- →Review Clay's data broker registration status in all jurisdictions where you operate
- →Negotiate data usage restrictions to prevent your enrichment queries from informing competitor targeting
- →Request Clay's complete subprocessor list and compare against the 34 disclosed at trust.clay.com
If You're Evaluating Clay
- →Understand that Clay is a self-admitted data broker — assess whether your compliance framework accommodates data broker relationships
- →Compare Clay's subprocessor disclosure against runtime vendor detection before signing
- →Request contractual guarantees on query confidentiality and data usage restrictions
- →Evaluate whether server-side enrichment alternatives reduce your regulatory exposure compared to Clay's approach
Negotiation Leverage
- →Data broker disclosure: Clay self-identifies as a data broker — use this to require CCPA data broker registration verification and negotiate enhanced data deletion rights
- →Subprocessor undercount: 44+ vendors detected vs. 34 disclosed at trust.clay.com — leverage this gap to negotiate contractual indemnification for regulatory exposure
- →Competitive intelligence risk: Every enrichment query reveals your ICP to Clay's platform serving competitors — negotiate data usage restrictions and query confidentiality guarantees
- →Advertising vendor exposure: 15+ undisclosed advertising/tracking vendors on clay.com — use this to negotiate restrictions on how your enrichment data feeds advertising systems
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
Identity stitching
Ignoring CMP signals
Device identification
IOC Manifest
Indicators of compromise across 5 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
24 detection signatures across scripts, domains, cookies, and network endpoints
