How This Briefing Works
This report opens with key findings, then maps the gaps between what Elevenlabs 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
Elevenlabs was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Unknown - requires claims extraction via CDT”
Runtime evidence shows C09 pattern
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Elevenlabs
- →Confirm consent before Elevenlabs script loads
- →Review DPA: is user input data used for model training?
- →Audit what audio interaction data is collected
If You're Evaluating Elevenlabs
- →Test: does Elevenlabs load before consent banner?
- →Ask: is voice synthesis input used for AI training?
- →Verify privacy policy discloses audio data collection
Negotiation Leverage
- →C09 consent bypass observed. How do you ensure consent before audio tracking?
- →Is user text-to-speech input used for model training? This requires explicit disclosure.
- →Embedded AI creates processor relationship. Do you have GDPR Article 28 DPA in place?
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.
Ignoring CMP signals
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
No indicators in this category
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
5 detection signatures across scripts, domains, cookies, and network endpoints