
France
Fully legal
Overview
Intro & Key Facts
Quick Summary
Practical Usage
Permitted Document Types
Commercial contracts
Employment agreements
NDAs
Service agreements
Software licenses
Invoices and purchase orders
Lease agreements
Insurance contracts
Banking documents
Procurement documents (with QES)
Restricted Document Types
Wills and codicils
Notarial deeds (actes notariés), including real estate transfers
Family law documents (marriage, divorce, adoption, inheritance)
Personal suretyships by non-professionals
Commercial instruments (promissory notes)
Public procurement contracts (require QES or AES with a qualified certificate)
Common Exclusions
Authentication Required
SES: No specific authentication required beyond email delivery.
AES: Signer must be uniquely identifiable through authentication data under their sole control (email + access code, SMS verification, or knowledge-based authentication).
QES: Requires a qualified certificate issued by an ANSSI-certified QTSP, with identity verification.
Restrictions
Signing Workflow Controls
Generally Permitted
Time-limited signature windows.
Sequential signing order.
Mandatory field completion.
Document expiration dates.
IP-based access restrictions.
Password-protected envelope access.
SMS verification codes.
Attachment requirements.
May Require Special Handling or Exclusions
Restrictions that prevent signers from reviewing the complete document before signing.
Restrictions that obscure material terms.
Blanket prohibitions on retaining personal copies.
Requirements for specific hardware or paid software to complete signing.
Legal Requirements
France E-Signature Law Explained
Legal Frameworks
Regulatory Bodies
Minimum Retention
Commercial contracts: 10 years (Code de commerce L.123-22)
Civil contracts: 5 years (Civil Code Art. 2224)
Employment records: 5 years after termination
Tax-related documents: 6 years
Consumer contracts: 2 years from delivery
Retention Notes
Data, Privacy & Cross-Border
Data Privacy and Compliance France
Privacy Frameworks
GDPR (direct application as EU member state) + Loi Informatique et Libertés (French Data Protection Act, updated 2018)
Privacy Compliance Status
Firma.dev processes data as a processor under GDPR. Data Processing Agreement available. EU-only hosting (AWS Paris) ensures no international transfers for standard operations. CNIL registration not required for standard e-signature processing.
Privacy Notes
Collect only data necessary for signature validity (name, email, signature image, IP, timestamps). Inform signers of data processing via privacy notice. Define retention periods in your DPA. Respond to data subject requests within 30 days. Consider DPIA for high-volume or sensitive document processing.
Data Residency
Adequacy Decision
France is an EU member state, so GDPR adequacy decisions apply for outbound transfers. Current adequacy covers:
Andorra
Argentina
Canada (commercial organizations)
Faroe Islands
Guernsey
Israel
Isle of Man
Japan
Jersey
New Zealand
South Korea
Switzerland
UK
Uruguay
US (Data Privacy Framework participants only)
Cross-Border Transfers
Unrestricted within EU/EEA. For non-EU transfers: Standard Contractual Clauses, Binding Corporate Rules, or adequacy decisions required per GDPR Chapter V. EU-US Data Privacy Framework provides adequacy for US transfers.
Residency Notes
Standard commercial data: EU hosting sufficient. Health data (données de santé): requires HDS-certified hosting. Banking data: may require specific certifications. Public sector: may have France-only requirements. Firma.dev's AWS Paris (eu-west-3) region satisfies all standard commercial requirements.
Maximum Retention
GDPR storage limitation principle: retain personal data only as long as necessary for the purpose. For e-signatures, this typically means the contract validity period plus statutory retention requirements plus limitation period for potential disputes. Delete or anonymize after.
Industry Compatibility
E-Signatures by Industry in France
Fully Supported Industries
General Commercial
SaaS Software
HR Tech Employment
Education/Edtech
Construction
Supported with Agreement
Healthcare
Life Sciences/Pharma
Insurance
Financial Services/Fintech
Legal Tech
Real Estate Tech
Should Consult Counsel
Government
Industry Matrix Notes
Most B2B commercial use cases work with SES/AES. Healthcare and financial services may need additional compliance measures (HDS certification, PVID identity verification). Government contracts require QES, which is outside Firma.dev's current scope. Real estate transactions involving notarization also require QES.
General Commercial
Standard B2B contracts, vendor agreements, NDAs, purchase orders, invoices, and service agreements all work with SES/AES under French commercial law. Article L.110-3 of the Commercial Code allows proof by any means in commercial matters, making electronic signatures fully valid between businesses. No special requirements beyond reliable signer identification.
SaaS Software
SaaS companies can use SES/AES for all B2B contracts in France: software licenses, subscription agreements, API terms of service, MSAs, and DPAs. Freedom of form under French commercial law means electronic signatures are fully valid. Firma.dev's API-first approach fits naturally into software onboarding flows.
Healthcare
Healthcare organizations can use SES/AES for most administrative documents, but HDS (Hébergeur de Données de Santé) certification is required for hosting health data. AES or QES recommended for patient consent forms. Firma.dev's EU hosting (AWS Paris) supports HDS-compliant workflows when paired with certified infrastructure.
Life Sciences/Pharma
Clinical trial agreements, CRO contracts, and research collaborations work with SES/AES. Documents requiring GxP compliance may need enhanced audit trails. ANSM (Agence nationale de sécurité du médicament) regulated submissions may have specific electronic signature requirements. Quality agreements between manufacturers should specify signature standards.
Insurance
Standard insurance policies, broker agreements, and B2B service contracts work with SES/AES under French commercial law. Certain regulated or consumer-facing products may call for enhanced identity verification, and AES is the safer default wherever the signer's identity carries evidentiary weight. Retain signed policies together with their full audit trail in line with commercial retention periods.
Financial Services/Fintech
Financial services contracts generally work with SES/AES under French commercial law. High security standards apply for customer-facing documents, and AML/CFT compliance may require PVID-certified identity verification for certain transactions. Most B2B fintech agreements work seamlessly with Firma.dev.
HR Tech Employment
Employment contracts, offer letters, NDAs, and HR policy acknowledgments all work with SES/AES under French labor law. No special signature requirements for standard employment documentation. Retention: keep employment contracts for 5 years after termination.
Legal Tech
Engagement letters, client agreements, NDAs, and vendor contracts all work with SES/AES. Court filings and certain regulated procedures require QES issued by an ANSSI-certified QTSP, which sits outside Firma.dev's current scope, so law firms should confirm the requirement matter by matter. Legal tech platforms embedding signing into client onboarding are well served by SES/AES.
Real Estate Tech
Residential and commercial lease agreements can be signed with SES/AES. Property conveyances requiring notarization must use QES. Firma.dev works well for lease agreements, property management contracts, and related B2B documents.
Education/Edtech
Enrollment agreements, student contracts, staff employment documents, and supplier agreements work with SES/AES. Nothing in standard education administration requires QES. Edtech platforms can embed signing directly into institutional onboarding, and Firma.dev's EU hosting supports GDPR-aligned handling of student records.
Construction
Construction contracts, subcontractor agreements, change orders, and project documentation work with SES/AES. Public works contracts (marchés publics) require QES. Retain signed documents for 10 years per construction liability periods (garantie décennale). Consider timestamping for dispute resolution.
Government
Public procurement contracts require QES or AES with qualified certificate per the March 2019 Decree. This is outside Firma.dev's current scope (SES/AES only). Government contractors should use ANSSI-certified QTSPs for public sector work.
How we works
How Firma.dev Works in France
Firma.dev Supports
Firma.dev supports SES and AES workflows, covering the vast majority of B2B commercial use cases in France.
Firma.dev supports SES and AES workflows, covering the vast majority of B2B commercial use cases in France. The platform provides:
Signer identification: Email-based authentication with optional SMS verification
Tamper-evident documents: Cryptographic sealing ensures any modification after signing is detectable
Complete audit trails: Every action is timestamped and logged
EU data residency: All data hosted in AWS Paris
For B2B software agreements, SaaS subscriptions, employment contracts, NDAs, and vendor agreements, Firma.dev's signature level meets French legal requirements.
Firma.dev's API-first design means you can embed signing directly into your application. French companies using Customer Workspaces get isolated environments for each customer, with templates and envelope usage tracked separately.
Legal Details
France's e-signature framework combines EU regulation with national civil code provisions. The eIDAS Regulation (No. 910/2014) provides the overarching structure, establishing three signature levels and ensuring cross-border recognition throughout the EU.
The French Civil Code, specifically Articles 1366-1367, defines electronic signatures domestically. Article 1367 is particularly important: it grants only Qualified Electronic Signatures the presumption of reliability. QES is automatically assumed valid unless the challenging party proves otherwise. SES and AES don't get this presumption, but they remain fully admissible in court if the relying party can demonstrate the signature process was reliable.
Decree No. 2017-1416 specifies technical requirements for a signature to be considered reliable, linking back to eIDAS definitions. For commercial contracts between businesses, Article L.110-3 of the Commercial Code allows proof "by any means," which strengthens the position of SES/AES in B2B disputes.
Signature Types Recognized
Simple Electronic Signature (SES): Any data in electronic form attached to or logically associated with other data, used by a signatory to sign. Valid for most commercial contracts.
Advanced Electronic Signature (AES): Must be uniquely linked to the signatory, capable of identifying them, created using data under their sole control, and linked to the signed data so any change is detectable. Firma.dev's standard signing flow meets AES requirements.
Qualified Electronic Signature (QES): An AES created by a Qualified Signature Creation Device using a qualified certificate from an ANSSI-certified QTSP. Required for public procurement, notarial deeds, and certain regulated filings.
Recent developments
E-Signature Landscape in France: 2026
Court of Cassation ruling (March 13, 2024, n° 22-16.487): Confirmed that scanned signatures do not constitute reliable electronic signatures under Art. 1367 of the Civil Code. A scanned image of a handwritten signature lacks the presumption of validity. Businesses should use proper e-signature solutions with authentication and audit trails.
eIDAS 2.0 (Regulation 2024/1183): Entered into force May 2024 with phased implementation. Every EU member state must make at least one compliant EU Digital Identity Wallet available to citizens by December 31, 2026. Mandatory acceptance by relying parties follows in November 2027. Existing SES/AES methods remain fully valid throughout and after the transition.
INPI QES adoption (2025): The French IP Office now accepts itsme QES for business modification filings via Guichet Unique, signaling growing QES infrastructure in France for regulated filings.
Sources
eIDAS Regulation (EU) No 910/2014: https://eur-lex.europa.eu/eli/reg/2014/910/oj/eng
eIDAS 2.0 (Regulation 2024/1183): https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/915931811/The+European+Digital+Identity+Regulation
French Civil Code Art. 1366-1367 (Legifrance): https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032042176
Decree No. 2017-1416 on electronic signatures: https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000035720269
Court of Cassation, Chambre commerciale, 13 March 2024 (n° 22-16.487): https://www.legifrance.gouv.fr/juri/id/JURITEXT000049291099
Art. L.110-3 Commercial Code (proof by any means): https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000006219131
CMS Expert Guide (France): https://cms.law/en/int/expert-guides/cms-expert-guide-to-e-signatures-in-commercial-contracts/france
ANSSI Trusted List: https://www.ssi.gouv.fr/
CNIL: https://www.cnil.fr/en


