How This Briefing Works
This report opens with key findings, then maps the gaps between what ChiliPiper B2B Email Intelligence 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
Runtime scan detected 48 third-party vendors loading on chilipiper.com
Pre-Consent Activity
ChiliPiper B2B Email Intelligence was observed loading and executing before user consent was obtained on 4% of sites where it was detected.
Pre-Consent Tracking
19 vendors fire before consent is obtained (4.5% pre-consent rate)
Undisclosed Party
Not in privacy policy
Undisclosed Sharing
Hidden data recipients
Claims vs. Observed Behavior
Subprocessor Disclosure
“Trust center lists 2 subprocessors: AWS and Google Cloud Platform”
Runtime scan detected 48 third-party vendors loading on chilipiper.com
BLACKOUT scan 2026-01-23 detected Clarity, HubSpot, MetaPixel, GoogleAds, ZoomInfo, RB2B, LinkedIn, and 40+ others
Pre-Consent Tracking
“GDPR and CCPA compliance claimed on trust center”
19 vendors fire before consent is obtained (4.5% pre-consent rate)
Pre-consent vendors include: Bitly, Clarity, DoubleClick, G2, GoogleAds, GoogleAnalytics4, HubSpot, MetaPixel, LinkedIn, TwitterPixel
Identity Resolution Undisclosed
“No disclosure of identity resolution/deanonymization capabilities”
RB2B, ZoomInfo, LeadRocket, and other identity resolution vendors detected
These vendors specialize in identifying anonymous website visitors and linking to contact databases
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use ChiliPiper B2B Email Intelligence
- →Audit the vendors ChiliPiper loads on YOUR site — their 48-vendor footprint may indicate what loads in their embeds
- →Review your consent mechanism — ensure ChiliPiper components respect your CMP before loading third-party scripts
- →Update your subprocessor documentation — citing only AWS and GCP dramatically understates actual vendor relationships
- →Request data flow documentation for your meeting and routing data through ChiliPiper's vendor ecosystem
If You're Evaluating ChiliPiper B2B Email Intelligence
- →Request complete subprocessor list — the 2-vendor trust center listing is not credible given 48 detected vendors
- →Test ChiliPiper embeds in a staging environment and audit all network requests
- →Compare with Calendly and other scheduling tools on vendor disclosure transparency
- →Require contractual restrictions on identity resolution and competitive intelligence derived from your booking data
Negotiation Leverage
- →Subprocessor disclosure gap: 48 vendors detected vs. 2 disclosed (AWS, Google Cloud) — a 24x undercount that undermines trust center credibility; require complete disclosure as a contract condition
- →Identity resolution vendors: RB2B, ZoomInfo, and LeadRocket detected on chilipiper.com — use this to negotiate restrictions on visitor identification within your ChiliPiper implementation
- →Pre-consent rate: 4.5% pre-consent rate detected — while lower than many vendors, verify this behavior does not extend to ChiliPiper embeds on your properties
- →Meeting data sensitivity: Scheduling and routing data reveals sales pipeline intelligence — negotiate data usage restrictions preventing competitive insights from your booking patterns
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.
Keystroke/mouse tracking
Identity stitching
Ignoring CMP signals
PII deanonymization
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 4 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
39 detection signatures across scripts, domains, cookies, and network endpoints