Software License Agreement in France: Template, Key Clauses and Local Law (2026)

A software licence agreement in France is a contract where the rights holder lets a user run software on defined terms, without transferring ownership of the code. In France software is protected by copyright (droit d'auteur) under the Intellectual Property Code (Code de la propriete intellectuelle), which lists software and its preparatory design material among protected works in Article L. 112-2. Because the licence turns on copyright, French law gives users certain rights that a contract cannot take away, and that is the first thing to get right. This page explains what belongs in a French software licence, the local-law points that change the draft, and a simple outline. It is general information, not legal advice. ## How French copyright shapes a software licence The author's economic rights in software are set out in Article L. 122-6 of the Intellectual Property Code: the right to reproduce, adapt and distribute the program. A licence grants a permission against those rights rather than selling the code. Two points follow: - Transfers must be written and specific. Under Article L. 131-3, any assignment of author's rights must state each right transferred, and its scope, purpose, territory and duration. A loosely worded grant is read narrowly against the licensor.

• Some user rights cannot be excluded. Article L. 122-6-1 gives the lawful user rights that survive contrary contract terms: to make a back-up copy, to observe and study the program to understand its ideas, and to decompile it for interoperability within limits. You cannot draft these away. France also limits moral rights for software: under Article L. 121-7 the author generally cannot oppose adaptation within the agreed limits or exercise a right of withdrawal, which gives licensors more stability than for other works. ## Key clauses in a French software licence ### Grant and scope State the licence type (non-exclusive is usual), permitted use, number of users or installations, territory and term. Keep it precise, because Article L. 131-3 means ambiguity favours the user. ### Restrictions Set out what is not allowed, but respect the Article L. 122-6-1 user rights on back-up, study and decompilation for interoperability. ### Delivery, acceptance and maintenance Cover how the software is delivered, any acceptance testing, and whether maintenance, updates and support are included or sold separately. ### Intellectual property and ownership Confirm the licensor keeps ownership, license any third-party and open-source components, and flag open-source obligations. ### Warranties Address conformity, the warranty against hidden defects and the guarantee against eviction (third-party IP claims) that apply under general French contract law. ### Liability and caps Caps are valid between businesses, but Article 1170 of the Civil Code strikes any clause that empties an essential obligation of substance, and you cannot exclude liability for fraud or gross fault. ### Audit and compliance If you allow licence audits, define scope, notice and how over-use is charged. ### Term, termination and effect Cover termination for breach and what happens to copies and data on exit. ### Data, governing law and language Add Article 28 GDPR terms if personal data is processed. B2B contracts may be in English, but the Toubon Law requires French in consumer and employment contexts, and a court can require a translation. ## A simple software licence outline for France 1. Parties and definitions

2. Grant, scope and restrictions
3. Protected user rights (back-up, study, interoperability)
4. Delivery and acceptance
5. Maintenance, updates and support
6. Ownership and third-party or open-source components
7. Warranties and the hidden-defect and eviction guarantees
8. Liability, caps and carve-outs
9. Audit and over-use
10. Term and termination
11. Data protection if relevant
12. Governing law, language and disputes ## Common mistakes to avoid - Drafting restrictions that try to override the Article L. 122-6-1 user rights, which are unenforceable.

• A vague grant that fails the Article L. 131-3 specificity rule and is read narrowly against the licensor.
• Ignoring open-source components bundled into the product.
• A blanket liability exclusion that falls foul of Article 1170 or the fraud and gross-fault carve-outs. ## Keeping licence terms and entitlements straight Software licences accumulate: different editions, user counts, maintenance terms and audit rights, often amended over years, and the entitlement that was granted is easy to lose track of. Holding each licence and its amendments in one workspace, with the grant, user limits, maintenance scope and audit terms visible and the renewal dates tracked, makes compliance and renewals far easier to manage. Adira is one AI workspace to draft, review, track and govern contracts; its depth outside India is on its roadmap, so verify French coverage before relying on it for a France-governed licence. More at Adira.