How This Briefing Works
This dossier opens with key findings, then maps the gap between what Mailchimp discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection evidence underneath. BLACKOUT observes runtime browser behavior and cites the regulations that address each pattern — legal determinations are your counsel's call.
At a Glance
across 2 sites
vendor fires before consent
1 HIGH
Briefing
Mailchimp, owned by Intuit since 2021, is widely deployed as an email marketing and automation platform. BLACKOUT runtime analysis across 2 sites reveals 9 distinct BTI behavioral codes — including session recording (C07), identity resolution (C14), cross-domain sync (C08), consent bypass (C09), and persistence mechanisms (C13). With a 50% pre-consent firing rate, Mailchimp's on-site JavaScript executes a comprehensive surveillance capability that goes far beyond email list management. The combination of behavioral biometrics, fingerprinting, and identity resolution transforms embedded Mailchimp components into a full visitor tracking infrastructure operating under the cover of 'email signup forms.'
What This Means For You
If Mailchimp is deployed on your site — even as a simple email signup form — your visitors are exposed to 9 distinct behavioral tracking codes. Your privacy notice likely describes Mailchimp as an email marketing processor, but runtime analysis reveals session recording, fingerprinting, and identity resolution capabilities that constitute a fundamentally different processing activity. Under GDPR, each undisclosed processing purpose is a separate transparency violation. The Intuit ownership means your visitor data enters a financial data conglomerate's ecosystem — a data controller relationship that almost certainly is not reflected in your DPIA or Records of Processing Activities. Half your visitors encounter this tracking before consent, creating systematic legal exposure.
Risk Channel Breakdown
Signal corruption score of 40 reflects Mailchimp's distortion of your measurement environment. When email signup forms deploy session recording, behavioral biometrics, and fingerprinting, the data flowing to Intuit's infrastructure extends far beyond what your analytics dashboards reveal.
CAC subsidization scores 100. Mailchimp's cross-domain sync (C08) and identity resolution (C14) mean visitor identity and behavioral data captured on your site flows into Intuit's broader data ecosystem. Your site visitors become data points in Intuit's advertising and financial data intelligence network.
Expands attack surface
Legal tail risk scores 100. Mailchimp components fire pre-consent 50% of the time while deploying 9 behavioral codes. Most organizations classify Mailchimp as an email processor in their Records of Processing Activities — the runtime reality of session recording, fingerprinting, and identity resolution is likely undisclosed in privacy notices and DPIAs.
Threat Indicators
Runtime-observed (BTI-C)
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Full session replay
Identity stitching
Ignoring CMP signals
Device identification
Long-lived identifiers
PII deanonymization
Container/loader (neutral)
Per-code narrative explanations of what each detected behavior means for your organization
Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →
Claims vs. Reality
BLACKOUT analyzed Mailchimp's public claims against observed runtime behavior and identified 1 contradiction.
Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →
What To Do
4 for current users · 4 for evaluators
contractual leverage points
Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →
Supply Chain & Pairings
Claims 0, observed 2
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →