How This Briefing Works
This report opens with key findings, then maps the gaps between what Typeform 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
Pre-Consent Activity
Typeform was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Requires claims extraction via CDT”
Defeat device, behavioral biometrics, consent bypass, and fingerprinting detected in runtime
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Typeform
- →Audit defeat device deployment within embedded form infrastructure
- →Review behavioral biometrics scope in form interaction monitoring
- →Require consent collection before Typeform tracking initialization
- →Verify fingerprinting boundaries for form submission workflows
If You're Evaluating Typeform
- →Native form builders preventing third-party behavioral monitoring
- →Self-hosted survey solutions eliminating competitive intelligence leakage
- →Privacy-respecting form platforms without embedded persistent tracking
Negotiation Leverage
- →Challenge defeat device mechanisms within data collection infrastructure
- →Require disclosure of all behavioral monitoring through embedded forms
- →Demand opt-out from cross-customer form engagement analysis
- →Request data processing agreement amendments addressing vendor tracking through form platform
- →Negotiate liability protection for consent violations by data collection 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
Impact: Detection evasion mechanisms obscure tracking deployment within conversational form interfaces.
Keystroke/mouse tracking
Impact: Keystroke dynamics and interaction timing captured as visitors complete form fields and navigate conversational workflows.
Ignoring CMP signals
Impact: Tracking mechanisms active within form experience before visitor consent collection completes.
Device identification
Impact: Browser and device characteristics harvested through embedded form infrastructure.
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
30 detection signatures across scripts, domains, cookies, and network endpoints