Photographer
Photographers
Your portrait, re-uploaded without your terms attached.
ProveConsent · Media Consent Registry
REGISTRY SNAPSHOT
REV. 2026-10-03
REV. 2026-10-03
A chain-of-custody ledger for media consent
The record that survives the edit.
Prove the consent behind a photo, clip, or track — even after it's cropped, recompressed, or stripped of every metadata tag on the way to a re-upload.
Hero photo
images/hero-photographer.jpg
images/hero-photographer.jpg
IMG_4471_final_v2.jpg
registered 2026-05-28 · Level 1 · active
What one lookup returns
Live UI preview
Uploaded copy
IMG_4471_final_v2.jpg
✕ no EXIF✕ recompressed, cropped 12%
✕ zero matching filename
Content-derived match
pHash + fingerprint
resolved against registry
resolved against registry
Consent active
Resolved record
✓ owner identity
✓ status: active
✓ terms + revocation log
✓ status: active
✓ terms + revocation log
Illustrative example — try it with a real file. Measured re-identification rate, false-match rate, and revocation latency available on request.
Whose work travels without them
Use casesAny file that leaves your hands can lose its terms along the way. These are the four we hear about most.
Musician
Musicians
A clip lifted into someone else's track, credit stripped.
Model / talent
Models & talent
A face used to train a model you never agreed to.
Illustrator
Illustrators
Work scraped into a dataset with the byline removed.
Why metadata isn't enough
The problem
Step 01 — Original
File leaves the camera
EXIF intact, terms attached, owner known.
Step 02 — Platform
Upload & re-encode
✕ metadata stripped on ingest
Step 03 — Re-upload
Copy circulates
✕ no trail back to original terms
✓ the pixels themselves are unchanged
✓ the pixels themselves are unchanged
Embedded metadata
- ✕ Stripped on upload by most major platforms
- ✕ Gone entirely from a screenshot or re-encode
- ✕ Nothing left to trace back to original terms
The content itself
- ✓ A crop or recompression barely moves it
- ✓ Resolves back to the registered consent record
- ✓ Can't be removed without destroying the file
How the ledger works
Mechanism
L0
Total Prohibition
Private personal use only. Opts out of all display, dissemination, AI, or likeness extraction.
L1
Personal Showcase
DefaultPublic display for organic viewing. Prohibits monetization, AI crawl, copy, or likeness harvesting.
L2
Commercial Monetization
Allows commercial use on approved platforms subject to mandatory smart-contract royalties.
L3
Full Rights & AI
Allows unrestricted use, redistribution, and commercial dataset training on opt-in media.
—
Custom Terms
Power usersSet monetization and AI training independently instead of picking a preset combination — e.g. non-monetized but AI-trainable, a combination none of the four presets cover.
Setting terms during registration looks like this — four preset consent levels plus independently configurable custom terms, each a W3C ODRL policy signed with a wallet or email-derived key.
01
Register
The rights holder sets terms — commercial use, AI training, derivative works, monetization split — as a W3C ODRL policy, then signs it with a wallet or email-derived key. Fingerprints are computed from the file itself, client-side.
02
Chain
Every action — registration, amendment, revocation — is appended as a SHA-256-linked block. Each entry's hash depends on the one before it, so earlier history can't be quietly edited without breaking the chain.
03
Match
An uploaded copy is resolved back to its original registration by what it is — perceptual and content-derived fingerprints — not by filename, embedded tags, or metadata that a platform may have already discarded.
04
Revoke
Consent can be withdrawn at any time. The revocation is itself a permanent, timestamped ledger entry — never a silent deletion of the record.
Versus a C2PA manifest: a manifest travels attached to the file, so it's gone the moment a platform strips it or a screenshot is taken. ProveConsent is built to complement that approach, not replace it — resolution and revocation status come from the content itself, so the record is still reachable after the manifest isn't.
Sign with what you already hold
Identity
Solana wallets
EVM wallets (MetaMask)
Email-derived identity
No prior Web3 experience required
Put your work on the record.
Register a file, set its terms, and know the record is still reachable — long after the metadata isn't.