How This Briefing Works
This report opens with key findings, then maps the gaps between what Rubicon Project 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
Rubicon Project was observed loading and executing before user consent was obtained on 22% of sites where it was detected.
Transparency
13+ third-party vendors detected on their own website firing pre-consent
Undisclosed Party
Not in privacy policy
Undisclosed Sharing
Hidden data recipients
Compliance Claim Mismatch
False certification claims
Claims vs. Observed Behavior
Transparency
“No specific subprocessor list provided”
13+ third-party vendors detected on their own website firing pre-consent
Runtime scan of magnite.com shows Demandbase, Hotjar, LinkedIn, Marketo, TrenDemon, and others
Consent
“Claims GPC and opt-out support”
21.7% pre-consent tracking rate across detected sites
intel_detections query shows pre_consent=true for 21.7% of Rubicon detections
Data Selling
“Openly discloses data selling”
Sells user data for targeted advertising
Privacy policy states: selling or processing of User Information for purposes of targeted advertising
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Rubicon Project
- →Audit your consent implementation to ensure Rubicon/Magnite pixels fire only after consent — 21.7% pre-consent rate across the industry
- →Review data processing agreements for explicit subprocessor enumeration — Magnite publishes no subprocessor list
- →Implement server-side integration where possible to control data exposure through the bid stream
- →Monitor bid stream for unauthorized data collection that could leak your audience intelligence to competitors
- →Update your privacy policy to disclose Magnite's data selling practices if using their programmatic services
If You're Evaluating Rubicon Project
- →Request complete subprocessor list and DPA before integration — the absence of a published list is a transparency gap
- →Verify consent flow compatibility with your CMP and test that Magnite honors GPC opt-out signals
- →Assess if 90-day data retention aligns with your data minimization requirements under GDPR Art 5(1)(e)
- →Consider their open data selling disclosure implications for your organization's privacy posture
- →Compare pre-consent compliance against alternative SSPs for reduced consent architecture risk
Negotiation Leverage
- →Subprocessor list requirement: Magnite provides no subprocessor list while 13+ vendors fire pre-consent on their site. Require complete enumeration of all data processing partners as a baseline contract condition.
- →Pre-consent SLA: 21.7% pre-consent rate. Require contractual guarantee that Magnite pixels fire only after consent on your property with GPC signal compliance verification.
- →Data sale transparency: Magnite openly discloses data selling. Require contractual specification of exactly what data categories from your property are sold and to which recipients, with right to opt out of specific data partnerships.
- →Bid stream protection: As a major SSP, bid stream data contains valuable audience intelligence. Require contractual protections against unauthorized data collection from bid requests originating from your inventory.
- →Retention limitation: Magnite claims 90-day retention. Require contractual commitment with audit verification that data from your property is deleted within the stated retention period.
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
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
148 detection signatures across scripts, domains, cookies, and network endpoints