ClearedBadge keeps a fingerprint of your file and the time, not the file itself. Keep your original file.
By creating a record you accept the Beta Terms and the Privacy Policy.
How it works
Standard: your file is sent over HTTPS to the ClearedBadge engine, which computes the
SHA-256 fingerprint of its exact bytes itself. The file is processed in memory only and not retained.
Private: your browser computes the same SHA-256 fingerprint of the exact bytes. Only that
fingerprint is sent; the file, its name and its size never leave your device. If you already have the
SHA-256 (for example calculated with code), you can enter it instead of choosing the file. ClearedBadge then
registers the fingerprint you supplied; it does not receive the file and cannot check which file it belongs to.
Either way, ClearedBadge keeps the fingerprint and the time — not the file. Keep your original file:
it cannot be recovered from the record. Both methods give the same fingerprint for the same file and
are verified the same way.
We hash the exact bytes without interpreting the file's contents. You get a record ID and a Verify link
to pass on with the unchanged file.
Recording an agent's JSON output? See For AI agents:
a JSON file uploaded here becomes a file record and is checked byte for byte.