Step 1. You upload a file
Use whichever channel is convenient — they all create the same kind of certificate:
- the web app on any device;
- the Chrome extension in the browser sidebar;
- e-mail: send the file as an attachment to SecureAuthorBot@gmail.com;
- the API from your own software.
Any file type works: images, PDF, Word documents, audio, video, source code, archives.
Step 2. SHA-256 fingerprint
SecureAuthor calculates the file's SHA-256 hash — a cryptographic fingerprint such as
26be856c7aa5748040bcf998b18d3081cacb2ab1e4e3b34aece9e86152f083aa.
Three properties make it useful as proof:
- Unique: two different files practically never produce the same hash.
- Sensitive: change one pixel, one comma or one byte and the hash is completely different.
- One-way: the hash cannot be turned back into the file, so it reveals nothing about your content.
The file is used only to calculate the hash and is not stored. What is a file hash? →
Step 3. Your certificate
You immediately get a receipt and a PDF certificate containing:
- certificate (receipt) ID;
- file name and size in bytes;
- date and time in UTC, in ISO 8601 and as a Unix timestamp;
- the SHA-256 hash;
- the blockchain network (Polygon Mainnet) and the record status;
- the expected time of the blockchain record;
- your user ID, if you are signed in.
Step 4. Anchoring on the Polygon blockchain
Receipts created since the previous record are combined into one period hash (shown as "Summary hash" on the certificate). A short JSON record with the period start and end, the period hash and a link to the list of receipts in the batch is written to Polygon in a single transaction. Anchoring runs twice a day, at 00:00 and 12:00 UTC. All records
are sent from one public address,
0xa3bb4f9ef78b51b9b9b75757f10db03705b2aabb, so anyone can list them on
Polygonscan.
After the run, the receipt status changes to Recording completed and you can download an updated certificate with:
- a link to the transaction on Polygonscan;
- the summary hash (period hash) written on-chain.
From then on the record is public and permanent. Nobody — including SecureAuthor — can change it or backdate it. Example transaction
Step 5. Verification
To prove authorship, upload two things on the verification page:
- the original file, and
- the certificate PDF or just the receipt ID.
SecureAuthor recalculates the hash and shows Files are equal or Files are different, with both hashes side by side. You can download the result as a PDF.
You can also check the whole chain yourself — file hash, Polygon transaction, period hash and batch list — with standard tools. Step-by-step independent check →
One file, one registration
If a file has already been registered, SecureAuthor does not create a new certificate — it returns the original one. This means the earliest registration of a file always wins, and a copy registered later by someone else cannot replace yours.
What SecureAuthor does not do
- It does not judge originality or check whether the work is yours — it records that you had this file at this time.
- It is not a government registry and does not give legal advice.
- It does not monitor the internet for copies of your work.