A proof of authorship gets tested exactly once, when someone has a reason to doubt it. That is the wrong moment to discover that what you were holding was a claim dressed up as evidence.
Four separate things decide whether a digital record survives that test: a hash that ties it to one exact file, a timestamp that fixes when it existed, a signature that ties it to a real identity, and a certificate that lets a stranger check all three without asking you anything. Leave one out and the record can still look complete. It simply stops working the moment somebody has a reason to check it.
The hash: proof of exactly which file
A cryptographic hash is a fixed-length value calculated from the bytes of a file. Change one character, one pixel, one line of hidden metadata, and the hash no longer matches. That is the entire point of it: a hash does not describe a file in general terms, it identifies one specific version of it.
Most disputes are not really about whether you made something. They are about which version you made, and when. A file name and a description are claims somebody typed. A hash is a value derived from the file itself, which is why it survives being challenged in a way a label never does.
A hash also works in one direction only. It cannot be used to reconstruct the file it came from. That is what allows a content hash to sit in a public, searchable database, an ISCC-style identifier that makes a work traceable for infringement checks and AI-training licensing, without the original file ever leaving your possession.
The timestamp: proof of when, from someone other than you
A date in your own system is a date you set. It sits in a database you administer, on a server you control, and somebody with the right access could change it. None of that makes it false. It makes it unusable as evidence against a skeptical counterparty, because the party making the claim and the party who wrote the date are the same party.
A qualified electronic timestamp comes from outside that loop. A Qualified Trust Service Provider issues it over the hash, and under eIDAS, a qualified timestamp carries a legal presumption as to the date and time it indicates and the integrity of the data it is bound to. The date stops being something you assert and becomes something a third party attested to, independently of your own systems.
That is the piece that turns "we had this on the third of March" from a sentence into a fact somebody else can check.
The signature: proof of who
A hash proves which file. A timestamp proves when. Neither says anything about who made it, which is the signature's job, and it is why the three are not interchangeable, only cumulative.
A qualified electronic signature issued through an accredited certification service provider carries the same legal effect under Swiss law as a handwritten signature, per ZertES. That effect depends on the signature being tied to a verified identity at the point of issuance, not on a signer typing their own name into a form. A name in a text field is a claim about identity. A qualified signature is issued only after that identity has already been checked by a party other than the signer.
The certificate: proof that anyone can actually check
The first three pieces can all be genuinely true and the record can still fail, if checking any of them requires trusting the party making the claim or contacting them directly. A certificate that bundles the hash, the timestamp and the signature into one document, with a link that resolves to a public verification page, is what closes that gap.
The test is simple. Send the link to somebody with no account, no relationship to you, and no reason to take your word for anything. If they can open it and confirm the file, the date and the identity without a single message to you, the record holds up. If verification requires an email to your team first, what you have is a claim with better formatting, not proof.
A working example
A designer delivers a brand concept to a client on a Tuesday. Three months later a near-identical design appears from a different source, and the designer has to show their version existed first, unchanged, and that it was theirs.
An email with the file attached shows a date, but that date sits in a mail server the sender does not fully control, and the attachment could in theory have been swapped into an older thread. A hash computed from the exact delivered file, timestamped by a Qualified Trust Service Provider on the day of delivery, and signed under a verified identity, answers all three questions at once: this file, this date, this person. Anyone checking the certificate later does not need to trust the designer's account of what happened. They check the record instead.
Why partial proof fails at the worst moment
A file with only a hash proves a version exists, not when or by whom. A file with only an internal timestamp proves a date somebody could have set themselves. A file with only a signature proves an identity but not which version of the work that identity actually signed. Each piece answers a different question, and a dispute rarely stays confined to the one question your particular record happens to answer.
This is also why a checkbox is not the same thing as a record. A declaration of "AI generated" or "human authored" is only as true as the trust placed in whoever wrote it. Bind that same declaration to a hash and a qualified timestamp, and it stops being a statement you made and becomes a fact about a specific object, dated by somebody who was not you.
Why this travels across borders, and what it does not do
Under the Berne Convention, copyright arises automatically on creation in more than 180 countries, with no registration required anywhere. That is a right, and it already crosses every one of those borders on its own. Proof of when and how you exercised it does not cross a border automatically the same way an unrecorded claim does, but a hash, a qualified timestamp and a verified signature are checkable data, and checkable data works the same way wherever somebody opens the link.
Stated narrowly, because narrow is accurate here: a verification page confirms that a specific file matched a specific hash at a specific time, signed by a specific identity. It is not automatic legal admissibility in every court. How a particular court treats a particular piece of evidence is a matter for that court's own procedure, and no technology changes that. What the record gives you is the same underlying fact, checkable the same way, regardless of which border the dispute happens to land on.
A short check for your own records
Before relying on any proof of authorship you already hold, four questions decide whether it survives being challenged: does it identify one exact file rather than a description of one; was the date set by a party other than you; is the identity behind it verified by someone other than the person who typed it; and can a stranger check all of that without emailing anyone first. A record that answers yes to all four is evidence. A record that answers yes to one or two is a well-organized set of claims.
The full mechanics of producing a record like this, from upload to verification link, are covered in how the process works.
