Voice Cloning Consent: Permission Checklist Fish Audio

Voice cloning consent is permission from the person whose voice is being reproduced—not permission to use the audio file. A recording may be owned by one party while the voice rights belong to another. The safe workflow records both, states the projects covered and gives the speaker a clear way to revoke future use.

What counts as valid consent?

Valid consent is informed, specific and recorded. The speaker should understand that a reusable synthetic model may generate lines they never recorded, and that the output may be published, localized or used in a commercial project.

A generic “I agree” buried in unrelated terms is weak evidence. A usable record names the voice, the project, the audience and the party who controls the clone.

What should a consent record contain?

Keep the record concise enough that it can actually be reviewed:

• Speaker’s full name and contact details.
• Date and identity of the person obtaining permission.
• The exact audio sample used for cloning.
• Project or campaign name and intended audience.
• Personal, commercial, client or resale permissions.
• Languages, territories and time period.
• Whether the output may be edited, dramatized or localized.
• Required synthetic-voice disclosure.
• Deletion, revocation and contact instructions.
• Signature or another verifiable approval.

Store the record with the voice profile and project files. If a client supplies a clone, require evidence that the client has authority to do so.

Who can authorize a clone?

The person whose voice is reproduced normally authorizes it. An employer, studio or client may control the recording, but that does not automatically grant the right to impersonate the speaker in new statements.

For a character voice, document both the performer’s permission and the rights holder’s permission when they are different. For a deceased person, estate or publicity rights may apply; do not treat a historical recording as free-to-clone material.

What uses should be prohibited?

Do not use a cloned voice to:

• Create statements the speaker never made.
• Suggest endorsement, employment or partnership without permission.
• Harass, defraud or impersonate someone.
• Bypass identity checks or access controls.
• Sexualize a real person or place them in a deceptive context.
• Reproduce a public figure for entertainment without the required rights.
• Ignore a platform’s synthetic-media and disclosure rules.

These restrictions apply even if the voice sample was technically available online. Availability is not consent.

How should public figures and minors be handled?

Public figures require a higher level of scrutiny because imitation can imply endorsement or create a false statement. Do not clone them for parody, commentary, advertising or satire unless the intended use is clearly lawful and separately reviewed.

For minors, require permission from a parent or legal guardian and use the narrowest possible scope. Avoid commercial and public distribution unless the rights and consent record explicitly cover it. Delete the voice profile when the project ends.

How do you document the cloning workflow?

Use a small record for each voice:

1. Verify the speaker’s identity.
2. Explain that a reusable synthetic voice will be created.
3. Agree on the projects and languages.
4. Capture the consent record.
5. Upload the authorized sample and create the voice.
6. Store the consent note with the profile and final media.
7. Review any output that could be mistaken for a real statement.

For the technical process, follow the Fish Audio voice cloning guide. For commercial projects, use the commercial use guide and the appropriate Creator or Studio pack.

What if a client supplies the voice?

Do not accept a client’s assurance as the complete permission record. Ask who the voice belongs to, which project it may be used for, and whether the client has the authority to grant that scope. Keep the client’s authorization separate from the speaker’s consent when they are different parties.

If the client cannot identify the speaker or produce permission, stop before cloning. A vendor relationship does not transfer a person’s voice identity, and an unclear chain of permission is difficult to repair after audio has been published.

How does revocation work?

The consent record should say who to contact and what happens next. After a valid withdrawal, stop creating new audio with the cloned voice, remove or disable the voice profile where the product allows it, and follow the agreed process for published media.

A revocation does not automatically erase every copy already published by third parties, which is why the original consent should define the project boundaries before distribution. Keep a record of the actions taken.

What should a team review before publishing?

Before a cloned voice appears publicly:

• Confirm the speaker identity and recorded permission.
• Check that the script stays within the allowed project.
• Apply the platform’s AI disclosure requirements.
• Review names, claims and endorsements for deception.
• Keep the consent record accessible to the publishing owner.
• Confirm that removal and contact instructions still work.

The site’s privacy policy and disclaimer describe the product context, but the operator remains responsible for the specific recording and release.

Frequently asked questions

Do I need consent to clone my own voice?

You can clone your own voice, but document the project and intended distribution if other people will use the result. Consent becomes essential whenever the voice belongs to someone else or the clone will represent them.

Can I clone a public figure or celebrity?

No. Public visibility is not permission. Do not create a clone of a public figure, streamer or actor to imply endorsement, create new statements or distribute impersonated content without explicit rights that cover the intended use.

What should a consent record include?

Record the speaker’s identity, the voice sample, the allowed projects, commercial or non-commercial use, geographic and time limits, disclosure requirements, revocation contact and the signature or verifiable approval.

Can consent be withdrawn later?

The agreement must say how future use stops and what happens to existing published media. Stop new generation promptly after a valid withdrawal and follow the agreed deletion or takedown process.

Is this page legal advice?

No. It is a practical product and safety checklist. Laws and platform rules vary by location and use case, so consult qualified counsel for a high-risk or commercial deployment.