Bridle governs the use of AI-generated likeness and voice. Consent becomes a live permission — checked at the moment of use, revocable at will, and provable after.
or email us →The right question
Every synthetic-media tool answers "is this fake?" — after the fact. The question a performer, a union, and a general counsel actually need answered is "was this allowed — right now?"
Consent is not a checkbox at sign-up. It is a live permission, checked at the moment of use — and its withdrawal is provable. That is what Bridle enforces, and what it records: for every act of use, a signed, tamper-evident decision of whether it was conformant.
The moment
A render is running under a live grant. When the rights-holder withdraws consent, the next check refuses — and Bridle produces the signed receipt that proves it. Try it.
Northbank — shot 14 · likeness ADG-001 (face, voice)
Issued by the rights-holder, at her own service. Bridle cannot revoke — it only reads the signed list.
Signed, tamper-evident — anyone can check it.
How it works
Every use is re-evaluated live against the issuer's signed status list. Nothing is cached; anything Bridle can't verify is refused.
Bounded, revocable authority to use a subject.
Signed receipt of one act of use.
The signed conformant / non-conformant decision.
Static, signed artefact — the issuer's, not Bridle's.
Why it's neutral
Revocation authority is custody of the status-list signing key — and that key stays with the rights-holder's fiduciary, never with the operator or the vendor. Bridle holds only the public key: it fetches the signed list, verifies it, and fails closed. That separation is the whole point — and it's falsifiable.
"We have no revoke capability. Here is the code."
The claim a general counsel can falsify — not trust. The check is free and open; the guarantee around it is what Bridle sells. See the standard →
Who it's for
Deploy synthetic actors and voices with proof each use was licensed — governance above whoever renders the pixels.
Give performers withdrawal that actually takes effect — and a signed record when it does. GDPR Art. 7(3) as a running system.
The artefact your procurement team — and an underwriter — actually relies on: admissible, tamper-evident evidence.
Where we are, honestly
Bridle is a working reference implementation in early access. Today it produces signed, tamper-evident decision records, the issuer's status-list signature is real ES256, and the system is designed to be insurable. Full grant-signature verification and external anchoring are on the roadmap — we say what is proven and what is not. The open standard →
See it live
A short walkthrough of the governed actor — issue, check, the live revoke, and the receipt an underwriter relies on.