It is getting easy to put a familiar voice on a new script or a familiar face on a new scene. Ease is not permission. This is project hygiene for makers: how to decide whether synthetic voice or likeness belongs in the work at all, and what consent has to cover before you generate.
The checklist is not a release, licence, capacity assessment, or lawful-basis decision. High-risk, employment, minor, deceased-person, political, intimate, and commercial uses require specialized review.
It is not a cloning tutorial. For personal scam defense around your own voice, use voice clone personal safety check. For still photos of people, use photo consent before AI edit or share. For adult non-consensual intimate imagery emergencies, use adult deepfake first response and StopNCII.org. Stage-level taste decisions remain in keep your taste.
Why “they would probably be fine with it” fails
Illustrative scenario: a podcast producer clones a co-host’s laugh as a transition sting “as a joke” using old episode audio. The co-host hears it in the published feed. Permission for the original recording did not cover this new synthetic use.
Consent is specific. A person who agreed to be recorded for Episode 12 did not automatically agree to a synthetic performance in a trailer, an ad, or a fictional scene.
Do not build a workflow that starts with generation and asks for forgiveness. Synthetic media is hard to claw back once distributed. Consent is a gate before render, not a caption after upload.
Consent scope checklist (minimum)
Before any synthetic voice or likeness generation for a project, get a clear yes that covers:
- Who - the identifiable person (or rights holder for estates / minors - get appropriate guardian/authority involvement; do not improvise).
- What - voice only, face only, full performance, stills, etc.
- Which scripts/scenes - attach or summarize the intended lines and contexts.
- Where it will appear - private draft, password review, public feed, paid ads, training data, merchandise.
- How long - one campaign, one season, perpetual? Prefer time-bounded rights.
- Withdrawal and takedown limits - how they can stop future controlled use, which channels you can take down, what law or contract governs, and which distributed copies you cannot promise to recall.
- Compensation - unpaid cameo vs. paid performance; write it down.
- Storage - where reference audio/video will live, who can access it, when it will be deleted.
Keep the answers in the project record and use an appropriately reviewed agreement where one is needed. A chatbot conversation is not a substitute for that agreement.
Reference recordings are sensitive biometric-adjacent material in practice even when your local law uses different vocabulary. Store them in access-controlled folders, do not paste them into random consumer accounts, and follow the agreed retention, deletion and any controlling legal requirements. Pasting a client’s voice sample into an unapproved tool can also be a work-secrets problem (do not paste work secrets).
Project hygiene steps
- Decide if you need likeness at all. A narrator hire or stock licensed for commercial use may be cleaner.
- If you proceed, resolve the intended scope and provider processing before upload. A change of service may require revisiting permission.
- Generate only inside the approved scope. New scene = new yes.
- Label synthetic performances in credits when audiences could assume a real performance (disclose AI in creative credits).
- Keep a controlled-channel takedown plan. Know how you will stop future use and remove the asset from feeds and ads you control, while documenting any technical, contractual, archival, or third-party limits. Do not promise a universal recall after distribution.
Special-care cases
- Minors: default to no synthetic likeness for public projects without specialized legal and parental/guardian process. This article will not soften that.
- Intimate or sexualized content: adults only, with explicit, documented consent for that exact use and separate checks of law, platform rules and third-party rights. Do not create sexualized depictions of minors; guardian permission or specialist review cannot authorize them. Non-consensual intimate imagery is a safety emergency, not a creative experiment (StopNCII; adult first response).
- Deceased persons: rights and cultural norms vary; do not treat “they’re gone” as a free license. Get counsel and family/estate clarity when the use is public or commercial.
- Employees and freelancers: Do not assume a company recording policy authorizes marketing clones. Get a project-specific yes.
Prepare questions for a real agreement
Use this as a briefing record for the person and the responsible reviewer, not as signing language:
| Issue | Decision to document |
|---|---|
| Script and scene | Exact approved version and excluded contexts |
| Provider processing | Tool/account, reference upload, training or reuse terms, access and retention |
| Publication | Channels, audience, duration and required labels |
| Change | Who approves new scripts or uses |
| Ending use | Future-use stop, controlled-channel removal, legal retention and copies beyond your control |
| Compensation and authority | Agreed terms and who has capacity or authority for this use |
Unresolved provider terms can change the person’s decision. Do not claim consent is finalized before the service’s relevant data handling is known.
Refusal and redesign patterns
When consent is missing or partial:
- Recast with a consenting actor
- Use original narration you perform yourself
- Redesign the scene so identity is not required (silhouette, abstract audio)
- Drop the bit
Do not “anonymize” a voice that is still recognizable to anyone who knows the person. Recognizability is the test that matters ethically.
Handle partial permission without stretching it
Invented case: a narrator approves a synthetic reading of script version 3 for an internal prototype, but declines advertising. The prototype is made only after its service and reference-audio handling are approved. When a marketer asks to reuse a line publicly, the existing permission does not cover the request. Stop that reuse and seek new agreement, hire a performer or replace the element.
The US Copyright Office’s digital-replica work treats replicas as a distinct policy issue. This example is a scope check, not a legally complete release or a statement that one jurisdiction’s rule governs all projects.



