What we keep — and what we don't
| Data | Kept? |
|---|---|
| Your file | No — hashed and discarded |
| SHA-256 hash | Yes — needed for verification |
| Upload timestamp (UTC) | Yes |
| File name, size, type | Yes — printed on the certificate |
| Account ID and e-mail | Only if you sign in with Google |
| On the blockchain | Period start/end, the period hash of the batch, a link to the batch list |
| Public batch list | Receipt ID, SHA-256 hash, timestamp, file name and size |
Why the hash is safe to publish
A SHA-256 hash is a fixed-length value (64 hex characters) calculated from the file. It works only one way: with the file you can recompute the hash, but with the hash you cannot recover the file. That is why publishing it proves existence without disclosing content.
Built on open standards
- the hash algorithm is an open standard (SHA-256, FIPS 180-4) — anyone can recompute it;
- the record sits on a public blockchain (Polygon) with its own timestamps;
- the certificate shows the file hash, the time, the summary hash and the transaction link.
Practical tips
- Rename files with sensitive names before uploading.
- Keep the original file and the certificate together, with a backup.
- Do not edit or re-export the registered file — create a new certificate for each version.
Read the Privacy Policy and Terms of Use.