QA mode · Tier:PUBLIC(override via ?tier=paid | premium)
← All Vendors
marketing_automation

Intercom

Intercom's "customer messaging" widget loads 25 scripts, fires before consent on 51% of observed deployments, and stitches user identity across customer sites — far exceeding what a chat tool requires.

38 IOCs observed88 detections66% pre-consent56 sites
85
Vendor Risk Score
Tier: HOSTILE
Observation Coverage

BLACKOUT observes runtime behavior in the browser. This dossier reflects browser-side execution, which is one of five vendor data-egress classes. Server-to-server transfers, backend integrations, and offline data flows are outside this observation boundary.

BLACKOUT observes runtime behavior and cites the regulations that address that behavior pattern. Legal determinations are the customer's counsel's call.

How This Briefing Works

This dossier opens with key findings, then maps the gap between what Intercom 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.

Key Findings

At a Glance

Detections
88

across 56 sites

Pre-Consent Rate
66%

vendor fires before consent

Disclosure Gaps
1

1 HIGH

Summary

Briefing

Intercom is a customer messaging platform offering live chat, email campaigns, and knowledge base tools. BLACKOUT detected it on 42 sites across 65 total observations, with a payload of 25 distinct scripts — extraordinarily heavy for a chat widget. With 7 BTI-C codes triggered including cross-domain sync (C08) and identity resolution (C14), Intercom is not merely facilitating customer conversations — it is building cross-site identity graphs from your visitors. The 51% pre-consent firing rate means the majority of observed Intercom deployments activate their full tracking suite before any consent mechanism engages.

Customer Impact

What This Means For You

If Intercom is on your site, you are loading 25 scripts for what most visitors perceive as a chat bubble. That payload performs cross-domain identity stitching, behavioral tracking, and device fingerprinting well beyond what customer messaging requires. Your visitors' chat conversations, browsing patterns, and device characteristics flow into Intercom's platform where they are merged into persistent identity profiles. The 51% pre-consent rate means your CMP is likely not controlling Intercom effectively — creating direct ePrivacy liability. Your privacy policy probably describes Intercom as a "customer support tool" while it operates as a cross-site identity resolution platform.

Collapse Engine

Risk Channel Breakdown

Oracle
Truth Collapse
40

Signal corruption score of 40 reflects Intercom's impact on measurement integrity. Its 25-script payload injects significant JavaScript execution that can interfere with page performance metrics, attribution models, and first-party analytics accuracy. What appears as engagement data may be Intercom's own instrumentation.

Broker
Control Collapse
100

CAC subsidization score of 100 — maximum severity. Intercom's cross-domain sync and identity resolution capabilities mean visitor data from your site feeds into Intercom's platform intelligence. With identity stitching across 42+ customer sites, Intercom accumulates behavioral profiles that inform its product recommendations and potentially its broader data partnerships.

Reaper
Safety Collapse
0

Expands attack surface

Counselor
Legitimacy Collapse
100

Legal tail risk score of 100 — maximum severity. 51% pre-consent firing rate with 25 scripts creates substantial ePrivacy exposure. Cross-domain identity stitching without explicit consent violates GDPR's purpose limitation principle. Intercom's identity resolution (C14) turns anonymous chat interactions into identifiable user profiles — a processing activity most privacy policies do not adequately disclose.

BTI Codes

Threat Indicators

Runtime-observed (BTI-C)

BTI-C01
Defeat Device

Evasion infrastructure, auditor bypass

BTI-C06
Behavioral Biometrics

Keystroke/mouse tracking

BTI-C07
Session Recording

Full session replay

BTI-C08
Cross-Domain Sync

Identity stitching

BTI-C09
Consent Bypass

Ignoring CMP signals

BTI-C10
Fingerprinting

Device identification

BTI-C13
Persistence Mechanisms

Long-lived identifiers

BTI-C14
Identity Resolution

PII deanonymization

7
BTI Consequences Identified

Per-code narrative explanations of what each detected behavior means for your organization

Available in VIDB Subscription

Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →

Disclosure Gaps

Claims vs. Reality

1
Gaps Observed
1 HIGH

BLACKOUT analyzed Intercom's public claims against observed runtime behavior and identified 1 contradiction.

Available in VIDB Subscription

Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →

Recommended Actions

What To Do

Recommended Actions
8

4 for current users · 4 for evaluators

Negotiation Leverage
5

contractual leverage points

Available in VIDB Subscription

Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →

Ecosystem

Supply Chain & Pairings

Commonly Paired With
10

googletagmanager, googleanalytics4, linkedinads

Available in VIDB Subscription

Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →

Profile: intercomFirst Seen: 2026-01-03Last Updated: 2026-05-30