Consent must describe a use
“The singer said yes” is not enough for a reusable model. A useful agreement identifies the recordings, the model operator, who may access it, allowed genres or contexts, commercial scope, payment, credit, security, duration and what happens when permission ends.
Consent should be understandable to the performer before recording. Do not hide model training inside a general studio release if the practical effect is a voice that can generate new performances.
Keep identity and performance distinct
A voice conversion can preserve timing and expression from one performance while changing apparent identity. Record who performed the guide and whose timbre model was used. Both contributions may matter. Avoid marketing language that implies a person sang words they did not approve.
Plan revocation before success
Decide whether revocation blocks future generations, requires model deletion, affects already licensed releases, or triggers a takedown process. Technical deletion and contractual withdrawal are not always the same. The agreement should say what can actually be done.
Session checklist
- Identity verified and scope explained.
- Training files listed and secured.
- Permitted users and projects named.
- Review or approval points defined.
- Compensation and accounting defined.
- Revocation contact and response documented.
Use licensed models precisely
A platform may describe artist permission or revenue sharing while individual models carry different rules. Save the model-specific license and any required approval. Do not translate “licensed model” into a blanket claim that every output is cleared for every use.
Sources & reading trail
- Voice-Swap — primary documentation or research used for the bounded claims above.
- Human Artistry Campaign — primary documentation or research used for the bounded claims above.
- Kits AI rights guidance — primary documentation or research used for the bounded claims above.
Reviewed for this local compilation on 15 September 2026. Product terms and platform policies can change; recheck them for a release. This article is editorial guidance, not legal advice or a claim of independent product testing.