AI Likeness Consent: What Goes On Paper

6 minute read · amended 8/10/2026

A defensible AI likeness consent record names the person, scopes exactly what may be generated, sets an end date, states how consent is revoked, and timestamps itself — a standard photo model release does almost none of this.

The gap nobody closed

Model releases were written for photographs: a fixed image, a known use, a finite shoot. Generative systems break every one of those assumptions. The output did not exist when the release was signed, the use is open-ended, and the likeness can be recombined indefinitely.

So the paperwork most productions still use answers questions nobody is asking, and is silent on the ones that will actually be litigated.

What a usable consent record contains

Six elements. Missing any one of them turns the record into an argument rather than an answer.

  • Identity — who signed, verified well enough that a third party can believe it.
  • Scope — what may be generated: face, voice, both; which contexts are permitted and which are barred outright.
  • Term — when permission begins and when it ends. Perpetual consent is the clause that gets challenged first.
  • Revocation — the stated mechanism for withdrawal, and what happens to work already produced.
  • Timestamp — a sealed date, so the order of events cannot be argued later.
  • Receipt — a durable reference that can be attached to each generated asset, tying the output back to the permission that allowed it.

Why buyers are starting to demand it

Enterprise procurement is the forcing function. As buyers begin asking suppliers to show provenance for AI-assisted creative, the suppliers who can produce a chain of title win the contract, and the ones who cannot are dropped without ever being told why.

The same record does double duty in insurance and in union-adjacent work, where the question is not whether the output looks good but whether you can show you were allowed to make it.

How BellusTowne handles it

The Towne keeps a registrar: a person signs, scopes, dates, and may revoke permission for their likeness or voice, and a receipt is issued that can travel with the generated file. The registrar is deliberately neutral — it holds the covenant, it does not own the face.

Alongside it sits the ledger of making, which records what produced an asset, from what inputs, under whose licence, at what moment. Consent answers 'were you allowed'; the ledger answers 'and can you show it'.

Questions the Herald is asked

Does a standard model release cover AI-generated likeness?
Usually not well. Photo-era releases assume a fixed image and a known use; they rarely scope synthetic generation, set a term for it, or define revocation. Treat an old release as a starting point, not coverage.
Can consent for AI likeness be revoked?
It should be, and the record should say exactly how, and what happens to work already produced. A consent record with no revocation mechanism is the clause most likely to be challenged.
Who needs a likeness consent registry?
Agencies, studios, brands, campaigns, and anyone paying a real person to appear in synthetic media — plus estates and families dealing with the voice of someone who has died.
Is a signed PDF enough?
It carries the terms but not the proof: a PDF alone does not fix its own date or tie itself to the assets it authorised. What closes the gap is a timestamped record plus a receipt attached to each generated file.

Where this leads

Other halls

Strength & Solidarity LLC dragon-shield emblem
Hearthsong silent