Use case
Copied code: how to prove who wrote it first
Code is protected by copyright as soon as it's written. But you still need to prove who wrote it, and when.
The situation
One scenario, two outcomes
The same moment, depending on whether the work was timestamped or not.
The trigger
An agency delivers the technical foundation of your product. Three external developers contributed to it.
Without proof
During due diligence (the audit carried out before the acquisition), the buyer asks for the chain of title on the code's rights. The Git history shows commits reattributed during a repository migration, and two of the developers are unreachable. The indemnity clause (the seller's commitment to cover hidden liabilities) gets heavier.
With a certificate
Each delivery was timestamped on receipt, attributed to its author. The chain of title fits on a single page, in a registry with a verifiable date. The matter is resolved in a day.
Is your situation different?
Something went wrong while adapting the scenario. The typical scenario is still shown. You can rephrase your situation and try again.
Adapted scenarioBased on: ""
Automatically generated text, for illustration only, based on the sentence you entered. It describes an evidentiary position (what you could prove, and how). For an analysis suited to your situation, ask a legal professional for advice.
The need
Ownership, contractors, technical audit.
Dating your Git history
A repository's history can be altered: dates rewritten, authors reattributed, branches rebuilt. Timestamping commit or archive fingerprints at regular intervals records this history outside the repository, where it can no longer be rewritten.
Freelancers, agencies, external contributions
A significant share of a startup's code is written by third parties. Attributing each delivery to its author and its date documents the chain of title. This is the first item requested in a technical audit.
Algorithms and models
Model architectures, parameter sets and training pipelines often fall under trade secret rather than patent protection. The certificate dates them without disclosing them, and documents the protection measures taken.
→Fingerprint of a commit, a release, or a full archive
→Automatable via API (a direct connection between software tools) in your CI/CD pipeline
→Contributions attributed to each developer
→Encrypted transfer, with file storage available to subscribers
If your code is copied
From proof to defense
Every day
Every version is dated
Archives, releases, commit fingerprints, deposited by hand or through the API in your CI pipeline.
Discovery
You call a legal expert
Covéa Protection Juridique's legal experts answer by phone. You quickly learn whether the situation is a dispute and how to report it.
Assessment
The case is qualified
The preliminary assessment sets out what is protected, who owns it and what each deposit proves.
Conciliation
An amicable solution first
The legal experts seek removal, regularization or a negotiated agreement. Many cases are settled at this stage.
Proceedings
A lawyer if needed
Software falls under copyright, covered on every plan. Your defense costs are covered up to €5,000 per dispute, €10,000 on the Professional plan.
Frequently asked questions
How do I protect software source code?
Source code is protected by copyright from the moment it is written. To enforce it, you need to prove who wrote it, and when. Regularly timestamp archives or versions of your code on Ipocamp, because Git history is easy to rewrite.
Does my code have to leave my company?
With the API, or with the agent offered as an option to large accounts, the fingerprint is computed in your infrastructure and only the fingerprint is sent. The fingerprint identifies the file without revealing its content. For a deposit from the website, the file is transferred encrypted, and subscribers can choose to keep it stored.
Who owns code written by a freelancer?
Under French law, code written by an employee as part of their duties belongs to the employer. Code written by a freelancer or an agency stays with its author unless rights are transferred in writing. Timestamp each delivery with its author, and attach it to your transfer agreement.
When does the legal protection apply?
After a three-month waiting period, for a creation timestamped by Ipocamp, if your subscription has stayed active without interruption since that timestamp. So subscribe before you share your work. The exact terms are in the Covéa information notice.
For an answer tailored to your case, talk to an expert: this page describes a typical situation, and yours has its own specifics.
Contact usTorn between several of these situations?
Describe what you want to protect and when. We'll open the case that fits.