All Vendors
platform

Slack

Collaboration platform with embedded tracking patterns that activate before consent collection completes.

49 IOCs74 detections100% pre-consent72 sites
70
Vendor Risk Score

How This Briefing Works

This report opens with key findings, then maps the gaps between what Slack 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

Key Findings

74 detections across 72 sites100% pre-consent activity
CRITICAL

Pre-Consent Activity

Slack was observed loading and executing before user consent was obtained on 100% of sites where it was detected.

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps

disclosure

HIGH
They Claim

“Pending claims extraction”

Observed Behavior

Runtime detection shows C06 (behavioral biometrics) and C09 (consent bypass) activation

Customer Impact

What This Means For You

Revenue teams using Slack for customer engagement (community channels, support widgets) face consent timing liability. Behavioral fingerprinting in embedded contexts creates persistence that complicates opt-out fulfillment. Cross-workspace data flows may expose competitive intelligence through shared channel analytics.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Slack

  • →Audit all customer-facing Slack deployments (widgets, embeds, public channels) for consent timing
  • →Implement consent-gated initialization for all Slack components on revenue properties
  • →Review Slack analytics access permissions to limit workspace-level intelligence exposure

If You're Evaluating Slack

  • →Document pre-consent activation windows in embedded Slack features
  • →Obtain written confirmation that behavioral biometrics are not used for cross-workspace profiling
  • →Request data flow diagram showing all data sharing between Slack workspaces and analytics partners

Negotiation Leverage

  • →Pre-consent activation: Embedded Slack components initialize before host site consent collection — vendor must provide mechanism to defer initialization until consent obtained.
  • →Behavioral biometrics: Interaction patterns within Slack widgets create persistent fingerprints — require confirmation these are not used for cross-workspace user identification.
  • →Cross-workspace intelligence: Shared channel analytics may expose competitive demand signals — negotiate restrictions on analytics derived from customer workspace activity.
Runtime Detections

Runtime Detections

2 BTI-C CODES

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.

BTI-C06Behavioral Biometrics

Keystroke/mouse tracking

BTI-C09Consent Bypass

Ignoring CMP signals

IOC Manifest

IOC Manifest

36 INDICATORS

Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.

No indicators in this category

Ecosystem

Ecosystem & Supply Chain

Slack appears in collaboration-heavy environments alongside project management platforms (Asana, Monday.com), developer tools (GitHub, GitLab), and customer support systems (Zendesk, Intercom). Common co-deployments include analytics platforms that track Slack widget engagement patterns.
Evidence

Evidence Artifacts

Artifacts collected during analysis, available with evidence-tier access.

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

49 detection signatures across scripts, domains, cookies, and network endpoints

Vendor Details