EchoVox

Voice cloning starts with permission, not a sample

A clean recording proves that a model can learn a voice. It does not prove that the speaker agreed to every script, language, channel, audience, or future use.

Use this checklist before creating or using a cloned voice in EchoVox or any other production tool.

Verify the speaker and the request

Confirm who owns or controls the voice and who is asking for the clone. A public video, podcast, meeting recording, voicemail, or social post is not automatic permission to build a synthetic voice. For an employee, contractor, actor, customer, or family member, obtain direct authorization from that person or a legally authorized representative.

Define the permitted use

Consent should name the project, types of scripts, languages, channels, audience, territory, and time period. “Marketing” is too broad if the actual use may include paid ads, customer calls, political material, adult content, or automated agents. State whether the voice may be modified, combined with another voice, or used to train later models.

Control access and generated material

Limit who can upload reference audio, create generations, download files, and share credentials. Keep an audit trail of the source recording, consent version, model or voice ID, scripts, operators, and exports. Do not place sensitive reference recordings in casual chat threads or shared folders with open links. Remove access when a team member or vendor no longer needs it.

Review and disclose the output

The speaker or an authorized reviewer should approve representative output before publication, especially in a new language or sensitive context. Correct pronunciations that could change meaning. Where an audience may reasonably believe the recording is live or authentic, add a clear disclosure that synthetic speech was used. Do not use a clone to impersonate a person, bypass authentication, or make them appear to endorse words they did not approve.

Plan revocation and deletion

Consent should explain how the speaker can pause or revoke future use and what happens to stored recordings, models, and generated files. Define a contact path and response owner before launch. Some already-published media may be difficult to recall, so the agreement should distinguish future generation, internal archives, and public copies. Keep only the material required for the approved purpose and legal obligations.

Production checklist

  • Verify the speaker or authorized representative
  • Name projects, languages, channels, and duration
  • Restrict access to recordings and voice IDs
  • Keep script and export audit records
  • Review new languages and sensitive contexts
  • Define revocation, retention, and deletion