Free verification certificate · self-issued, honestly labeled
Hand over the file — and the proof of what was in it.
A trust receipt binds a file's SHA-256 fingerprint to the disclosure check it passed: score, signals, rules version, time. Print it, attach it to the delivery, and anyone can later re-verify that the file in front of them is byte-for-byte the file that was checked.
Drop a file to issue its receipt
The fingerprint and score are computed locally — the file is never uploaded.
Verify a delivered file against a receipt
Paste the fingerprint from any trust receipt, choose the delivered file, and compare. A match means byte-identical; anything else — a re-save, a resize, a platform copy — changes the fingerprint and fails the check, which is the point.
Questions
What exactly does a trust receipt prove?
Two things, no more. First, that a file with this exact SHA-256 fingerprint was checked at the stated time and produced the stated score and signals — the fingerprint covers every byte, so the receipt describes one exact file. Second, later, that a delivered file is byte-identical to the checked one, if its fingerprint matches. It does not prove who created the file, that the score was deserved, or anything about the scene the file depicts.
Is a trust receipt the same as Content Credentials (C2PA)?
No, and the receipt says so on its face. C2PA is a signed manifest embedded in the file by an identified signer, verifiable against a trust list. A trust receipt is a self-issued record kept alongside the file: no signature, no trust list, no third-party attestation. It is the right weight for a freelancer-to-client handover — a shared, checkable record — and the wrong tool where regulated provenance is required.
Why would a client want one?
Because deliveries drift: the file a client publishes is often a re-save, a screenshot, or a platform copy of the file the creator checked. The receipt freezes the checked state — score, signals, fingerprint — so both sides can later prove which file was actually approved, and re-run the fingerprint check on whatever is about to go live.
Is my file uploaded anywhere?
No. The fingerprint and the score are computed by JavaScript in your browser; the file never leaves your device, for issuing or for verifying. You can confirm it in your browser's network panel — dropping a file makes no upload request.