# AI Avatar and Voice Permissions: What to Record Before Production [Read the original article]() By Garry ยท Founder Published: 2026-09-27T21:12:12.976Z Updated: 2026-09-27T21:25:40Z 6 min read Categories: Content creation Before creating an AI avatar or cloned voice from a real person, record what they have actually agreed to. Permission to film an interview is not automatically permission to generate new. ![A small microphone and blank card beside tied folders, a lockbox, and a key.]() ## Key takeaways - Separate source copyright from likeness, voice, privacy, and contract questions. - Describe new performances and translations explicitly in the agreed scope. - Link every published variant to a usable permissions record. Before creating an AI avatar or cloned voice from a real person, record what they have actually agreed to. Permission to film an interview is not automatically permission to generate new performances, translate their speech, or place their likeness in future advertisements. Define the intended use before uploading reference material. A useful permissions record is specific enough that a future editor can decide whether a proposed use is covered. It should identify the person, assets, purpose, allowed transformations, distribution, duration, restrictions, and contact responsible for questions. Keep that record beside the production files. ## Separate the rights and interests involved Several issues can exist at once: copyright in source material, rights connected to a person's likeness or voice, privacy, contractual restrictions, and the terms of the generation provider. A license to a photograph does not necessarily resolve all of them. The [U.S. Copyright Office's AI resources]() address digital replicas and copyrightability in separate reports. That distinction is useful: whether an output receives copyright protection is not the same question as whether you may create or commercially use a replica of someone. Rules vary by jurisdiction and context. A practical production team should identify which issues apply and obtain appropriate advice for uncertain or sensitive uses. Avoid treating a generic release downloaded from the internet as proof that every future synthetic performance is authorized. Also review advertising implications. An authorized voice can still deliver an inaccurate endorsement. The [FTC's endorsement guidance]() requires attention to truthful opinions, experiences, and material connections. ## Describe the synthetic use in ordinary language Explain what the system will do with the reference material. Will it create a digital presenter, generate new speech, change language, alter appearance, or combine the person with a different setting? A person should not have to infer those uses from technical jargon. Show examples or a limited pilot where appropriate. The practical effect of a synthetic performance can be easier to understand when someone sees how their likeness or voice may appear. Keep the example distinct from approval of an unlimited future library. State whether the content is promotional, educational, internal, or another defined use. An employee agreeing to an internal training avatar may not expect to appear in paid advertisements for unrelated products. Write down what is prohibited. Restrictions may concern subject matter, political uses, sensitive claims, particular products, or contexts that would change the person's apparent views. These boundaries should be visible to editors, not hidden in a file only one person knows about. ## Define scope before scale Record the channels and territories where the output may appear, the duration of use, and whether paid advertising is included. Clarify whether partners, agencies, or other brands can access or reuse the asset. Define transformations explicitly. Translation, new scripts, voice changes, edited facial expressions, and new product endorsements can materially expand the original use. Do not assume that permission for one transformation includes all others. Set an approval process for new scripts or sensitive uses when needed. Specify who can approve, what they will review, and what happens if the person does not respond. Silence should not become an invented permission rule. Connect these requirements to your [approval workflow](). The workflow should prevent a publisher from treating a technically available asset as automatically cleared for any campaign. ## Record storage, access, and provider handling Reference recordings and likeness assets may be sensitive. Limit access to people who need them for the agreed production task. Do not place private reference media in public repositories, generic prompt libraries, or broadly shared folders without a reason. Review the provider's terms for input handling, retention, training use, deletion options, and commercial output rights. Keep the relevant terms and account configuration with the project record, especially if they can change over time. Identify who can request changes or removal and how the team will respond. A removal request may affect source files, generated outputs, scheduled posts, and copies held by partners. A clear inventory makes that response more manageable. Do not promise technical deletion or revocation behavior that your tools cannot provide. Explain the practical process honestly and confirm any provider-dependent steps rather than assuming every system offers the same controls. ## An illustrative permission record for a founder voice Imagine a founder wants a synthetic version of their own voice for product tutorials. This is a hypothetical planning example. The initial purpose is a set of short explanations on the company's website and social accounts. The record identifies the source recording, approved product topics, allowed languages, review owner, distribution channels, and period of use. It states that new claims and paid advertisements require an additional review. It also identifies who can generate new audio and where the reference files are stored. Later, a partner asks to use the voice in a joint promotion. The team does not assume the original tutorial permission covers that request. It checks the partner distribution and promotional scope, then records any additional agreement before production. This process makes expansion possible without losing track of what was authorized. The record is useful precisely because it can answer a new question, not because it contains a large amount of formal language. ## Keep a permissions ledger for every reusable identity A practical ledger should include the identity or avatar identifier, source assets, agreement location, allowed uses, restrictions, expiry or review date, approval contact, and locations where outputs have been published. Add the provider and relevant account owner. Link every final asset to that entry. If permissions change, you should be able to find the affected videos without searching by a person's face or guessing from filenames. A series identifier can help connect variants and translations. Use an [evergreen content library]() to track whether the content remains valid, but include permissions as well as factual freshness. A video can remain technically accurate while its agreed use period has ended. Review the ledger when a campaign expands, a new agency joins, or a provider changes. These are moments when assumptions often become outdated even though the asset itself has not changed. ## Preserve the person's meaning in the final performance Permission to use a likeness is not a reason to make the person appear to say anything convenient. Review the script, delivery, context, and surrounding caption. A neutral explanation can become an apparent endorsement when paired with a strong recommendation or personal claim. If a real customer statement is involved, preserve its qualifications and context. Do not translate or shorten it in a way that changes the experience being described. Keep the original approved wording available to the reviewer. Draft supporting copy with the [caption generator](), then inspect it for new claims about the speaker. Caroush's [free tools]() can support adjacent content, but they do not establish likeness permissions or replace provider agreements. Before release, confirm that the use matches the record, the facts remain supported, and any required disclosure is present. The strongest permissions process leaves both the creator and the production team able to understand what happens next. Include a practical exit procedure in the agreement discussion. Identify the person who can stop new generation, the team that can locate scheduled uses, and the process for reviewing already published material. Do not leave these responsibilities until a disagreement occurs. Even when everyone has a good relationship, staff changes and agency handoffs can make informal understandings difficult to recover. A clear process helps the team respond consistently without promising removal from systems or copies it does not control. ## Sources - [U.S. Copyright Office: Copyright and Artificial Intelligence]() - [FTC: Endorsement Guides questions and answers]() ## Frequently asked questions ### Does permission to film someone cover an AI clone? Not automatically. Clarify whether the agreement covers synthetic performances, new scripts, translations, commercial distribution, and other intended transformations. ### Can I use my own voice without any review? You control an important part of the decision, but still review provider terms, business agreements, claims, and any rights in source recordings or other material involved. ### What should a permissions ledger track? Track the identity, reference assets, agreement, allowed uses, restrictions, review dates, approval owner, provider, and locations where resulting assets have been used. ### Is copyright permission the same as likeness permission? No. Copyright, likeness or voice rights, privacy, contracts, and platform terms can raise different questions. Resolve the issues relevant to the specific use and jurisdiction. ## About the author Garry Gaurav Sapkota builds Caroush, a workspace for creating, scheduling, and publishing social content. - [https://x.com/gauravsapkotanp]()