How This Briefing Works
This report opens with key findings, then maps the gaps between what [24]7.ai 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
consent_gap
Pre-consent tracking observed for 247.ai's own code, Apollo.io, GoogleAnalytics4, TrustArc itself, and Verisoul
subprocessor_gap
30+ third-party vendors observed including Apollo.io, ZoomInfo, HubSpot, Factors.ai, Verisoul, HGInsights
Pre-Consent Activity
[24]7.ai was observed loading and executing before user consent was obtained on 2% of sites where it was detected.
claims_gap
Uses Apollo.io and ZoomInfo as subprocessors - both are known hostile de-anonymization services
consent_gap
TrustArc itself fires pre-consent (pre_consent=true in detections)
Claims vs. Observed Behavior
consent_gap
“Cookie consent banner deployed via TrustArc requiring user consent”
Pre-consent tracking observed for 247.ai's own code, Apollo.io, GoogleAnalytics4, TrustArc itself, and Verisoul
intel_detections shows pre_consent=true for multiple vendors on 247.ai scans
subprocessor_gap
“Privacy policy mentions 'service providers' and 'data aggregators' generically with no names”
30+ third-party vendors observed including Apollo.io, ZoomInfo, HubSpot, Factors.ai, Verisoul, HGInsights
Network requests captured in scan showing 31 distinct vendor domains
claims_gap
“SOC 2 Type II and ISO 27001:2013 certified, verified by independent auditors”
Uses Apollo.io and ZoomInfo as subprocessors - both are known hostile de-anonymization services
Trust Center claims certification while runtime shows data flows to identity resolution vendors
consent_gap
“TrustArc CMP deployed to manage consent”
TrustArc itself fires pre-consent (pre_consent=true in detections)
TrustArc detected with pre_consent=true, defeating the purpose of the CMP
disclosure_gap
“No mention of Global Privacy Control in privacy policy”
GPC is a legal requirement in California and increasingly elsewhere
Full text search of privacy policy shows no GPC mention
disclosure_gap
“Privacy policy silent on device fingerprinting”
No disclosure of fingerprinting practices one way or another
Privacy policy does not address fingerprinting despite extensive tracking
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use [24]7.ai
- →Request complete subprocessor list immediately — their privacy policy names zero vendors while 30+ are detected at runtime
- →Audit data flows to verify what data reaches Apollo.io and ZoomInfo through your [24]7.ai deployment
- →Review your DPA to ensure undisclosed vendor relationships are covered by contractual protections
- →Test consent implementation — verify [24]7.ai scripts respect your CMP signals given their own TrustArc fires pre-consent
- →Document risk acceptance if continuing use — their pre-consent behavior and undisclosed vendors create shared liability
If You're Evaluating [24]7.ai
- →Demand named subprocessor list before procurement — zero vendor disclosure is a critical transparency failure
- →Require contractual mandate for consent-gated loading — their own site contradicts compliance claims
- →Ask specifically about Apollo.io and ZoomInfo relationships and whether identity resolution data flows affect your customer data
- →Verify SOC 2 and ISO 27001 certification scope covers your specific deployment use case
- →Consider CX alternatives with transparent data practices and published subprocessor lists
Negotiation Leverage
- →Subprocessor list requirement: [24]7.ai's privacy policy names zero subprocessors while 30+ vendors are detected at runtime. Require complete named subprocessor list as a contract precondition — this is a baseline GDPR Art 28 requirement.
- →Identity resolution disclosure: Apollo.io and ZoomInfo on their site perform visitor deanonymization. Require written confirmation of whether these services process data from your customer interactions.
- →CMP remediation: Their TrustArc consent banner fires before consent. Require contractual guarantee that any scripts deployed in your customer experience environment respect your CMP signals with zero pre-consent activity.
- →Security certification scope: Request SOC 2 and ISO 27001 reports and verify scope covers customer-facing deployments, not just internal infrastructure.
- →Data flow audit rights: Require quarterly right to audit network requests from [24]7.ai solutions deployed in your environment to verify no undisclosed third-party data flows.
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
IOC Manifest
Indicators of compromise across 3 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
210 detection signatures across scripts, domains, cookies, and network endpoints