Verify that the file in your hands is the file that was published — and read a work's session record. Files you drop here are hashed in your browser and never leave your computer. (That promise covers your files; the page itself carries the site's usual privacy-friendly analytics.)
Handed a work with an Earned Trust QR code on it? You don’t need this page to scan it — your phone’s own camera is the scanner:
The record travels inside the code itself — no account, no download, nothing sent anywhere. On a computer with a printed page? Scan with your phone, or drop the work’s file below instead.
New here? See how this works before you try your own file.
Try a sample record → Verify my own fileNo download, nothing needed — the sample record rides inside the link itself.
A record card is the author's account of the work — dates, services, and what each session did. It describes; it does not prove. Proof is the fingerprints: verify the published file below, and the sealed evidence if the author published a seal manifest.
Copied — paste it into any AI.Paste the checksum from the work's Zenodo record (Files section — an md5:… value) or from its published seal manifest (a SHA-256 value). The reader detects which kind it is.
MD5 appears here only because Zenodo publishes MD5 checksums; Earned Trust’s own seal manifests use SHA-256.
On any Zenodo record page, the Files table shows each file's md5: checksum — for example, the Earned Trust standard itself: doi.org/10.5281/zenodo.20719927 (always resolves to the newest version). A work sealed with the Earned Trust Field Kit also publishes a manifest of SHA-256 fingerprints for its retained evidence.
A match proves the file is byte-for-byte the one that was published — not altered, not trimmed, not swapped. A mismatch doesn't prove bad faith; it proves this copy is not that file. Get the original from the record and check again.
This page saves a draft in your browser as you type, so you can come back. Nothing is sent until you press Send in your email.
Answer the fixed choices in one sitting. Nothing is uploaded by this page. Before you send, the page shows you back everything that will be used.
When you press Submit, the exit form makes two lines from your answers. Your public line holds everything that prints — it goes in the report’s appendix word for word, and it is the only thing in the QR image. Your private line holds the seven report-private answers; the study keeps it, counts it into totals, and never prints it. Both lines go in the same exit email. Your private line is held by the study and never printed; it is not encrypted, and email is a postcard.
An exit form you already sent is already the study’s raw data and still prints; withdrawal cannot pull it back. Compression is not encryption: anyone with the Reader can decode either line. Keep your own copy. Never enter a passphrase here.
This must be the author name on your Zenodo record. If they differ, you will get one email saying so, and the correction form takes your name and DOI together.
If anything is wrong, change it above and press Submit again. This recheck is the last word — there is no later change window; your documented-participant letter and the report will carry this line generated from what you send, never retyped. When it is right:
One form, one send. Both lines go in the same exit email. Your exit is complete when that email arrives. Keep both lines with your own records.
If your email program doesn’t open, copy the three pieces and paste them into a new email.
Paste a complete ETB1 line (a public line) or ETB1P line (a private line). Decoding happens in this browser; nothing is uploaded. A public line shows no report-private items; a private line shows only the seven (five on a line made before 12 September 2026).