SaaS Subscription Agreement in France: Template, Key Clauses and Local Law (2026)

A SaaS subscription agreement in France is a service contract (contrat de prestation de services), not a software sale or a licence of code. The customer never receives the software; it pays to access a hosted service for a term. Under French law this is treated as a form of contrat d'entreprise or louage d'ouvrage within the meaning of Article 1710 of the Civil Code, where one party performs work or a service for another in return for a price. That framing matters, because it shapes the warranties, the standard of performance and the exit rights you should write in. This page covers what belongs in a French SaaS agreement, the local-law points that change the usual draft, and a simple outline. It is general information, not legal advice. ## Is a SaaS subscription agreement enforceable in France Yes. General contract law sits in the Civil Code, reformed by Ordinance No. 2016-131 of 10 February 2016. A contract needs consent, lawful and certain content, and good-faith performance (Article 1104). A click-through or signed order form is valid; there is no special form requirement for a B2B SaaS deal. Watch two rules that bite on standard subscription terms: - Significant imbalance. Article 1171 of the Civil Code treats as unwritten any non-negotiated clause in a standard-form contract that creates a significant imbalance. Article L. 442-1 of the Commercial Code adds a parallel business-to-business rule with damages. Vendor terms of service are prime candidates, so avoid clauses that are plainly one-sided.

• Automatic renewal. If you sell to consumers or, in some cases, small professionals, the Chatel rules in the Consumer Code (Articles L. 215-1 and following) require you to remind the customer of the window to refuse a tacit renewal. For pure B2B this is lighter, but renewal and notice mechanics should still be explicit. ## Key clauses in a French SaaS subscription agreement ### Grant of access and restrictions State that the customer gets a non-exclusive right to access the service for the term, define authorised users, and set acceptable-use limits. There is no transfer of the software itself. ### Service levels and the standard of performance French law distinguishes an obligation of means from an obligation of result. Availability commitments and an SLA with credits clarify which standard applies and reduce argument later. ### Fees, renewal and price review Set the subscription fee, the billing cycle, any usage charges and how prices change on renewal. If you serve consumers, respect the Chatel renewal-reminder rules. ### Data protection Where the provider processes personal data for the customer, Article 28 of the GDPR requires a data processing agreement, supervised in France by the CNIL under the amended Law No. 78-17 of 6 January 1978 (Loi Informatique et Libertes). Address hosting location and any transfers outside the EEA. ### Security and confidentiality Describe the security posture (encryption in transit and at rest, access controls) and keep confidentiality mutual. ### 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. A total blackout of liability for downtime is risky. ### Reversibility and data return Build in an exit plan: return or export of customer data in a usable format, and a defined assistance period. French customers increasingly expect a reversibility clause. ### Governing law, language and disputes B2B contracts may be in English, but the Toubon Law (Law No. 94-665 of 4 August 1994) requires French in consumer and employment contexts, and a French court can require a translation. ## A simple SaaS subscription outline for France 1. Parties and definitions

2. Grant of access, users and restrictions
3. Service levels and support
4. Fees, billing and renewal (Chatel rules if B2C)
5. Customer data and the Article 28 processor terms
6. Security
7. Confidentiality
8. Warranties and standard of performance
9. Liability, caps and carve-outs (Articles 1170, 1231-5)
10. Term, suspension and termination
11. Reversibility and data export
12. Governing law, language and disputes ## Common mistakes to avoid - Treating SaaS as a software licence; in France it is a service contract.

• A blanket liability exclusion for outages, which risks being struck under Article 1170.
• Ignoring the Chatel renewal reminder when any customers are consumers.
• No reversibility clause, leaving the customer unable to get its data out cleanly. ## Keeping subscription terms under control SaaS portfolios drift: renewal dates, price-review triggers, data-processing terms and reversibility promises end up scattered across order forms and amendments. Holding the subscription agreement, its data processing terms and its key dates in one workspace, with per-clause risk visible and renewals tracked, makes the relationship easier to govern on both sides of the table. 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 deal. More at Adira.