How This Briefing Works
This report opens with key findings, then maps the gaps between what FullStory 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
22+ third-party vendors detected on fullstory.com operating pre-consent including 6sense, Demandbase, Criteo, Qualified, Contactout, G2, LinkedIn, Google Ads
Pre-Consent Activity
FullStory was observed loading and executing before user consent was obtained on 60% of sites where it was detected.
Pre-Consent Tracking
55.6% pre-consent tracking rate across sites using FullStory. Identity resolution and advertising vendors load before consent on their own website.
Undisclosed Sharing
Hidden data recipients
Compliance Claim Mismatch
False certification claims
Claims vs. Observed Behavior
Subprocessor Disclosure
“Subprocessor list discloses 6 vendors (Google, Fastly, Salesforce, Zendesk, Marketo, OpenAI)”
22+ third-party vendors detected on fullstory.com operating pre-consent including 6sense, Demandbase, Criteo, Qualified, Contactout, G2, LinkedIn, Google Ads
BLACKOUT runtime scan 2026-01-23
Pre-Consent Tracking
“GDPR and CCPA compliant as certified via trust center”
55.6% pre-consent tracking rate across sites using FullStory. Identity resolution and advertising vendors load before consent on their own website.
intel_detections pre_consent_pct = 55.6%
Data Sale Disclosure
“We do not sell the data of our Customers or their Users collected through the Services”
Privacy policy CCPA section states: Certain information of Visitors may be sold or shared, including to advertising and marketing partners
Privacy policy CCPA disclosure section
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use FullStory
- →Audit your consent flow to ensure FullStory script loads only after consent — 55.6% pre-consent rate indicates most deployments are non-compliant
- →Review the subprocessor disclosure gap — 14+ undisclosed vendors may require updates to your GDPR Art 30 records and privacy policy
- →Verify your privacy policy accurately reflects FullStory's session recording scope including form inputs, clicks, and page content
- →Implement data masking and exclusion rules given the sensitivity of session replay data capturing user interactions
- →Monitor for identity resolution vendors loading alongside FullStory on your property
If You're Evaluating FullStory
- →Request updated subprocessor list and compare against the 22+ vendors detected at runtime on fullstory.com
- →Verify consent-mode integration documentation and test in your environment before deployment
- →Assess the risk of identity resolution vendors (6sense, Demandbase, Qualified) on their corporate site extending to customer deployments
- →Request SOC2 and ISO 27701 reports and verify scope covers client-side session recording behavior
- →Compare FullStory's compliance posture against alternatives like PostHog (self-hosted) for session replay with full data control
Negotiation Leverage
- →Subprocessor transparency: 6 disclosed versus 22+ detected including identity resolution (6sense, Demandbase, Qualified) and advertising (Criteo, LinkedIn, Google Ads). Require complete enumeration of all third-party vendors, with 30-day advance notice before additions.
- →Pre-consent SLA: 55.6% pre-consent rate. Require contractual guarantee that FullStory script loads only after consent on your property with documented consent-mode integration.
- →Session data scope: Session replays capture detailed user interactions. Require contractual specification of exactly what data is recorded with mandatory PII masking verification before deployment.
- →Identity resolution isolation: 6sense, Demandbase, and Qualified on fullstory.com perform visitor deanonymization. Require contractual guarantee that no identity resolution capabilities are embedded in FullStory's JavaScript deployed on your property.
- →ISO 27701 scope verification: Request ISO 27701 privacy certification and verify scope covers session recording and client-side data collection, not just server infrastructure.
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
Ignoring CMP signals
Device identification
PII deanonymization
IOC Manifest
Indicators of compromise across 6 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
115 detection signatures across scripts, domains, cookies, and network endpoints