Data Protected - France
Last updated March 2020
General | Data Protection Laws
National Supervisory Authority
Scope of Application
Sensitive Personal Data
Data Protection Officers
Accountability and Privacy Impact Assessments
Rights of Data Subjects
Transfer of Personal Data to Third Countries
ePrivacy | Marketing and cookies
General | Data Protection Laws
General data protection laws
The General Data Protection Regulation (EU) (2016/679) (“GDPR”).
Law n° 2018-493 of 20 June 2018 “relating to personal data protection” incorporates the GDPR provisions in existing French Law n° 78-17 of 6 January 1978.
For greater clarity, the law has been rewritten via Ordinance n° 2018-1125 of 12 December 2018, which took effect on 1 June 2019 (altogether the “revised French DPA”).
Entry into force
The GDPR has applied since 25 May 2018.
The revised French DPA has retrospective effect and applies from 25 May 2018.
National Supervisory Authority
Details of the competent national supervisory authority
The CNIL acts as the supervisory authority in France.
Commission Nationale de l’Informatique et des Libertés (the “CNIL”)
3 Place de Fontenoy
Tel: 00 33 1 53 73 22 22
Fax: 00 33 1 53 73 22 00
The CNIL will represent France on the European Data Protection Board.
Notification or registration scheme and timing
There is no obligation to notify regulators of any processing under the GDPR. However, controllers and processors must keep a record of their processing and make it available to their supervisory authority on request (subject to limited exemptions).
The revised French DPA maintains the existing obligation to declare processing relating to health data to the CNIL.
Exemptions to notification
Scope of Application
What is the territorial scope of application?
The GDPR applies to the processing of personal data in the context of the establishment of a controller or processor in the EU.
It also contains express extra-territorial provisions and will apply to controllers or processors based outside the EU that: (i) offer goods or services to individuals in the EU; or (ii) monitor individuals within the EU. Controllers and processors caught by these provisions will need to appoint a representative in the EU, subject to certain limited exemptions.
The European Data Protection Board has issued Guidelines on the territorial scope of the GDPR (3/2018).
Without prejudice of the above, the revised French DPA applies to processing of personal data carried out in the context of the activities of an establishment of a controller or a processor on French territory, whether or not the processing takes place in France.
In addition, where the GDPR permits national variations, those variations will apply where the data subject resides in France regardless of whether or not the controller is established in France.
Is there a concept of a controller and processor?
Yes. The GDPR contains the concept of a controller, who determines the purpose and means of processing, and a processor, who just processes personal data on behalf of the controller.
Both controllers and processors are subject to the rules in the GDPR, but the obligations placed on processors are more limited.
Are both manual and electronic records subject to data protection legislation?
Yes. The GDPR applies to both electronic records and structured hard copy records.
Are there any national derogations?
The GDPR does not apply to law enforcement activities which are instead subject to the Law Enforcement Directive. The GDPR also does not apply to areas of law that are outside the scope of Union law, such as national security, and does not apply to purely personal or household activity.
What is personal data?
Personal data is information relating to an identified or identifiable natural person.
This is a broad term and includes a wide range of information. The GDPR expressly states it includes online identifiers such as cookies.
Is information about legal entities personal data?
No. However, information about sole traders and partnerships is likely to be personal data.
What are the rules for processing personal data?
All processing of personal data must comply with all six general data quality principles. Personal data must be: (i) processed fairly, lawfully and transparently; (ii) collected for specific, explicit and legitimate purposes and not processed in a manner incompatible with those purposes; (iii) adequate, relevant and not excessive; (iv) accurate and, where necessary, up to date; (v) kept in an identifiable form for no longer than necessary; and (vi) kept secure.
The processing of personal data must also satisfy at least one condition for processing personal data. These conditions are that the processing is: (a) carried out with the data subject’s consent; (b) necessary for the performance of a contract with the data subject; (c) necessary for compliance with a legal obligation; (d) necessary in order to protect the vital interests of the data subject; (e) necessary for the public interest or in the exercise of official authority; or (f) necessary for the controller’s or recipient’s legitimate interests, except where overridden by the interests of the data subject.
These rules are almost identical to the core requirements for processing personal data in the old Data Protection Directive. The European Data Protection Board has issued Guidelines on the performance of a contract processing condition for online services (2/2019).
Are there any formalities to obtain consent to process personal data?
The requirements for consent under the GDPR are strict.
To be valid, consent must be in clear and plain language and, where sought in writing, separate from other matters. Consent must be based on affirmative action so pre-ticked boxes are not acceptable. Consent might not be valid if: (i) there is any detriment to the data subject for refusing; (ii) there is an imbalance of power; (iii) consent for multiple purposes is bundled together; or (iv) the consent is a condition of entering into a contract. Finally, consent can be withdrawn at any time.
In practice, other processing conditions should be relied on where possible. Consent will only be an appropriate processing condition if the individual has a genuine choice over the matter, for example, whether to be sent marketing materials.
The Article 29 Working Party has issued Guidelines on Consent (WP259).
Are there any special rules when processing personal data about children?
Consent from a child in relation to online services will only be valid if authorised by a parent. A child is someone under 16 years old, though Member States may reduce this age to 13.
France has chosen to reduce this age limit to 15.
Are there any special rules when processing personal data about employees?
The GDPR allows Member States to implement more specific national rules governing the processing of personal data about employees. It may also be possible to process special category personal data where it is necessary for a legal obligation in the field of employment law.
The revised French DPA allows employers' or administrations' processing of biometric data where strictly necessary to control access to the workplace or to computing resources.
It is a general obligation under French law to use the French language when conducting business or dealing with consumers or employees in France.
Sensitive Personal Data
What is sensitive personal data?
Special category data is personal data consisting of racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, biometric data, data concerning health or data concerning a natural person’s sex life or sexual orientation.
The inclusion of genetic and biometric data is new and an extension to the types of sensitive personal data in the Data Protection Directive.
Information about criminal offences is dealt with separately and is subject to even tighter controls.
Are there additional rules for processing sensitive personal data?
Special category data may only be processed if a condition for processing special category data is satisfied. A condition arises where the processing: (a) is carried out with the data subject’s explicit consent; (b) is necessary for a legal obligation in the fields of employment, social security and social protection law; (c) is necessary to protect the vital interests of the data subject or another person where the data subject is unable to give consent; (d) is carried out by a non-profit-seeking body and relates to members of that body or persons who have regular contact; (e) relates to data made public by the data subject; (f) is necessary for legal claims; (g) is for reasons of substantial public interest under EU or Member State law; (h) is necessary for healthcare reasons; (i) is necessary for public health reasons; or (j) is necessary for archiving, scientific or historical research purposes or statistical purposes and is based on EU or Member State law.
The revised French DPA allows the processing of sensitive personal data about health for public interest reasons under certain conditions (e.g. declaration of conformity with standard references and regulations established by the CNIL, ad hoc authorisation, etc.).
The revised French DPA also contains additional provisions regarding processing of sensitive personal data. It allows: (i) employers' or administrations' processing of biometric data where strictly necessary to control access to the workplace or the use of apparatus or software applications; and (ii) processing of sensitive personal data where that data will be promptly anonymized in accordance with a method validated by the CNIL.
Other provisions relate to the reuse of public information contained in judgments and decisions and, under some circumstances, processing necessary for public research.
Finally, the revised French DPA imposes controls on the processing of national registration numbers, also known as NIRs. NIRs can be used in processing: (i) which are only used for official statistical purposes and are implemented by the official statistical service; (ii) which are only used for scientific or historical research purpose; or (iii) to permit the use of e-government teleservices available to users of the French administration. Decree n° 2019-341 of 19 April 2019 provides an exhaustive list of other use cases for NIR including verifying a candidate’s identity and processing of payroll in the context of social contributions.
Are there additional rules for processing information about criminal offences?
It is only possible to process personal data relating to criminal convictions or offences if: (a) it is carried out under the control of official authority; or (b) when the processing is authorised by EU or Member State law providing for appropriate safeguards for the rights and freedoms of data subjects.
The revised French DPA lists categories of persons allowed to process such personal data: (i) courts, public authorities and legal persons entrusted with a public service, acting within the scope of their functions; (ii) auxiliaries of justice (such as mediators or experts) for the strict exercise of their functions, as well as entities collaborating with judicial entities as determined by Decree; and (iii) persons reusing public information appearing in published rulings, provided that the processing has neither the purpose or effect of allowing the re-identification of the concerned persons.
The revised French DPA also allows natural or legal persons to process information about criminal offences for the purpose of enabling them: (i) to take legal action as a victim or on behalf of such victim; and (ii) to have a ruling enforced, for a duration proportionate to this purpose. Communication to a third party is only possible under the same conditions and to the extent strictly necessary for the pursuit of the same purposes.
Finally, the processing of information about criminal offences is permitted by specified intellectual property rights management agencies for the purpose of defending those rights.
Are there any formalities to obtain consent to process sensitive personal data?
Consent to process sensitive personal data must be explicit. The general restrictions on consent, set out above, will also apply. This suggests a degree of formality, such as ticking a box containing the express words “I consent”. It is unlikely explicit consent could be obtained through a course of conduct.
Data Protection Officers
When must a data protection officer be appointed?
Both controllers and processors must appoint a data protection officer if: (i) they are a public authority; (ii) their core activities consist of regular and systematic monitoring of data subjects on a large scale; or (iii) their core activities consist of processing special category personal data on a large scale (including processing information about criminal offences).
The revised French DPA provides that controllers processing personal data under the scope of Law Enforcement Directive must appoint a data protection officer (with the exception of persons acting within scope of their judicial activity).
What are the duties of the data protection officer?
The data protection officer must be involved in all data protection issues and cannot be dismissed or penalised for performing their role. The data protection officer must report directly to the highest level of management. Details of the data protection officer must be communicated to the relevant supervisory authority.
The Article 29 Working Party has issued Guidelines on Data Protection Officers (WP243).
Accountability and Privacy Impact Assessments
Is there a general accountability obligation?
The GDPR adds a new general accountability obligation under which you must not only comply with these new rules, but also be able to demonstrate you comply with them. This means ensuring suitable policies are in place supported by audit and training.
Are privacy impact assessments mandatory?
A privacy impact assessment must be conducted where “high risk” processing is carried out. This includes: (a) systematic and extensive profiling that produces legal effects or significantly affects individuals; (b) processing on a large scale either special categories of personal data or personal data relating to criminal convictions and offences; and (c) systematic monitoring of a publicly accessible area on a large scale (e.g. CCTV). Where the assessment indicates the risk cannot be mitigated, the controller must consult the relevant supervisory authority.
The Article 29 Working Party has subsequently issued Guidelines on Data Protection Impact Assessments (WP 248). It suggests there are nine criteria to consider to determine whether to conduct a privacy impact assessment, and that an assessment should be made if two or more of those criteria are met. This is arguably wider than the criteria set out in the paragraph above.
The revised French DPA specifies that controllers processing personal data under the Law Enforcement Directive must conduct a privacy impact assessment when that processing is high risk (for example, when such processing relates to sensitive personal data).
In order to help conduct privacy impact assessments, the CNIL has developed an open source tool, recently updated by the CNIL, which is available here.
Rights of Data Subjects
A controller must provide data subjects with a privacy notice setting out how the individual’s personal data will be processed. The privacy notice must contain the enhanced transparency information.
The Article 29 Working Party has issued Guidelines on Transparency (WP260).
It is a general obligation under French law to use the French language when conducting business or dealing with consumers or employees in France. It is very likely this obligation will also apply to privacy notices under the GDPR.
Rights to access information
Data subjects will have a right to access copies of their personal data by making a written request to the controller.The initial request is free, though a charge can be made for subsequent requests. Controllerscan refuse the request if it is manifestly unfounded or excessive. The response must be provided within a month, though this can be extended by two months if the request is complex.
Rights to data portability
Data subjects will also have a right to data portability where the condition for processing personal data is consent or the performance of a contract. It entitles individuals to obtain any personal data they have “provided” to the controller in a machine-readable format. Individuals can also ask for the data to be transferred directly from one controller to another. There is no right to charge fees for this service.
The Article 29 Working Party has issued Guidelines on data portability (WP242).
Right to be forgotten
A data subject can ask that their data be deleted in certain circumstances. However, those circumstances are relatively limited, for example where the processing is based on consent, that consent is withdrawn and there are no other grounds for processing. Even where the right does arise, there are range of exemptions, for example where there is a legal obligation to retain the data.
The European Data Protection Board has issued Guidelines on the criteria of the Right to be Forgotten in the search engines cases under the GDPR (part 1) (5/2019).
Objection to direct marketing
A data subject can object to their personal data being processed for direct marketing purposes at any time. This includes profiling to the extent related to direct marketing.
The GDPR contains a range of other rights, including a right to have inaccurate data corrected. There is also a right to object to processing being carried out in the performance of a public task or under the legitimate interests condition.
Finally, there are controls on taking decisions based solely on automated decision making that produce legal effects or similarly significantly affects the data subject. The Article 29 Working Party has issued Guidelines on Automated Decision Making and Profiling (WP251).
In addition, the revised French DPA allows individuals to give instructions regarding the retention, erasure and communication of their data after their death. Such instructions can be revoked or modified at any time.
Security requirements in order to protect personal data
The GDPR contains a general obligation to implement appropriate technical and organisational measures to protect personal data.
In addition, controllers and processors must ensure, where appropriate: (i) the pseudonymisation and encryption of personal data; (ii) the ability to ensure the ongoing confidentiality, integrity, availability and resilience of its information technology systems; (iii) the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident; and (iv) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.
Specific rules governing processing by third party agents (processors)
A controller must ensure that any processor it instructs will ensure adequate security for personal data and otherwise meet the requirements of the GDPR.
The controller must have written contracts with its processor containing the enhanced processor clauses.
Notice of breach laws
A personal data breach must be notified to the relevant supervisory authority unless it is unlikely to result in a risk to data subjects. The notification must, where feasible, be made within 72 hours. If the personal data breach is a high risk for data subjects, those data subjects must also be notified.
Specific notice of breach laws apply to the electronic communications sector under national laws implementing the Privacy and Electronic Communications Directive and to operators of essential services and digital service providers under national laws implementing the Network and Information Systems Directive.
The Article 29 Working Party has issued Guidelines on Personal Data Breach Notification (WP250).
Decree n° 2019-536 dated 29 May 2019 lays down two categories of processing that are exempt from the obligation to notify data subjects, namely: (i) processing including personal data likely to allow to identify persons whose anonymity is protected by laws protecting freedom of the press; and (ii) processing of certain health or administrative data where notification is likely to represent a risk for national security, national defence or public security.
Transfer of Personal Data to Third Countries
Restrictions on transfers to third countries
The GDPR contains a restriction on transborder dataflows. A transfer can take place if it: (i) is to a whitelisted country; (ii) is made pursuant to a set of Model Contracts; (iii) is made pursuant to binding corporate rules; (iv) is made to an importer who has signed up to an approved code or obtained an approved certification; or (v) is otherwise approved by the relevant supervisory authority.
Transfers are also possible if an individual derogation applies. These derogations allow a transfer if it: (i) is made with the data subject’s explicit consent; (ii) is necessary for the performance of a contract with, or in the interests of, the data subject; (iii) is necessary or legally required on important public interest grounds, or for legal claims; (iv) is necessary to protect the vital interests of the data subject; (v) is made from a public register; or (vi) is made under the so-called minor transfer exemption.
The position is broadly the same as under the old Data Protection Directive. One notable change is the introduction of the so-called minor transfer exemption, though that exemption will be very hard to rely on in practice.
The European Data Protection Board has issued Guidelines on derogations applicable to international transfers (2/2018).
Notification and approval of national regulator (including notification of use of Model Contracts)
In general, there is no need for prior approval from a supervisory authority. However, this depends on the justification for the transfer.
For example, there will be no obligation to get approval for the use of Model Contracts (though it is possible some supervisory authorities may want to be notified of their use). In contrast, it will be necessary to get approval to rely on binding corporate rules, and the supervisory authority must be informed of transfers made using the minor transfers exemption.
Use of binding corporate rules
The GDPR places binding corporate rules on a statutory footing. It will be possible to obtain authorisation from one supervisory authority (subject to approval through the consistency mechanism) that will cover transfers from anywhere in the EU.
In France, then a number of binding corporate rules were approved by the CNIL under the current law including Airbus, Atos, AXA, BMC, Bristol Myers Squib, Cap Gemini, CMA-CGM, Corning, ENGIE, GE, Hermès, HP, International SOS, Linkbynet, Michelin, Novartis, Safran, Salesforce, Schneider, Société Générale, and Total.
The GDPR is intended to make data protection a boardroom issue. It introduces an antitrust-type sanction regime with fines of up to 4% of annual worldwide turnover or €20m, whichever is the greater. These fines apply to breaches of many of the provisions of the GDPR, including failure to comply with the six general data quality principles or carrying out processing without satisfying a condition for processing personal data.
A limited number of breaches fall into a lower tier and so are subject to fines of up to 2% of annual worldwide turnover or €10m, whichever is the greater. Failing to notify a personal data breach or failing to put an adequate contract in place with a processor fall into this lower tier.
The Article 29 Working Party has issued Guidelines on administrative fines (WP253).
The revised French DPA does not modify existing criminal sanctions. The current criminal sanctions include imprisonment for up to five years and fines of up to EUR 300,000 (and up to EUR 1,500,000 for legal entities). However, it is likely that these sanctions will be updated in the near future.
Data subjects have a right to compensation in respect of material and non-material damage.
Regulators will have a range of other powers and sanctions at their disposal. This includes investigative powers, such as the ability to demand information from controllers and processors, and to carry out audits. They will also have corrective powers enabling them to issue warnings or reprimands, to enforce an individual’s rights and to issue a temporary or permanent ban on processing.
- In January 2019, Google was fined €50 million for failing to provide transparency and clarity to users when informing them how their data is processed and a lack of valid consent in relation to personalised ads. The fine arose out of complaints from pressure groups - the Austrian organisation "None of Your Business" and the French NGO "La Quadrature du Net".
- In November 2019, a small company in the energy sector was fined €500,000 after a complaint was made about cold calls. CNIL found that the company had received several complaints that had been ignored and had not informed individuals about the processing of their personal data including the recording of calls.
- In May 2019, real estate company Sergic was fined €400,000 for its poor security measures and excessive data storage. Third parties were able to access sensitive customer data online as there were no prior authentication procedures in place and customer documents were stored for longer than was necessary.
- In December 2018, the CNIL issued a fine of €400,000 against UBER for having insufficiently secured the data of the users of its VTC service, and a fine of €250,000 against telecom company Bouygues Telecom for having insufficiently protecting customer data.
- In June 2018, the optics company Optical Centre was fined €250,000 for having insufficiently secured the data of its customers placing an order online from its website.
- In July 2019, insurance intermediary and designer/distributor of automobile insurance contracts company Ctive Assurances was fined €180,000 for breaching the security of customer data.
- In January 2018, household appliances, computer, telephony and audio-visual equipment reseller Darty was fined €100,000 for not having sufficiently secured the data of customers who made an online request for after-sales services.
- In June 2019, a small company of 9 employees specialized in translation services was fined €20,000 for having set up a video surveillance system that placed its employees under constant surveillance.
Other enforcement action: In 2018, the CNIL received 11,077 complaints, representing a 32,5% increase compared to 2017. 35.7% were related to the dissemination of personal data on the Internet, 21% to the business and marketing sector, 16.5% to human resources, 8.9% to the banking sector and 4.2% related to the health and social sector.
In 2018, there were 310 investigations. This led to 48 formal notices and 11 sanctions. Out of those 310 investigations, 204 were carried on site, 51 were conducted on-line and 20 targeted CCTV systems. These online investigations are facilitated by the “Law on consumption” dated 17 March 2014.
The CNIL has not yet published its annual report for 2019. However, it has stated it focused its action on complaints received by data subjects, relations between controllers and processors and processing of children’s data.
ePrivacy | Marketing and cookies
The “Trust in the Digital Economy Act” (the “Act”) implemented Article 13 of the Privacy and Electronic Communications Directive on 21 June 2004. The Act is now codified under Article L. 34-5 of the Postal and Electronic Communications Code and is mentioned in Articles L. 222-16 and 223-7 of the Consumer Code.
The Ordinance no. 2011-1012 of 24 August 2011 (the “Ordinance”). The Ordinance implements the amendments to the Privacy and Electronic Communications Directive.
The revised French DPA requires data controllers to obtain prior consent from users to store or access cookies after having provided the user with information about the purposes for which cookies are used and about the means to prevent such storage or access.
The revised French DPA explicitly recognises that such consent may result from appropriate settings on a user’s connection device, such as an internet browser, or from any other applications placed under a user’s control.
Prior information and consent requirements do not apply where the cookie’s sole purpose is to enable or facilitate the communication (i.e. technical cookies) or where the cookie is strictly necessary to provide an online communication service requested by the user (e.g. cookies concerning language preferences).
On 14 January 2020, the CNIL published a draft recommendation (the “Recommendation”) regarding the practicalities of obtaining valid consent to cookies. It provides concrete examples of the implementation of the cookie laws. A definite version of the Recommendation is expected during spring 2020.
Conditions for direct marketing by e-mail to individual subscribers
Direct marketing e-mail requires the “prior consent” of the recipient. “Prior consent” is defined as a “free, specific and informed manifestation of consent to his personal data being used for direct marketing purposes”.
Conditions for direct marketing by e-mail to corporate subscribers
Direct marketing by e-mail is permitted subject to prior notification that the e-mail address will be used for marketing purposes. The marketing e-mail must relate to the profession of the person to whom the marketing e-mail is sent.
Exemptions and other issues
For both individual and corporate subscribers, it is permitted to send an e-mail for the purposes of direct marketing if it falls within the similar products and services exemption and complies with the requirements of the DPA.
The sender must include the eCommerce information and provide simple means to freely object to any further similar communications.
However, direct marketing e-mails are prohibited if: (i) the identity of the sender is disguised or concealed; (ii) an opt-out address is not provided; or (iii) the title of the e-mail does not relate to the service or product offered.
Regarding corporate subscribers specifically, the rules on consent and objection outlined above do not apply to generic e-mail addresses such as email@example.com, firstname.lastname@example.org and email@example.com.
SMS/MMS are subject to the rules on direct marketing by e-mail rather than the rules on direct marketing by telephone.
Conditions for direct marketing by telephone to individual subscribers (excludes automated calls)
Professionals wishing to engage in direct marketing by phone must inform consumers of their right to register with Bloctel, a direct marketing opposition list. Professionals cannot call consumers who have registered on Bloctel save in respect of limited situations.
It is not permitted to make direct marketing calls to individual subscribers who have previously objected to such calls.
Conditions for direct marketing by telephone to corporate subscribers (excludes automated calls)
It is not permitted to make direct marketing calls to corporate subscribers who have previously objected to such calls.
Exemptions and other issues
Calls can be made to individual subscribers where there is a pre-existing contractual relationship or the call is to offer subscriptions to newspapers, journals and magazines.