How to Prove IP Ownership in a Copyright Dispute (2026)
Legal Compliance

How to Prove IP Ownership in a Copyright Dispute (2026)

In a copyright dispute, the outcome turns on who can prove creation date. Here is exactly what EU and Swiss courts accept, and how to build court-admissible proof before a dispute arises.

S
Swiss Trust Layer Legal Team· Trust & Compliance
·June 16, 2026· 9 min read

In February 2026, a Geneva-based brand design studio delivered a full visual identity to a SaaS startup three days before the service contract was countersigned. The startup folded four months later. Its liquidators assigned all company-developed IP to a buyer, including the studio's logo system. The studio had version files, Slack threads, and a PDF invoice. The buyer's lawyers had one question: prove the studio made it before the contract date. The studio could not. The dispute cost CHF 210,000 to settle.

If you need to prove IP ownership in a copyright dispute, the answer turns on one question: can you prove when you created the work, and what it contained at that exact moment? This guide explains what evidence EU and Swiss courts accept, why digital timestamps matter, and the fastest way to create legally admissible proof of creation.

What Courts Actually Need to See

In a copyright dispute, you are not required to register your work to have rights (under Berne Convention Art. 5, copyright arises at creation, without formality). But unregistered rights create a practical problem: you must prove creation date and authorship yourself, without a registration certificate to rely on.

Courts in EU jurisdictions and Switzerland accept the following as evidence of IP ownership:

  • Dated digital records: emails, version-controlled repositories, cloud storage with verifiable timestamps
  • Qualified electronic timestamps: issued by a Qualified Trust Service Provider (QTSP) under eIDAS, carrying a statutory presumption of accuracy under eIDAS Art. 41
  • Notarised documents: timestamped by a notary, expensive and slow
  • Registered mail: date-stamped by postal service (contested in many jurisdictions)
  • Witness testimony: weakest form, easily challenged

Of these, only a QTSP-issued qualified electronic timestamp carries the Art. 41 legal presumption: the court must accept the timestamp as accurate unless the opposing party proves otherwise. Every other form of evidence can be challenged, and you bear the burden of proving it.

The Burden of Proof Problem

In copyright disputes without a qualified timestamp, the evidentiary burden falls on you. This means:

  1. You must prove your work existed before the alleged infringement
  2. You must prove the work was yours and not derived from the other party's work
  3. You must prove the date you claim, not just assert it

Opposing counsel will challenge informal timestamps. Email timestamps can be altered before sending. Server logs can be fabricated. Cloud storage dates can be rolled back by account administrators. Git commits can be rewritten, though harder to do undetectably.

A QTSP-issued qualified timestamp under eIDAS Art. 42 cannot be successfully challenged on any of these grounds. It is cryptographically bound to a UTC time source, issued under a supervised QTSP key pair, and verifiable independently by the court without relying on your servers or accounts.

Step-by-Step: How to Prove IP Ownership

Step 1: Seal the Work at Creation

The moment you complete a creative work (a design, a document, source code, a manuscript, a musical composition), seal it. Do not wait until a dispute arises. A timestamp created after a claim is filed provides much weaker protection.

What to seal: the final file, plus any version history that establishes your creative process. A PDF export of a design plus the source .fig or .ai file creates a stronger combined record than either alone.

Step 2: Use a QTSP-Backed Platform

Upload your file to a platform backed by a QTSP. Swiss Trust Layer works with Swisscom Trust Services, an accredited trust service provider under ZertES (Switzerland) and recognised under the eIDAS framework for cross-border EU admissibility.

The platform:

  1. Hashes your document (SHA-256)
  2. Sends the hash to the Swisscom QTSP for qualified timestamping
  3. Applies a PAdES-compliant digital seal
  4. Issues a certificate linked to your document hash

You receive a sealed document and a verification certificate. Anyone, including a court, can verify independently via our public verification page without creating an account.

Step 3: Store the Certificate and Original

Keep three things:

  • The original unsealed file (proves content at time of sealing)
  • The sealed document (carries the qualified timestamp and digital seal)
  • The verification certificate (links the seal to the QTSP trust chain)

Store these in at least two separate locations (cloud and local). Courts expect you to produce originals. If you cannot produce the original file that matches the hash in the certificate, the certificate's probative value is diminished.

Step 4: Document Your Creative Process

A qualified timestamp proves when and what. It does not prove who created the work. To prove authorship, keep records of the creative process:

  • Draft iterations with dates
  • Communications with collaborators or clients discussing the work
  • Software version history (Git, Figma history, Photoshop saves)
  • Invoices or briefs referencing the work before the alleged infringement

These records, combined with a qualified timestamp, form a complete evidentiary package.

Step 5: If a Dispute Arises

Contact an IP lawyer before filing any claims or responding to infringement notices. Your lawyer will need:

  • The sealed document with its certificate
  • Your chain of creation evidence (drafts, git history, communications)
  • The specific works you believe were infringed
  • Any evidence of access by the infringing party (did they see your work before creating theirs?)

For Swiss disputes, note that ZertES-qualified seals are directly admissible under Swiss contract law (ZertES Art. 2). For EU cross-border disputes, the eIDAS Art. 41 presumption applies automatically in all 27 member states.

What Would Have Happened

If the Geneva studio had sealed the final brand files with a qualified timestamp on the day of delivery, the liquidators' lawyers would have faced a different situation entirely. The QTSP-issued certificate would have established, with statutory presumption under eIDAS Art. 41, that those exact files existed on that exact date and in that exact form. The buyer could not have challenged the timestamp without proving QTSP failure. There would have been nothing to settle.

Common Mistakes That Weaken Your Case

Timestamping after the dispute starts. A timestamp created after the other party's work appears is legally suspicious. Courts may dismiss it entirely if the timing is too convenient.

Using blockchain timestamps. Public blockchain timestamps are not qualified under eIDAS (Art. 42). They carry no statutory presumption and are routinely challenged. See our blockchain vs qualified timestamp comparison.

Sealing only the final version. If the other party can show their work predates your sealed version, you may lose even if you created the underlying ideas earlier. Seal drafts and working files at key milestones.

Relying solely on email timestamps. These are easily fabricated and frequently challenged. Use them as supporting evidence, not primary proof.

What Swiss and EU Courts Accept (Summary Table)

Evidence TypeLegal PresumptionChallengeableRecommended
QTSP-issued qualified timestampeIDAS Art. 41 statutory presumptionNo, opponent must rebutPrimary
ZertES-qualified seal (Switzerland)ZertES Art. 2 legal equivalenceNoPrimary (CH)
Notarised documentNotary trustDifficultSlow, costly
Registered copyrightRegistration certificateRarelyNot available all jurisdictions
Email timestampNoneYes, easilySupporting only
Git commit timestampNoneYes, rewritableSupporting only
Blockchain timestampNoneYes, no QTSPNot recommended
Witness testimonyNoneYesWeakest

The Geneva studio's situation is not unusual. A CHF 5 seal at delivery would have ended the dispute before it began. The settlement cost CHF 210,000. Average Swiss IP disputes run between CHF 150,000 and CHF 400,000 (Swiss Arbitration Association). The math is consistent: qualified timestamps cost CHF 5 per document; disputes settled without them cost orders of magnitude more.

Seal Your Work with a Qualified Timestamp

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

The qualified signature workflow, start to finish
Legal

The qualified signature workflow, start to finish

A qualified electronic signature involves identity verification, signing ceremony, PAdES application, RFC 3161 timestamping, and public verification. Each step serves a specific legal purpose. This is what the process looks like from upload to verified certificate.

July 19, 2026Read more →
5 documents Swiss businesses should never sign with a basic e-signature
Legal

5 documents Swiss businesses should never sign with a basic e-signature

Swiss law specifies document types where only a qualified electronic signature carries the legal weight of a handwritten signature. Using a simple or advanced e-signature on these documents creates an enforceable gap that surfaces in disputes. Here are the five categories that matter.

July 18, 2026Read more →
DocuSign vs SealMyIdea: where a visual signature isn't enough
Legal

DocuSign vs SealMyIdea: where a visual signature isn't enough

DocuSign provides advanced and simple electronic signatures. For real estate, IP transfers, fiduciary mandates, and employment contracts in Switzerland, only a qualified electronic signature under ZertES Art. 11 carries legal presumption. This is the gap DocuSign cannot close.

July 17, 2026Read more →
For agencies: prove you authored the work and get clean client sign-off
Legal

For agencies: prove you authored the work and get clean client sign-off

Creative and digital agencies lose IP disputes because they cannot prove creation date or obtain legally binding client acceptance. A qualified electronic signature for client sign-off, combined with timestamped delivery, creates the complete audit trail that courts recognise.

July 16, 2026Read more →
Blockchain proves a file existed. It doesn't prove a court will accept it.
Legal

Blockchain proves a file existed. It doesn't prove a court will accept it.

A blockchain timestamp records that a file existed at a point in time. It carries no legal presumption under eIDAS or ZertES. A qualified electronic timestamp issued by an accredited QTSP does.

July 15, 2026Read more →