How This Briefing Works
This report opens with key findings, then maps the gaps between what PartnerStack 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
PartnerStack was observed loading and executing before user consent was obtained on 71% of sites where it was detected.
Claims vs. Observed Behavior
disclosure
“Pending claims extraction”
Low Counselor score (40) indicates consent violations but minimal data commercialization. Privacy policy likely lacks specific disclosure of partner tracking scope.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use PartnerStack
- →Implement consent gate before PartnerStack tracking activates
- →Audit partner attribution accuracy impact from consent-gated deployment
- →Review Data Processing Agreement for partner data sharing and retention
- →Confirm privacy policy discloses partner referral tracking
If You're Evaluating PartnerStack
- →Defer PartnerStack scripts until post-consent confirmation
- →Assess server-side referral tracking alternatives to reduce client-side tracking exposure
- →Consider whether partner attribution can operate with reduced tracking coverage
- →Evaluate first-party referral parameter passing instead of third-party cookies
Negotiation Leverage
- →PartnerStack contract should address consent-gated deployment impact on attribution accuracy
- →Negotiate partner communication protocols for consent-related attribution gaps
- →Confirm PartnerStack supports first-party tracking modes that reduce consent friction
- →Request technical documentation on consent-aware attribution capabilities
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.
Ignoring CMP signals
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
6 detection signatures across scripts, domains, cookies, and network endpoints