For IT & security teams

The verification seal binds the SHA-256 hash of the rendered PDF bytes and the pinned rendering engine version. The in-browser check computes SHA-256 with the Web Crypto API entirely on the recipient's device; bytes are never uploaded. An engine-supersession advisory (when shown) is looked up server-side from the published determinism changelog and never affects the hash verdict. The seal is tamper-evidence — it is not a legal e-signature and not a C2PA content credential.