voice cloning consent
Consent is required to create any cloned voice, with no exceptions.
- Consent is required on every clone
- Consent JSON must contain fullName and email
- No create path skips consent
- Cloning available on paid plans, not Free
definition
Consent and safety in voice cloning are enforced at the API, not left to policy. Creating a voice on the Speechify Build API requires a consent record containing the speaker’s full name and email. The requirement is structural: there is no create path that omits it, so every cloned voice is authorized by design.
consent-is-mandatory
The consent field on the create call is a JSON string that must contain fullName and email. It is required, so a create request without a valid consent record does not produce a voice. This makes consent a precondition of cloning rather than a checkbox after the fact.
access-control
Cloning is available on the paid plans, Starter, Pro, Scale, and Enterprise, and is not included on Free. A Free-tier attempt returns a 402 with the code voice_cloning_not_included, so the capability is gated to accounts that have it.
in-practice
Whether you clone your own voice, an author’s, or a performer’s, the flow captures consent as part of creation. See the ethics page for the wider principles and the voice cloning API for the field details.
Frequently asked questions
Is consent required to clone a voice?
What does the consent record contain?
Who can use voice cloning?
Start building
Consent is required to create any cloned voice, with no exceptions.