Resources

What consent for AI training actually looks like

Consent that stands up is specific, informed, and auditable — and it separates the content licence from the voice behind it.

Published 2026-07-22 · 6 min read

The landscape here moves quickly — re-verify against the cited sources for the current status before you rely on it.

Key takeaways

  1. Real consent is specific: it names AI training and commercial use, not just appearance or research.
  2. It is informed: the person understood what their voice would be used for.
  3. It is auditable: there is a record of who agreed, to what, and when.
  4. A content licence and voice or likeness consent are two separate permissions.
  5. Provenance ties both permissions to the asset a buyer is licensing.

“We have consent” is easy to say. The harder question is what the consent actually covers, and whether anyone can prove it.

For AI training, loose consent is a liability. A checkbox nobody read, a release that predates model building, a verbal yes with no record — each looks like consent and holds up like tissue. This is what durable consent looks like instead.

Specific: consent to the use you are actually making

Consent has to name the use. Agreeing to appear on a podcast is not agreeing to train a model. Agreeing to research is not agreeing to a commercial system.

Data-protection law makes the same point. Valid consent under the GDPR is specific and unambiguous, given for defined purposes. A blanket permission to do anything with a recording is weak precisely because it is not specific. Name the purpose: training, developing, and evaluating AI models, including commercial ones.

Informed: the person understood what they agreed to

Informed consent means the person knew what was being collected, why, and what would happen to it. For voice data this matters more, because a voice can be used to build a model that speaks.

Some jurisdictions make this explicit. Illinois’ Biometric Information Privacy Act requires written notice and a written release before a company collects a voiceprint. The theme is consistent across regimes. Tell the person plainly, then get their agreement. Consent buried in dense terms nobody reads is not informed consent.

Auditable: you can prove it later

Consent you cannot evidence is, for practical purposes, consent you do not have. A buyer diligencing a dataset will ask how it was obtained. “Trust us” is not an answer.

Auditable consent means a record: who agreed, to what wording, when, and for which asset. It travels with the material. When a rights question arises months later, the record answers it. This is the difference between a claim of consent and proof of it.

Two permissions: the content licence and the voice

A common mistake is to treat consent as one thing. It is usually two.

The content licence is the right to use the recording — the file, the words, the performance. Voice and likeness consent is the right to use an identifiable person’s voice or image. They can belong to different people. The podcaster may hold the recording; the guest holds their own voice.

Durable consent captures both. On fiund, the AI-training licence sits on the asset, and where a person is identifiable, voice and likeness consent is handled separately. Owners keep ownership and approve buyers. Provenance records tie the two permissions to the file so a buyer can see the whole chain.

NoteConsent standards differ by jurisdiction. GDPR consent, US publicity rights, and biometric statutes like Illinois BIPA each set their own bar, so a single global form is rarely enough on its own.
TipIf you cannot show the wording a person agreed to and the date they agreed, assume a careful buyer will treat the consent as missing.

Sources

← All resources

Frequently asked questions

Is a signed appearance release the same as consent to AI training?

Not usually. A release written for publishing rarely names model training or commercial AI use. Consent has to reach the specific use, so most releases need updating for training.

Why separate the content licence from voice consent?

Because they can belong to different people and cover different rights. The owner of a recording is not always the person whose voice is in it, and an identifiable voice is protected on its own.

What makes consent auditable?

A durable record: the exact wording agreed, the person who agreed, the date, and the asset it applies to, kept with the file so it can be checked later.

Related resources

Want data that clears this in diligence?

Whether you're building a model or sitting on an archive, the first conversation is short and specific.

Send a brief