Service Provider Obligations for Electronic Signature in France

Introduction

Deploying an electronic signature solution in France is not something you can improvise. Behind every qualified or advanced signature lie dozens of legal obligations incumbent upon the trust service provider (TSP). eIDAS Regulation, GDPR, general security framework, ETSI standards… the regulatory framework is both dense and evolving. For using enterprises, understanding these legal obligations regarding electronic signature service providers in France, eIDAS and GDPR is essential in order to choose a compliant partner and avoid any legal risk. This article details, section by section, all the requirements applicable to TSPs operating on French territory.

---

The status of a qualified trust service provider

What is a TSP under eIDAS?

The eIDAS Regulation No. 910/2014 distinguishes between two categories of service providers: non-qualified trust service providers and qualified providers (QTSPs). The former can offer simple or advanced electronic signature services without mandatory third-party audit. The latter — sole authorised providers to deliver qualified signatures within the meaning of Article 3(15) of eIDAS — must satisfy considerably stricter requirements.

In France, the National Agency for Information Systems Security (ANSSI) fulfils the role of supervisory authority ("Supervisory Body") provided for in Article 17 of eIDAS. It publishes and maintains the French Trust List (TSL — Trust Service List), accessible on its official website, listing qualified providers and their services.

The qualification procedure: audit and compliance

To obtain qualified status, a TSP must necessarily:

• Have its services audited by a Conformity Assessment Body (CAB) accredited by COFRAC in accordance with the EN ISO/IEC 17065 standard.

• Submit the audit report to ANSSI, which rules on the granting of qualified status. This status is re-evaluated at least every 24 months (Article 20 §1 eIDAS).

• Notify ANSSI of any material change in its services within 3 months before the planned modification (Article 21 eIDAS).

Failure to comply with these steps exposes the provider to removal from the TSL and loss of the legal presumptions attached to qualified signature. For client enterprises, using a TSP not listed on the TSL amounts to receiving no presumption of reliability whatsoever.

> To go further on the different signature levels and their legal effects, consult our guide.

---

Technical and security obligations imposed on TSPs

Compliance with ETSI standards

Qualified providers must comply with a set of European standards published by the European Telecommunications Standards Institute (ETSI). The main ones are:

• ETSI EN 319 401: general security requirements applicable to all TSPs.

• ETSI EN 319 411-1 and 411-2: policies and practices of certification authorities issuing qualified signature certificates.

• ETSI EN 319 132: advanced electronic signature formats (XAdES for XML, PAdES for PDF, CAdES for CMS).

• ETSI EN 319 122: CAdES format for qualified signatures.

• ETSI TS 119 431: requirements for remote signature creation services (remote QSCD).

These standards are not optional: the eIDAS Regulation (Annex II, III and IV) explicitly refers to them in order to define the minimum requirements for qualified certificates and signature creation devices.

Management of secure signature creation devices (QSCD)

One of the pillars of qualified signature is the use of a Qualified Signature Creation Device (QSCD) compliant with Annex II of eIDAS. The provider must ensure that:

• The signatory's private key cannot be generated, stored or copied outside the QSCD.

• Key generation takes place exclusively in a certified environment (Common Criteria certification EAL 4+ or equivalent).

• Authentication of the signatory preceding any signature act relies on at least two authentication factors.

In a remote signature context — increasingly common in SaaS environments — these requirements apply to the HSM (Hardware Security Module) server hosting the keys. ANSSI has published specific protection profiles (PP-0075, PP-0076) defining the security criteria to be met.

Business continuity policy and incident notification

Article 19 of eIDAS requires every trust service provider (qualified or not) to:

• Notify the supervisory authority (ANSSI) and, where applicable, the data protection authority (CNIL), within 24 hours of detecting a security breach likely to have an impact on the reliability of the service.

• Maintain a documented and regularly tested business continuity plan.

• Have a formalised information security policy, covering in particular risk management, incident management and backup policy.

These requirements partially overlap with those of the NIS2 Directive (2022/2555/EU), transposed into French law by Law No. 2023-703 of 1 August 2023, which classifies TSPs of significant size among important or essential entities subject to enhanced cybersecurity obligations.

> Learn how your organisation should integrate these constraints into your documentary workflows.

---

GDPR-specific obligations for TSPs

Is the TSP a controller or processor?

The GDPR qualification of the service provider depends on the nature of the service provided:

• When the TSP directly issues qualified certificates on behalf of the signatory and determines the purposes of personal data processing (identity, biometric authentication data), it acts as a controller within the meaning of Article 4(7) GDPR.

• When it integrates its API into a B2B client's platform and processes personal data solely at the instruction of that client, it takes on the role of processor (Article 4(8) GDPR) and must necessarily conclude a DPA (Data Processing Agreement) compliant with Article 28 GDPR.

In practice, most SaaS TSPs cumulate both roles: controller for the management of their own certification infrastructure, processor for the processing of documents and metadata of signatories.

Specific obligations linked to biometric and identity data

The identification and authentication of the signatory — a mandatory step to issue a qualified certificate — often involves the processing of sensitive data: identity document scan, video selfie, facial recognition biometric data. This data constitutes personal data subject to GDPR, or even biometric data falling under Article 9 GDPR (special categories).

The TSP's obligations include:

• Legal basis: explicit consent (Article 9§2a) or, in some cases, legal obligation (Article 9§2b) for the processing of biometric data.

• Limited retention period: according to CNIL guidelines, identification data must be retained for the strictly necessary time, generally aligned with the validity period of the certificate + legal proof period (often 10 years for private deeds, Article 2224 of the Civil Code).

• Mandatory impact assessment (DPIA) (Article 35 GDPR) as soon as the processing is liable to result in a high risk — which is systematically the case for biometrics.

• Processing register (Article 30 GDPR) kept up to date and documenting each category of processing.

International data transfers

Many TSPs host all or part of their infrastructure outside the European Economic Area (EEA). In this case, the appropriate safeguards required by Chapter V of the GDPR apply: adequacy decision, standard contractual clauses (SCCs) of the European Commission or binding corporate rules (BCR). The Schrems II judgment (CJEU, C-311/18, 16 July 2020) recalled that transfers to the United States require a prior country risk analysis.

> To understand the impact of these rules on your organisation, consult our guide.

---

Transparency and information obligations towards users

Certification Policy (CP) and Certification Practice Statement (CPS)

Every TSP issuing certificates is required to publish a Certification Policy (CP) and Certification Practice Statement (CPS), in accordance with ETSI EN 319 411 standard. These documents, freely accessible, detail:

• The procedures for identification and registration of signatories.

• The physical and logical security measures deployed.

• The conditions for certificate revocation and associated timeframes.

• The TSP's responsibilities and liability limitations.

The absence or incompleteness of these documents constitutes a non-conformity that may be noted during the re-qualification audit by the accredited organisation.

Pre-contractual and contractual information to clients

Beyond purely technical obligations, Article 13 of the GDPR requires the TSP to provide to each person whose data is collected clear and accessible information on:

• The identity of the controller and the contact details of the DPO (mandatory for TSPs processing sensitive data on a large scale, Article 37 GDPR).

• The purposes and legal basis of each processing activity.

• The rights of individuals (access, rectification, erasure, portability, opposition).

• Any potential recipients of data (sub-processors, authorities).

This information must appear in the service's privacy policy, in the terms and conditions and, where applicable, in the DPA concluded with professional clients.

Qualified timestamps and audit trail

To guarantee the evidential value over time of signatures, serious TSPs systematically associate a qualified electronic timestamp (Article 42 eIDAS) with each signed deed. This timestamp constitutes legally presumed evidence of the existence of the data on the indicated date. The preservation of the audit trail (identification logs, document fingerprint, signature data) is a factual obligation to allow any subsequent judicial verification.

> Compare market solutions according to these criteria in our guide.

---

eIDAS 2.0: new obligations on the horizon 2026-2027

Regulation eIDAS 2.0 (EU) 2024/1183

Published in the Official Journal of the EU on 30 April 2024, Regulation (EU) 2024/1183 called "eIDAS 2.0" significantly strengthens the obligations of TSPs around three axes:

• The European Digital Identity Wallet (EUDI Wallet): Member States must make available a certified digital identity wallet by 2 November 2026. TSPs will need to integrate their service with this wallet to offer qualified signatures via eIDAS 2.0 identity.

• The management of attribute attestations: eIDAS 2.0 introduces qualified attribute attestations (QEAAs), issued by qualified attestation providers. New audit and qualification procedures will apply.

• The strengthening of supervision: national supervisory authorities (ANSSI for France) see their powers expanded, in particular the ability to conduct surprise audits and impose binding corrective measures within shortened timeframes.

Practical implications for current providers

TSPs already qualified under eIDAS 1.0 will need to carry out progressive compliance adjustments before the deadlines set by the Commission's implementing acts (published or in the process of publication). The main adaptations concern:

• The overhaul of the identification infrastructure to support the EUDI Wallet as a means of authentication.

• The update of CP/CPS to integrate new types of certificates and attestations.

• The strengthening of security requirements for remote QSCDs, with new protection profiles to come.

For client enterprises, this means verifying from today that their service provider has a documented and verifiable eIDAS 2.0 compliance roadmap.

Legal framework applicable to the obligations of electronic signature service providers

The normative chain applicable to electronic signature service providers operating in France is structured on several complementary hierarchical levels.

French Civil Code — Articles 1366 and 1367

Article 1366 of the Civil Code recognises electronic writing as a means of proof equivalent to paper writing, provided that "the person from whom it emanates can be duly identified and it is established and preserved in conditions such as to guarantee its integrity". Article 1367 specifies that electronic signature "consists of the use of a reliable identification process guaranteeing its link with the act to which it is attached". The presumption of reliability benefits qualified signatures within the meaning of eIDAS, reversing the burden of proof in favour of the signatory.

eIDAS Regulation No. 910/2014/EU

This regulation, directly applicable in all Member States, establishes the legal framework for trust services. Its Article 26 defines the conditions for advanced electronic signature; its Article 28 the requirements for qualified certificates; its Annex I details the mandatory content of these certificates. Qualified TSPs benefit from a presumption of compliance with the technical and legal requirements of the Regulation (Article 19§2), which constitutes a major advantage in the event of litigation.

eIDAS 2.0 Regulation — (EU) 2024/1183

Published on 30 April 2024, this amending regulation introduces new categories of trust services (qualified attribute attestations, qualified archiving services) and strengthens supervisory obligations. It repeals and partially replaces Regulation 910/2014, with progressive applicability according to implementing acts of the European Commission.

GDPR — Regulation (EU) 2016/679

The GDPR applies to any processing of personal data carried out within the framework of an electronic signature service. Articles 5 (principles of lawfulness), 6 (legal basis), 9 (sensitive data), 13-14 (information), 28 (sub-processing), 32 (security), 33-34 (breach notification), 35 (DPIA) and 37 (DPO) constitute the most frequently applicable provisions. The CNIL is the competent supervisory authority in France and can impose fines of up to 20 million euros or 4% of annual worldwide turnover (Article 83§5 GDPR).

NIS2 Directive — (EU) 2022/2555

Transposed into French law by Law No. 2023-703 of 1 August 2023, NIS2 classifies significant TSPs among important or essential entities subject to cyber risk management obligations and incident notification to ANSSI within 24 hours (early warning) then 72 hours (complete notification).

ETSI Standards

All EN 319 401, EN 319 411-1/2, EN 319 132, EN 319 122 and TS 119 431 standards constitute the mandatory technical reference for qualification audit. Their non-compliance results in the impossibility of obtaining or maintaining qualified status.

Legal risks in case of non-compliance

A non-compliant provider is exposed to: removal from the French TSL, engagement of its contractual and non-contractual liability, CNIL administrative penalties, NIS2 fines that can reach 10 million euros or 2% of worldwide turnover for important entities and 20 million or 4% of turnover for essential entities, as well as legal recourse by clients who have suffered harm as a result of legally invalid signatures.

Usage scenarios: how enterprises verify their TSP's compliance

Scenario 1 — An industrial group managing 3,000 supplier contracts per year

An industrial group of medium size (SME), active in the manufacture of mechanical equipment, dematerialises all its supplier contracts via a SaaS electronic signature platform. During an internal audit triggered after regulatory evolution, the legal department notes that the retained service provider — initially chosen on price criteria — is listed neither on the French TSL nor on any European TSL. The signatures delivered are "simple" type without robust signatory identification mechanism.

Given the legal risk — the entire set of signed contracts could see their evidential value contested in case of dispute — the company initiates a migration to an ANSSI-qualified TSP. The new solution integrates an advanced signature with qualified certificate, a qualified timestamp and an exportable audit trail. The migration project, carried out in less than 8 weeks, allows retroactively securing new acts and establishing a compliant documentary policy. The legal teams estimate that the litigation risk linked to old contracts remains marginal due to their execution without dispute, but any new signature is now covered.

Observed gains: 60% reduction in potential disputes linked to signature authenticity, and 3.5-day average gain in signature time on complex contracts thanks to workflow validation automation.

Scenario 2 — A law firm of 25 collaborators specialising in corporate law

A law firm wishing to digitalise the signature of mandates, consultations and procedural documents evaluates several service providers. Its assessment grid incorporates the following criteria: presence on the TSL, publication of an accessible CP/CPS, existence of a GDPR-compliant DPA, availability of a contactable DPO and certification of remote QSCDs.

Of five evaluated service providers, only two satisfy all criteria. The firm finally retains a TSP offering natively a qualified signature via remote QSCD, guaranteeing the presumption of reliability of Article 1367 of the Civil Code. Implementation takes 3 weeks, training included. Result: 75% of mandates are now signed in less than 24 hours compared to 5 to 7 days previously (postal sending), and the firm can justify to its clients the level of legal security offered by the solution — a differentiating argument in its commercial proposals.

Scenario 3 — A hospital group of approximately 1,200 beds

A public hospital group wishes to dematerialise employment contracts, internship agreements and partnership agreements with partner healthcare facilities. The sensitivity of the data processed (healthcare data of healthcare personnel, HR data) requires particular vigilance regarding the TSP's GDPR obligations.

The IT Department and the establishment's DPO require: data hosting in France with a healthcare data hosting provider certified HDS (Healthcare Data Hosting provider, certification provided for by Article L.1111-8 of the Public Health Code), no transfer outside the EEA, documented DPIA for the signatory identification processing, and DPA signed before any production deployment.

After selecting a TSP meeting these criteria, the deployment first covers HR contracts (approximately 800 acts per year). The average contract signature time for fixed-term contracts falls from 9 days to less than 48 hours, freeing significant capacity for human resources teams. The establishment thus has complete traceability of the consents collected, audited annually by its DPO.

Conclusion

The legal obligations weighing on electronic signature service providers in France form a demanding normative corpus: eIDAS qualification, GDPR compliance, respect for ETSI standards, NIS2 obligations and imminent adaptation to eIDAS 2.0. For using enterprises, ensuring the compliance of your TSP is not an optional undertaking — it is a sine qua non condition of the evidential value of signed deeds and the protection of signatories' personal data.

Certyneo is an electronic signature service provider designed to meet all these requirements: eIDAS compliance, GDPR by design, sovereign hosting and documented eIDAS 2.0 roadmap. Ready to secure your signatures in full compliance? Contact us and benefit from personalised support from day one.