Guide · Software
How to protect your code: copyright and proof of date
Updated November 5, 2026 · 3 min read
ZeFirst in plain wordsWhat ZeFirst proves, and what it doesn't →An app delivered to a client, an algorithm shown to an investor, a library published on GitHub: your code has value, and the day someone claims they wrote it first, you will need to prove otherwise.
Software is protected by copyright
In the United States and the United Kingdom alike, a computer program is protected as a literary work as soon as it is written and original, with no formality. What is protected is the way the program is written, not the idea or the feature: two developers can code the same function, each in their own way.
In the US, registering your code with the Copyright Office remains voluntary, but it is required before suing over a US work, and it is what makes statutory damages possible if done before the infringement. The UK has no register at all.
Patents are a different matter: software “as such” is excluded in the UK and Europe, and US software patents face strict limits. A technical invention implemented by a computer may still be patentable; see our guide on inventions.
Who owns the code?
- You are an employee: code written as part of your job usually belongs to your employer, both in the US (“work made for hire”) and in the UK.
- You are a freelancer or contractor: you generally keep the copyright unless you sign a written assignment. Without a contract that says so, what your client may do with the code quickly becomes a source of dispute: a clear contract is worth it.
- You built it together: the software belongs jointly to those who created it.
Why Git dates are not enough
A Git history tells the story of a project well, but its dates can be changed with one command and a history can be rewritten. Against someone who disputes them, they carry little weight. A hosting platform's dates are stronger, but they belong to a private third party, and nothing is dated until you publish.
How to date your code
With an electronic timestamp, the fingerprint of your code is dated by a third party, then checked by comparison. On a public blockchain, as with ZeFirst, anyone can run that check without relying on us, and your code is never sent anywhere: only its fingerprint is recorded. Details in our guide on timestamping.
- Date an archive of the code at every important version: a .zip of the source (for instance with
git archive), kept exactly as it is. - Or date the commit hash: a small text file with the project name and the commit hash (
git rev-parse HEAD). The hash is computed from the content and the whole history, so dating it proves that this exact version existed. Then keep the repository intact, without rewriting history. - Date before you show it: before a delivery, a demo, a pitch to an investor, an open-source release.
- Remember what surrounds the code: specifications, architecture diagrams, mock-ups, documentation.
With ZeFirst, a proof can also be split into shares between a project's developers, each receiving their own.
Key points
- Your code is protected as soon as it is written; in a dispute, what counts is proof of its date.
- As an employee, your code usually belongs to your employer; as a freelancer, it stays yours unless you assign it in writing.
- Git dates can be changed: date an archive or the commit hash at every version, before you show it.
This guide gives general information, which varies from one country to another. It does not replace the advice of a lawyer or a patent or trademark attorney for your situation.