Skip to content

LikenessConsent

Stable

Ask for, track and control a real person's consent to use their face or voice in avatars.

Also known as face consent, likeness check

Install with npm install @tattva/ui (setup), or copy the code from the kit in Downloads.

Every status

Asha Rao's face and voice

Waiting for Asha
  1. Ask, done
  2. Record, current
  3. Review
  4. Ready

Waiting for Asha to record

We sent Asha a link to record on their phone. It expires in 23 hours.

Nothing can be made with this likeness until Asha records and agrees.

Consent covers this workspace only. It does not give anyone ownership of Asha's likeness.

Waiting for Asha to record. The link expires in 23 hours.

The view of the person who asked. Pending is amber because Asha still has to act; nothing else is. They can see who may use it but not change it.

When to use it

Makes using a real person's likeness depend on that person's own recorded, scoped and revocable consent.

Made of: Whose likeness and status badge · Steps (Ask, Record, Review, Ready) · Heading · Status text · Recording (VoiceConsentCheck) · Who can use it · Where it was used · Actions · Scope note

Use it for

  • Creating an avatar of a teammate or presenter.
  • Cloning a person's voice for video narration (kind="voice").
  • A settings page where people see and control their own likeness.

Not for

Do and avoid

Asha Rao's face and voice

Not requested
  1. Ask, current
  2. Record
  3. Review
  4. Ready

Ask Asha for consent

Asha records a short video on their own device and reads a few lines aloud. That recording is the consent. A photo is not enough.

The link lasts 24 hours. Asha can say no, and can withdraw consent at any time later.

Consent covers this workspace only. It does not give anyone ownership of Asha's likeness.

Do. Asha records her own consent before her face is used.

Make an avatar

Upload a photo of the person
Avoid. A photo upload uses someone's face without ever asking them.

Do

  • Have the person record their own consent, and let it expire after 24 hours if they do not.
  • Start who-can-use-it at the narrowest choice.
  • List every use and tell the person each time.
  • Say what happens to takes already made when consent is revoked.

Avoid

  • Do not make a likeness from an uploaded photo of a real person.
  • Do not use amber once the person has acted. Accepted, rejected and revoked are not waiting on anyone.
  • Do not let anyone but the person in it widen who may use it.
  • Do not reduce consent to a terms checkbox.

On a phone

  • Fills the width. Action buttons share the row on a phone.
  • The step names sit under the step bar and stay readable at 320px.
  • Recording happens on the subject's own phone by default; "record now" opens the same check here.
  • Choices in Who can use it are 44px tall on touch.

Seen in products

  • HeyGen's avatar consent has pending, accepted and rejected statuses, null for avatars that are not real people, and a webcam link that expires in 24 hours.
  • Synthesia requires explicit consent, says sharing does not transfer ownership, and lets only the avatar owner revoke access.
  • Sora let people choose who could use their cameo, revoke it at any time, and be told when it was used.
  • Google Flow starts avatar capture on desktop and finishes on the phone, and says where avatars are not available.

Build your next AI screen with Tattva.

Free and open, with the code. Start in one line.

Get started