Skip to content

How it works

From file to verifiable evidence.

Here is exactly what happens when you register a creation — and what a verifier sees when they check it.

Register a CreationVerify a record

The process

Six things happen in under a minute.

  1. I

    You upload

    Choose a file, a category and a title. Add the date you created it if you know it — we record it as your statement.

  2. II

    You declare

    You confirm that you created the work or are authorised to submit it. The exact declaration wording and its version are stored with the record.

  3. III

    We fingerprint

    We calculate the SHA-256 fingerprint of the exact bytes received. Your browser shows the same fingerprint before upload, so you can compare.

  4. IV

    We seal the time

    We note the platform receipt time and request an independent RFC 3161 timestamp for the record — validated before it is ever shown.

  5. V

    We chain the history

    The record joins a hash chain with every other record. Daily signed checkpoints are kept outside our servers.

  6. VI

    We certify

    A certificate with its own automatic number, QR code and Ed25519 digital signature is issued for the version.

Clarity

Four times. Never mixed up.

Evidence is only useful if it is precise. Every record keeps four different times apart, everywhere they appear.

  • Creation date — what you tell us, clearly marked as not verified
  • Platform receipt time — when our server received the file
  • Independent timestamp — when the external authority sealed it
  • Certificate issued — when your numbered certificate was signed

Verification

What a verifier sees.

Each result is shown separately, so nobody has to take a single green tick on trust.

Record status

Verified, superseded, archived, under review or revoked.

Certificate integrity

Whether the certificate’s digital signature matches the record. A forged or edited certificate fails.

Timestamp evidence

The independent timestamp, its authority and its validation status.

History integrity

Whether the record’s place in the hash chain is intact.

File comparison

Drop a file to check it against the recorded fingerprint — computed in the browser, never uploaded.

Privacy respected

Only the details the creator allows are shown. The original file is never exposed.

Plain language

What is a fingerprint?

A SHA-256 fingerprint is a 64-character code calculated from every byte of a file. The same file always gives the same code. Change a single byte — one note, one pixel, one comma — and the code is completely different. It is practically impossible to make a different file with the same fingerprint.

Read the FAQ

Ready to record your first creation?

Three free records. Takes two minutes.

Register a CreationPricing