How This Briefing Works
This report opens with key findings, then maps the gaps between what Apify 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
Transparency
26+ vendors detected at runtime
Pre-Consent Activity
Apify was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Data Processing
Leadfeeder, TrenDemon, G2 perform visitor identification
Consent
100% pre-consent tracking rate
Undisclosed Party
Not in privacy policy
Claims vs. Observed Behavior
Transparency
“Cookie policy discloses 7 vendors”
26+ vendors detected at runtime
Runtime scan of apify.com
Data Processing
“Aggregate data does not contain any personal data”
Leadfeeder, TrenDemon, G2 perform visitor identification
Detection of B2B identification scripts pre-consent
Consent
“GDPR compliant”
100% pre-consent tracking rate
All detected vendors fire before consent banner interaction
Documentation
“Subprocessors available at trust portal”
Full list requires NDA
GDPR info page states NDA required for sub-processor list
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Apify
- →Audit your own privacy policy for completeness — Apify's vendor sprawl may be inherited if you embed their tracking
- →Request their full subprocessor list to understand actual data flows beyond the 7 disclosed
- →Implement server-side integration to minimize client-side script exposure from Apify
- →Review data processing agreements to ensure your scraping data is not used for Apify's own intelligence
If You're Evaluating Apify
- →Request complete subprocessor list and compare against 26 detected vendors before signing
- →Test Apify in staging and audit all network requests to understand the full vendor ecosystem
- →Negotiate data isolation guarantees for your scraping targets and automation patterns
- →Require contractual representations on data confidentiality matching their maximum security claim
Negotiation Leverage
- →Vendor disclosure gap: 26 vendors detected vs. 7 disclosed — nearly 4x undercount; require complete vendor disclosure as a contract condition
- →B2B identification on site: Leadfeeder and TrenDemon actively identify corporate visitors — use this to negotiate removal of identification vendors or require consent-first architecture
- →Maximum security claim: Marketing claims maximum security and privacy while underdisclosing vendors — leverage for enhanced security audit rights and data protection guarantees
- →Scraping data sensitivity: Your scraping targets and patterns reveal competitive intelligence — negotiate data usage restrictions and payload confidentiality guarantees
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
Long-lived identifiers
Container/loader (neutral)
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
328 detection signatures across scripts, domains, cookies, and network endpoints