Security and privacy

SecureAuthor does not store your files. A file is sent over an encrypted connection, its SHA-256 hash is calculated and the file is discarded. Only the receipt is kept — hash, timestamp, file name, size and type — and only the hash is written to the Polygon blockchain, from which the file cannot be reconstructed.

What we keep — and what we don't

DataKept?
Your fileNo — hashed and discarded
SHA-256 hashYes — needed for verification
Upload timestamp (UTC)Yes
File name, size, typeYes — printed on the certificate
Account ID and e-mailOnly if you sign in with Google
On the blockchainPeriod start/end, the period hash of the batch, a link to the batch list
Public batch listReceipt 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.

How verification works →

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.

Frequently asked questions

Can someone see my work on the blockchain?

No. Only a hash is published. A SHA-256 hash is one-way: it cannot be turned back into the file and reveals nothing about its content.

Is it safe for confidential documents?

The document is not stored and only its hash is published, which makes the method suitable for confidential material. The file name is stored in the receipt, so rename the file before uploading if the name itself is sensitive.

What if SecureAuthor disappears?

The anchoring record stays on the public Polygon blockchain forever, and your certificate carries the file hash, the time, the period hash and the transaction link. Keep the original file and the certificate together, and save a copy of the batch list from the certificate's link.

Can SecureAuthor change or backdate a record?

Not after anchoring. Once the summary hash is in a Polygon transaction, its time is set by the network and cannot be changed by anyone.

Updated:

Protect your next file in seconds

Free proof of authorship: SHA-256 hash, UTC timestamp and a Polygon blockchain record. Your file is not stored.

Add to ChromeProtect a file