Voice cloning consent

Consent is required on every clone, and verification is replacing assertion as unverified cloning is retired.

Consent is required on every clone
Verified flow: the speaker reads a Speechify-issued phrase, the recording is matched against the voice sample, and it is retained as the consent record
The unverified consent-JSON flow is deprecated and being retired
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, and the platform is completing the move from asserted consent (a name and an email) to verified consent: the speaker reads a Speechify-issued phrase aloud, the recording is checked against that phrase and against the voice being cloned, and it is retained as the consent record for the voice. The last unverified integrations are deprecated and will be switched off.

On the verified flow, the create call requires a consent_challenge_id and a consent_recording. The challenge comes from POST /v1/voices/consent-challenges, which issues a single-use phrase for the speaker to read aloud; a create request without a verified recording does not produce a voice. The recording is also matched against the sample, so the person consenting has to be the person being cloned - permission relayed by someone else does not pass. This makes consent a precondition of cloning rather than a checkbox after the fact. The previous flow, a consent JSON string carrying a name and an email, is deprecated and will be switched off on a date announced ahead of time.

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 puts the speaker in front of a microphone as part of creation. See the ethics page for the wider principles and the voice cloning API for the field details.

FAQ

Frequently asked questions

Is consent required to clone a voice?

Yes, always. Creating a voice on the Speechify Build API requires a consent record. On the verified flow the speaker reads a phrase Speechify issues, and the recording is checked against that phrase, matched against the voice sample being cloned, and retained. The remaining unverified integrations, which assert consent as a name and email, are deprecated and will be switched off on a date announced ahead of time.

What does the consent record contain?

On the verified flow, a recording of the speaker reading a single-use phrase issued by the consent-challenge endpoint, plus the full name bound to that challenge. Speechify transcribes the recording, matches it against the issued phrase, matches the speaker against the voice sample being cloned, and retains it as evidence for the voice. Voices created on the outgoing flow carry an asserted name and email instead.

Who can use voice cloning?

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 voice_cloning_not_included.

fine-tuned voice cloning voice cloning languages voice cloning voice cloning ethics voice cloning ethics

Start building