The policy prohibits using ElevenLabs tools to replicate the voice of a real, identifiable person without that person's consent, and prohibits generating audio that places false statements in a real person's voice.
This analysis describes what ElevenLabs's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes a consent requirement for voice cloning that interacts directly with biometric privacy statutes in multiple US states and with GDPR consent and data processing obligations in the EU; enterprise users building products on top of the ElevenLabs API must assess whether their own consent collection mechanisms satisfy both ElevenLabs' policy requirements and applicable law.
Interpretive note: The policy does not specify the form or documentation standard required for valid consent, creating ambiguity for enterprise users seeking to operationalize this requirement across jurisdictions with differing statutory consent standards.
The provision was streamlined to remove distinction between public and private figures, simplified language from 'explicit prior consent' to 'consent', and added explicit prohibition on false attribution statements.
View full change record →Under this provision, users may not generate voice content of identifiable individuals without documented consent, and users who do so may be subject to account termination; individual creators and developers integrating the API are responsible for obtaining and retaining consent documentation in accordance with applicable legal standards in their jurisdiction.
How other platforms handle this
You may not display any personal contact, banking, or peer-to-peer payment information, whether in relation to you or any other person (for example, names, home addresses or postcodes, telephone numbers, email addresses, URLs, credit/debit card...)
Bypass or ignore instructions contained in our robots.txt file that controls automated access to portions of our Services;
Send content created in Mailchimp through another service.
"You may not use ElevenLabs to clone the voice of an identifiable individual without their consent, or to generate content that falsely represents a real person as saying something they did not say.Excerpt from ElevenLabs's Usage Policy
(1) REGULATORY LANDSCAPE: This provision engages Illinois BIPA, Texas CUBI, and Washington's My Health My Data Act where voice prints may constitute biometric identifiers requiring informed written consent prior to collection and use.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Search "[your state] attorney general consumer complaint" to find your state's direct complaint form
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision establishes a consent requirement for voice cloning that interacts directly with biometric privacy statutes in multiple US states and with GDPR consent and data processing obligations in the EU; enterprise users building products on top of the ElevenLabs API must assess whether their own consent collection mechanisms satisfy both ElevenLabs' policy requirements and applicable law.
Under this provision, users may not generate voice content of identifiable individuals without documented consent, and users who do so may be subject to account termination; individual creators and developers integrating the API are responsible for obtaining and retaining consent documentation in accordance with applicable legal standards in their jurisdiction.
ConductAtlas has identified this type of provision across 282 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by ElevenLabs.