Public Verification
Verify a Consent Record
Paste a consent hash or merkle proof to verify its integrity against published roots. No account needed.
How Verification Works
Every consent action (grant, access, revocation) creates a cryptographically signed entry in the consent ledger. Each entry references the hash of the previous entry, forming a tamper-evident chain.
Entries are batched into merkle blocks. The merkle root — a single hash representing all entries in the block — is published to a global registry. This root is the trust anchor.
To verify a consent, you need the entry's proof (a path of hashes from the entry to the root) and the published root. If the computed root matches the published root, the entry is verified — without revealing any personal data.