How This Briefing Works
This report opens with key findings, then maps the gaps between what RudderStack 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
RudderStack was observed loading and executing before user consent was obtained on 29% of sites where it was detected.
Undisclosed Sharing
Hidden data recipients
Marketing Mismatch
Behavior contradicts marketing
Compliance Claim Mismatch
False certification claims
Claims vs. Observed Behavior
Subprocessor Disclosure
“Subprocessor list available in DPA”
12+ marketing vendors (BingAds, DoubleClick, Clarity, Hotjar, etc.) active on website but not in public documentation
Runtime scan detected: Cloudflare Insights, Mapbox, Qualified (pre-consent); BingAds, Clarity, DoubleClick, GA4, GTM, Hotjar, HubSpot, LinkedInAds, Reddit
Privacy-First Marketing
“Privacy and Security focused Segment-alternative with privacy-first architecture”
28.6% pre-consent tracking including advertising network pixels
Own GitHub repo and marketing describe privacy focus; runtime shows ad trackers loading before consent
Consent Framework
“GDPR and CCPA compliant”
Pre-consent tracking present on own properties
28.6% pre-consent rate detected across scans
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use RudderStack
- →Audit your RudderStack consent integration — ensure events are blocked pre-consent for GDPR regions given their own 28.6% pre-consent rate
- →Review destinations receiving data and compare against your privacy policy disclosure obligations
- →Implement server-side tracking where possible to maximize the warehouse-native data control benefit
- →Request their full subprocessor list via DPA — 12+ vendors on their site are not in public documentation
- →Verify your implementation achieves the 'data never leaves your infrastructure' promise with network traffic monitoring
If You're Evaluating RudderStack
- →Note the gap between 'privacy and security focused' marketing and pre-consent advertising pixels on rudderstack.com
- →Request SOC2 Type II report and verify scope covers their SDK and data routing infrastructure
- →Verify that the warehouse-native architecture truly keeps data in your environment with no intermediate processing
- →Compare RudderStack's actual consent architecture against Segment — both have pre-consent issues on their own sites
- →Test consent-first SDK behavior in your environment before deployment to verify privacy claims
Negotiation Leverage
- →Privacy-first verification: RudderStack markets as the privacy-focused Segment alternative. Require documented evidence of how their SDK enforces consent-first data routing, given pre-consent advertising pixels on their own site.
- →Subprocessor reconciliation: 12+ marketing vendors on rudderstack.com not in public documentation. Require complete subprocessor list covering both infrastructure and marketing technology partners.
- →Warehouse-native guarantees: RudderStack's value proposition is that data stays in your warehouse. Require contractual guarantee with technical architecture documentation and right to audit data flows.
- →Pre-consent SLA: 28.6% pre-consent rate on their site. Require contractual guarantee that their SDK loads only after consent on your property.
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
Device identification
PII deanonymization
Container/loader (neutral)
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
176 detection signatures across scripts, domains, cookies, and network endpoints