How This Briefing Works
This report opens with key findings, then maps the gaps between what Mutiny 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
Subprocessor Disclosure
39 vendors detected on mutinyhq.com including identity resolution, advertising, and session recording
Pre-Consent Activity
Mutiny was observed loading and executing before user consent was obtained on 67% of sites where it was detected.
Pre-Consent Tracking
66.7% of detected tracking loads before consent
Data Minimization
Identity resolution vendors perform PII enrichment
Undisclosed Party
Not in privacy policy
Claims vs. Observed Behavior
Subprocessor Disclosure
“6 infrastructure vendors listed in subprocessor disclosure”
39 vendors detected on mutinyhq.com including identity resolution, advertising, and session recording
Scan data shows 6sense, Clearbit, Hotjar, HubSpot, MetaPixel, GoogleAds, LinkedInAds, Segment, Vector and 30+ others not in subprocessor list
Pre-Consent Tracking
“GDPR and CCPA compliance”
66.7% of detected tracking loads before consent
28 of 39 vendors load with pre_consent=true on mutinyhq.com
Data Minimization
“De-identified and aggregated information”
Identity resolution vendors perform PII enrichment
6sense, Clearbit, IDVisitors, Vector all perform person/company identification from anonymous visitors
GPC/DNT
“Policy states they do NOT honor DNT signals”
Explicit non-compliance with browser privacy signals
Privacy policy quote: we do respond to or honor DNT signals
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Mutiny
- →Audit your privacy policy to disclose all 39+ vendors Mutiny loads — your current disclosure likely covers only 6 infrastructure providers
- →Implement consent gating before Mutiny script loads — 66.7% pre-consent rate on their own site indicates their code may not respect your CMP by default
- →Update your GDPR Article 30 records to include identity resolution vendors (6sense, Clearbit, IDVisitors, Vector) processing your visitor data
- →Consider the GDPR Art 28 liability of 30+ undisclosed data recipients processing data from your property
- →Monitor network requests from Mutiny's script on your site to verify no undisclosed identity resolution calls
If You're Evaluating Mutiny
- →Request SOC2 report — none found publicly, which is a significant gap for a vendor with access to your website and visitor data
- →Demand full vendor disclosure before contract — 39 detected versus 6 disclosed is one of the largest gaps we observe
- →Ask for reconciliation of 'de-identified and aggregated' data claims versus 4 identity resolution vendors performing individual identification
- →Negotiate contractual indemnification for the subprocessor disclosure gap and pre-consent tracking liability
- →Compare against alternatives with transparent subprocessor lists and demonstrable consent-first architecture
Negotiation Leverage
- →Subprocessor disclosure: 6 infrastructure vendors disclosed versus 39 detected including 4 identity resolution services. Require complete enumeration of all third-party vendors with 30-day advance notice before additions.
- →De-identification verification: Privacy policy claims 'de-identified and aggregated' data while deploying 6sense, Clearbit, IDVisitors, and Vector for individual identification. Require written reconciliation and contractual specification of what identification capabilities are active.
- →Pre-consent SLA: 66.7% pre-consent rate. Require contractual guarantee that Mutiny's personalization script loads only after consent on your property with zero pre-consent activity.
- →Security certification: No SOC2 found publicly. Require SOC2 Type II as a contract condition given Mutiny's access to your website visitor data and personalization logic.
- →Identity resolution scope: Require contractual limitation on what identification granularity Mutiny applies to your visitors — company-level versus individual-level — with right to audit.
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
PII deanonymization
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 6 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
99 detection signatures across scripts, domains, cookies, and network endpoints