Why copyright proof works even where qualified signing doesn't
IP Copyright

Why copyright proof works even where qualified signing doesn't

Copyright exists automatically under the Berne Convention in 181 countries. What proves it in a dispute is not a signature, it is a qualified, timestamped seal on the exact file.

P
Philipp Stuppnik· Co-Founder & IP Strategy
·July 20, 2026· 6 min read
Why copyright proof works even where qualified signing doesn't — Swiss Trust Layer

A freelance illustrator in Lisbon licenses a character design to a studio in Singapore. Neither country requires a qualified electronic signature for that kind of contract, and the two sides never use one. Eighteen months later the studio reuses the character in a second project without paying a further fee, and the illustrator has to show a court, or more likely a mediator, that she made the design first and that the file she is holding up is the same one she sent. No signature dispute is involved. The entire case turns on one question: can she prove when the work existed.

This is the situation most creative and IP disputes actually sit in. The document was never signed because it never needed to be. What decides the outcome is proof of creation, and that proof does not come from a signature at all.

A signature and a timestamp answer different questions

These two concepts get merged in casual conversation, but legally they are not the same tool.

  • A signature (simple, advanced, or qualified under ZertES or eIDAS) answers: who agreed to this document, and did they consent to its terms.
  • A qualified electronic timestamp answers a different question entirely: did this exact file exist at this exact moment. Under eIDAS Article 41, a qualified timestamp carries a legal presumption of the accuracy of the date and time it indicates, and of the integrity of the data it is attached to.

A copyright dispute is almost always a timestamp question, not a signature question. Nobody is arguing about whether the illustrator consented to a contract. They are arguing about who made the character first. Confusing the two leads people to think that because a document has no signature requirement, it has no way to be proven, which is not true.

Copyright itself does not need a signature or registration

Under the Berne Convention, copyright exists automatically the moment a qualifying work is created, in every one of the treaty's 181 member countries. There is no signature step, no filing step, no fee. The right attaches to the work itself as soon as it takes a fixed form, whether that is a design file, source code, a manuscript, or a photograph.

Because Berne member states recognise each other's authors under Article 5, a work created in one member country carries copyright protection in all the others, without any local registration. This is what makes the right genuinely international, not tied to a single jurisdiction's signature rules or trust-service regime.

What Berne does not give you is evidence. The right exists whether or not you can prove it, but a right you cannot prove is a right you cannot enforce. That gap, between having the right and being able to demonstrate it, is where most disputes are actually decided.

Why the signature framework does not apply here

Qualified electronic signatures exist to solve a narrow, specific problem: certain document types, in certain jurisdictions, must carry proof of identity and consent equivalent to a handwritten signature. Under Swiss law, ZertES Article 11 sets that bar for the document categories where it applies. Under EU law, eIDAS Article 25(2) does the same. Neither of these is about proving when creative work was made. They are about proving who agreed to what.

Most copyright material never passes through that framework at all. A logo, a manuscript, a piece of music, a dataset, a photograph, a software repository, none of these is a contract requiring a signature by default. Waiting for a signature requirement to trigger some kind of protective action means most creative work sits with no evidentiary record until a dispute forces the question, at which point it is too late to create one.

What actually holds up when creation date is disputed

In practice, courts and mediators weigh evidence of creation date on a spectrum of reliability:

  • File system metadata and email timestamps are the weakest form. Both can be altered locally, and neither is independently verifiable.
  • Self-mailing or third-party cloud storage dates are stronger but still depend on trusting a platform's internal clock and access logs, which were not designed to serve as legal evidence.
  • A cryptographic hash of the file, sealed with a qualified electronic timestamp from an accredited Qualified Trust Service Provider (QTSP) is the strongest form available. The hash proves the exact file, byte for byte. The qualified timestamp proves the exact moment, with the legal presumption of accuracy that eIDAS Article 41 provides. Because the underlying right is recognised globally under Berne, this evidence is not limited to a single jurisdiction the way a signature framework can be.

This is also why blockchain timestamps alone are not the same thing as a qualified timestamp. A blockchain entry can show that a hash existed on a given date, but it does not carry a QTSP's regulatory accreditation or the legal presumption that comes with it. It is evidence a court may weigh, not evidence a court is required to presume accurate.

The practical takeaway

If a piece of work does not fall under a qualified signature requirement, that is not a gap in its legal protection, it means the protection was never going to come from a signature in the first place. Copyright already exists automatically under Berne. What is missing, for most creators and companies, is the sealed, timestamped record that turns an automatic right into a provable one, wherever in the world the dispute eventually happens.

For a closer look at why automatic copyright alone is not enough once a dispute starts, see Why Automatic Copyright Is No Longer Enough in 2026.

Protect your work with Swiss Trust Layer AG

Seal your intellectual property with a court-proof e-Seal backed by Swisscom Trust Services.

Book a Free Demo

Related Articles

For UAE company-formation firms: sealed, verifiable corporate documents
Country Markets

For UAE company-formation firms: sealed, verifiable corporate documents

UAE company formation runs through a chain of documents, from the Memorandum of Association to shareholder resolutions and powers of attorney, that pass through several parties before a license is issued. Here is what a sealed, timestamped record adds for corporate-services firms handling multi-jurisdiction incorporations, and where it fits alongside UAE notarization and attestation requirements.

July 26, 2026Read more →
Signing legally in the UAE with UAE Pass: a simple guide
Country Markets

Signing legally in the UAE with UAE Pass: a simple guide

UAE Pass is the UAE's national digital identity and e-signature platform, backed by Federal Decree-Law No. 46 of 2021. Here is when UAE Pass is enough on its own, and when a document needs a signature built for recognition outside the UAE too.

July 24, 2026Read more →
Voice cloning and consent: proving you had the right to use a voice
AI & Technology

Voice cloning and consent: proving you had the right to use a voice

Voice cloning consent disputes are rarely about whether permission was given. They are usually about whether anyone can prove exactly what was agreed and when. Here is why right-of-publicity law for voice varies by jurisdiction, what EU AI Act Article 50 adds on top of consent, and where a qualified timestamp actually helps, and where it does not.

July 23, 2026Read more →
How AI companies prove training-data provenance and defend copyright claims
AI & Technology

How AI companies prove training-data provenance and defend copyright claims

AI companies face two distinct exposures when training models: EU AI Act Article 10's data governance requirements, and civil copyright claims over training data. Here is what a defensible dataset provenance record actually needs, and what a qualified timestamp on a dataset hash can and cannot prove.

July 22, 2026Read more →
C2PA content credentials aren't enough on their own
AI & Technology

C2PA content credentials aren't enough on their own

C2PA Content Credentials give AI-generated content a signed history, but the metadata is routinely stripped by re-uploads, screenshots, and platform recompression. Here is what the standard actually verifies, where it breaks down in practice, and why an independent, qualified timestamp is worth adding alongside it.

July 21, 2026Read more →