Consent that travels with the character
Build a character from a real person, with their consent, and keep control of every use. The license and consent receipt are stored in the .char file. OmniChar checks the license before every generation it runs, reports each use to the license owner, and lets them revoke it at any time.
Talent agencies handle consent and licensing. Productions generate. OmniChar is the technology in between.
- 01Build with consent
- 02License each use
- 03Verify anywhere
- 04Track and revoke
A folder of photos cannot carry a license
Once a character sheet leaves the agency, the license is just a contract nobody can check.
| Compare | Character sheetHow likeness is licensed today | Licensed .charThe license travels with the file |
|---|---|---|
| What you hand over | Character sheetA folder of photos | .charOne .char file with the license inside |
| Proof of consent | Character sheetA contract stored somewhere else | .charA signed consent receipt in the file |
| What's allowed | Character sheetWritten in a contract, never checked | .charUse, territory and dates set in the license |
| Where it's used | Character sheetUnknown after handoff | .charEvery generation in OmniChar reported to the owner |
| Taking it back | Character sheetImpossible once copied | .charRevoke at any time; OmniChar stops generating |
| Talent earnings | Character sheetPaid once | .charCan be paid for each licensed use |
| Proving an output | Character sheetNo way to check | .charAnyone can verify it, no account needed |
| Across models | Character sheetRe-wire photos for every model | .charWorks in FLUX.2, MiniMax H3, Krea 2, ComfyUI and the API |
EU and US rules on using a real person's likeness in AI are tightening. Consent for each use is becoming a requirement, and a folder of photos cannot show it was given.
Consent at every step
From the first build to every generation, the license stays with the character.
- 01
Build with consent
The person confirms through their consent provider that it's them and that they agree. The signed receipt goes into the .char before it's saved.
- 02
License each use
Each new use needs its own yes. The license states what's allowed and for how long.
- 03
Track and revoke
OmniChar checks the license before every generation it runs and reports each one to the license owner. The owner can revoke at any time, and OmniChar stops generating with that character.
- 04
Verify anywhere
No account needed. The check shows who the character belongs to, what the license covers, and whether it's still valid.
What is inside a licensed .char
The same file you already know, with one more block. The license refers to the person without storing personal data, and points to a status endpoint for revocation checks.
"license": {
"issuer": {
"type": "consent_provider",
"id": "provider:example"
},
"subject": "subj_7Q2K9X",
"receipt_id": "rcpt_01J9Z4M8W2",
"signature": "ed25519:9f3c…a71b",
"scope": {
"uses": ["advertising", "social"],
"territory": ["EU", "UK"],
"media": ["image", "video"],
"starts": "2027-01-01",
"ends": "2027-06-30"
},
"status_url": "https://verify.example/rcpt_01J9Z4M8W2",
"created_at": "2026-11-02T10:14:00Z"
}Who it is for
Talent and agencies
- Consent on your own phone
- See every use of your character
- Revoke at any time
- Get paid per use. The person never pays.
Productions
- A character with a clear yes for your scope
- Arrives as a .char, ready for OmniChar, ComfyUI or the API
- No folder of photos to manage
Platforms and developers
- An open license field in an open format
- A verification API
- Works with any consent provider
See every use. Revoke when you need to.
| Date | Production | Model | Outputs |
|---|---|---|---|
| Oct 22 | Production A | Flux | 24 |
| Oct 21 | Studio B | MiniMax H3 | 6 |
| Oct 19 | Production A | LTX | 12 |
| Oct 17 | Studio C | Qwen 2.1 | 9 |
| Oct 15 | Studio B | Krea | 18 |
Where the license is checked
| Where | What happens |
|---|---|
| OmniChar Cloud | License checked before every generation. Usage logged. |
| OmniChar app | Checked before generation. |
| OmniChar ComfyUI node | Checks by default. The node is open source. |
| Any other tool | Verifiable with the public check. |
Revocation stops future use in tools that check the license. It does not delete copies already downloaded or outputs already made.
Questions
Can a license be revoked after a character is shared?
Yes, for future use in tools that check the license. OmniChar Cloud and the OmniChar app stop generating with a revoked character, and the public check shows it as revoked. Revocation does not delete copies already downloaded or outputs already made.
Who stores the consent?
The consent provider stores the consent record. The .char file carries a signed receipt that points to it.
Does the person need an OmniChar account?
No. They confirm through the consent provider on their own phone.
Can anyone verify an image or a .char?
Yes. The public check needs no account. It shows who the character belongs to, what the license covers and whether it was revoked.
Is this legal advice? Does it make us compliant?
No. OmniChar is the technical layer: the format, the checks, usage tracking and revocation. It is built for consent requirements. Talk to your own legal counsel about your obligations.
Which consent providers are supported?
The first providers are in the pilot now. Talk to us if you want to take part. The license field is open, so any consent provider can issue receipts.