Why "Automatic Copyright" Is No Longer Enough in 2026

In March 2025, a Basel-based UX agency delivered a complete brand identity to a Series A startup before the service agreement was countersigned. Two weeks after delivery, the startup's incoming in-house designer claimed the brand work had been developed internally. The agency had no qualified timestamp on any deliverable. The startup's lawyers asked one question: prove you made it first. The agency pointed to a Dropbox folder. The startup's counsel said file modification dates are trivially manipulable. The agency was not wrong about who created the work. They could not prove it.

The legal system says your copyright exists from the moment of creation. That is the promise of the Berne Convention, enacted in 181 member states. It sounds reassuring. It is not sufficient. Courts do not award rights to the party with the most compelling claim of ownership. They award them to the party with the best evidence. And in 2026, the gap between holding a copyright and being able to enforce it has never been wider or more expensive to discover.

If the agency had sealed the brand identity files with a ZertES-qualified timestamp before the first client delivery, the answer to the startup's lawyers would have been immediate. The SHA-256 hash of every deliverable, anchored via Swisscom Trust Services to a certified timestamp, would have created an independently verifiable record: this exact file, in this exact form, existed before the client's in-house designer joined the company. The claim of internal development would have been falsifiable in minutes, not months.

Three distinct threats are driving this gap. Each is accelerating. Each is solvable.

Threat 1: AI Scraping and the Training Data Dispute

Large language models, image generators, music composition tools, and code assistants are trained on enormous datasets. Some of that data is licensed. A great deal is scraped from publicly accessible sources. And some enters training datasets through the terms of service that users accept when they upload files to cloud platforms, collaboration tools, and sharing services.

The problem is not theoretical. When an AI tool generates output that closely resembles your work (a melody, a visual style, a code pattern, a written voice), establishing that your original preceded the AI output requires proving when your work existed in its current form.

Consider a music producer who shares an unreleased demo with a streaming platform via their standard upload flow. Months later, an AI-generated track is released that mirrors the melodic structure of that demo. The producer believes their work was scraped. The platform's lawyers say their tool trained on licensed data only. Without a certified timestamp predating the AI output, the producer has no credible prior art, only a belief and a Dropbox folder with manipulable file dates.

A cryptographic timestamp issued by an accredited certification authority does what no file system date can do: it creates an external, independently verifiable record that a specific file existed in a specific form at a specific moment. That record cannot be altered retroactively.

Threat 2: Collaborative Work and the Contribution Dispute

Modern creative and technical work is rarely solo. Beats, hooks, visual concepts, software architectures, and business methodologies circulate via WhatsApp, Dropbox, WeTransfer, and shared cloud drives long before contracts are signed or contributions are formally defined.

This is not a problem when a project fails. It becomes a critical problem when a project succeeds.

The pattern is consistent: two people collaborate informally. The work gains commercial value: a sync deal, an acquisition offer, a licensing agreement. Both parties now have financial incentives to claim a larger share. Without contemporaneous documentation, the dispute becomes a contest of memories and versions of events, resolved by negotiation or litigation, with the better-documented party holding the advantage regardless of what actually occurred.

A startup with three founding engineers and no sealed IP baseline faces exactly this dynamic when a fourth employee claims they contributed the core algorithm before leaving. The company cannot prove what existed before that employee joined. The dispute delays a funding round by six months and costs CHF 40,000 in legal fees to settle, even though the claim had no merit.

Sealing the technical architecture document before each new collaborator joins creates a definitive before-and-after record. It does not prevent disputes. It makes them straightforward to resolve.

Threat 3: Investor and M&A Due Diligence

The third threat is not adversarial in origin, but it is equally consequential. Investors, acquirers, label groups, and strategic partners now treat IP provenance as a structured diligence item, not a checkbox, but a forensic audit.

The question is no longer simply "do you own this?" It is: "Can you prove the ownership chain from creation to today, with documentation that would survive challenge?"

An architecture firm with a strong portfolio but no version-sealed design history faces this when a property developer offers to acquire their IP for licensing. The developer's lawyers want to verify independent creation for each design series, not the firm's word, but timestamped evidence. Without sealed records, the firm's counsel must reconstruct provenance from emails, file metadata, and testimony. The process takes eight weeks and reduces the acquisition value by 20%.

Investors running IP audits are looking for the kind of clean, independently verifiable evidence chain that a sealed version history provides. It works as legal protection, and it also serves as a data room asset that directly supports valuation.

Why File System Timestamps Are Not Evidence

The instinct to rely on a timestamp as proof is correct. The problem is that most available timestamps carry no legal weight.

File system dates (the creation and modification times shown by your operating system) are trivially manipulated. Email send dates can be spoofed. Version control commit timestamps, while harder to forge in isolation, are internal records that a sophisticated legal challenge can undermine. Screenshot dates are easily falsified.

What courts require, under ZertES in Switzerland, under eIDAS in the EU, and under analogous frameworks globally, is a timestamp issued by an accredited, independent certification authority using cryptographic methods that make retroactive alteration detectable. A timestamp that, by law, carries a presumption of accuracy that the challenger must rebut.

Swisscom Trust Services is simultaneously a BAKOM-accredited ZertES certification service provider (ZDA) and an eIDAS-qualified trust service provider (QTSP) listed on the EU Trust List. A timestamp issued via Swisscom carries legal presumption in Switzerland and all 27 EU member states. Every seal created through Swiss Trust Layer is anchored to Swisscom's infrastructure, satisfying both frameworks with a single document.

What You Can Do Today

The solution is straightforward and available now. Swiss Trust Layer gives you court-admissible, cryptographic proof of creation in under two minutes per file.

The process: upload any file to swisstrustlayer.com: music session, design file, code, document, image. The file is not stored. Only its SHA-256 cryptographic hash is processed. Swisscom Trust Services anchors that hash to a certified timestamp. You receive a PAdES-compliant certificate containing the hash, the timestamp, the Swisscom issuer chain, and your identity.

Anyone (a lawyer, a judge, an investor, an opposing party) can verify your seal at swisstrustlayer.com/validate without login and without contacting you. The system confirms: this exact file existed in this exact form at this certified time.

You do not need to seal everything. You need to seal the right things, at the right moments: before you share them with a collaborator, upload them to a platform, or present them to a partner. The moment work leaves your exclusive control, the window for uncontested prior art begins to close.

The Math

The Basel agency spent four months in dispute resolution. Legal fees reached CHF 38,000 before a settlement was reached, a settlement that reduced the contracted payment by 30% because the agency could not establish independent creation with the certainty the process required. The law gives you copyright automatically. Proof is a separate step, and it costs. Start at swisstrustlayer.com.

---

See also: ZertES legal proof of authorship · Compliance hub