Skip to content
Lorca Labs
Studio · Consent Receipt Registry Live demo

Try live

Issue, verify, and seal consent receipts in a tamper-evident registry. Not a CMS, not legal advice, not proof of informed-consent quality.

Experimental consent integrity — not a CMS, not legal advice, not proof of informed-consent quality.

Demo host: isolated demo host set by your deployment

Consent Receipt Registry · Agents & policy

Issue a consent receipt

Checking host…

Issue a consent receipt (purpose, scope, subject hash, issuer, expiration, meta) with a content hash and timestamp. Then verify it against the registry, and optionally seal it into a carrier image with key-bound steganography. Text/JSON only for issue/verify; sealing requires a carrier.

Not a CMS, not legal advice, not proof of informed-consent quality. Not tamper-evident beyond client-supplied hashes. The demo host runs in isolation — nothing is stored.

Issue

01

Verify

02

After issuing, verify the receipt against the registry. The host checks the content hash and returns a valid flag with reason.

Carrier image (optional seal)

03

Optional: seal the receipt into a carrier image. If skipped, the receipt is still stored with its content hash. Upload an image or generate a blank carrier.

…or generate a blank carrier
No carrier yet

No carrier loaded. Upload an image or generate a blank carrier (minimum 128×128).

Operator and workspace consoles are separate applications (pilot).