Cyberpediaby Brain

GDPR and personal data breaches

What a personal data breach is under the GDPR, the 72-hour notification to the CNIL, and what it changes for employees and for management.

On this page
  1. 1In 30 seconds
  2. 2What it is
  3. 3Straight answers
  4. 4What it changes for employees
  5. 5What it changes for management
  6. 6What the text says
  7. 7Where implementation stands
  8. 8Sources
  9. 9Cite this article

In 30 seconds

Where it happens
In any public or private organisation, whatever its size, as soon as it processes personal data[1].
What the text says
Where there is a risk to individuals, the organisation notifies the CNIL without undue delay and, where feasible, no later than 72 hours after becoming aware of it[3].
If it is already done
The incident must be documented internally, even when it is not notified[1].
The reflex
Report any incident involving personal data without delay to the person designated in your organisation, without hiding it or handling it alone.

What it is

A lost USB stick or a file sent to the wrong recipient: these incidents have one thing in common. They can involve personal data, and the General Data Protection Regulation (GDPR) then lays down specific rules for the organisation that processes it.

This article presents the principles of the GDPR, the definition of a data breach, and then what Articles 33 and 34 say about notifying the CNIL and informing individuals. It explains what this changes for an employee and for management.

Straight answers

What is a personal data breach?

Article 4.12 of the GDPR defines it as a breach of security leading, accidentally or unlawfully, to the destruction, loss, alteration or unauthorised disclosure of personal data, or unauthorised access to such data[1]. The CNIL specifies that it means any security incident, whether malicious or not, intentional or not, that compromises the integrity, confidentiality or availability of data[1].

Its examples: the accidental deletion of medical data not backed up elsewhere, the loss of an unsecured USB stick containing a company's customer database, the malicious intrusion into a school database to change results[1].

What are the basic principles of the GDPR?

Article 5 sets out six requirements for personal data. They must be processed lawfully, fairly and transparently. They are collected for specified, explicit and legitimate purposes. They are adequate, relevant and limited to what is necessary (minimisation). They are accurate and kept up to date where necessary. They are not kept longer than necessary in view of the purposes. Finally, they are processed in a way that ensures appropriate security, including protection against accidental loss, destruction or damage, through appropriate technical or organisational measures[2].

The controller is responsible for compliance with these principles and must be able to demonstrate that they are respected[2]. Article 6 adds that processing is lawful only if at least one of the conditions it lists is met, such as the person's consent or the need to perform a contract[2].

Must the CNIL always be notified?

No. The CNIL states that not all breaches must necessarily be notified to the supervisory authority or to the individuals concerned[1]. Where there is no risk to the rights and freedoms of individuals, the organisation documents the breach in an internal register and notifies neither the CNIL nor the individuals. Where there is a risk, it documents the breach and notifies the CNIL. Where there is a high risk, it documents the breach, notifies the CNIL and informs the individuals concerned[1].

Does the 72-hour period start at the time of the incident?

It starts when the controller becomes aware of the breach. According to the CNIL, the starting point is the moment when it has a reasonable degree of certainty that an incident has occurred and affected personal data[1]. During the investigation phase, it is not considered to be aware of the breach[1]. The organisation must have detection measures in place and carry out the necessary investigations as early as possible[1].

Must everything be known before notifying?

No. Article 33 allows information to be provided in phases if it cannot all be provided at the same time[3]. The CNIL describes an initial notification as soon as possible, followed by a supplementary notification[1].

What it changes for employees

The employee counts in the system, because the organisation can only notify what it knows. The CNIL recommends that organisations put in place measures to detect a breach immediately and contain it quickly[1]. It also gives cases where the organisation is considered to be informed: it realises that a USB stick containing personal data has been lost, or a third party proves to it that they received an email containing information about another person[1].

In practice, an employee who notices an incident reports it quickly to the person designated in their organisation (the IT department, the data protection officer or another named contact). They do not try to fix it discreetly. They note what they saw: which data, which systems, at what time. These elements match what the notification must describe: the nature of the breach, the individuals and records concerned, the likely consequences and the measures taken[3].

What it changes for managementManagement

The controller has four tasks.

  • Document every breach, stating the facts, its effects and the measures taken to remedy it. This documentation allows the CNIL to verify compliance with Article 33[3]. The register also contains, where applicable, the justification for not notifying[1].
  • Assess the risk case by case, according to the type of breach, the nature, sensitivity and volume of the data, how easily individuals can be identified, the possible consequences, the characteristics of the individuals (children, vulnerable persons) and their number[1].
  • Decide whether to notify. The controller remains in charge of this decision, even if it asks its processor to act on its behalf[1]. In case of doubt, the CNIL advises notifying: it will indicate whether the individuals must be informed[4].
  • Supervise its processors. The processor notifies the controller of any breach without undue delay after becoming aware of it[3]. The CNIL advises providing for this in the contract[1].

What the text saysOfficial text

Article 33 requires the controller to notify the breach to the competent supervisory authority without undue delay and, where feasible, no later than 72 hours after becoming aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. After 72 hours, the notification is accompanied by the reasons for the delay[3].

The notification must at least describe the nature of the breach, give the name and contact details of the data protection officer or another contact point, and describe the likely consequences and the measures taken or proposed[3]. It is made through a dedicated CNIL online service[1].

Article 34 provides that, where the breach is likely to result in a high risk, the controller communicates it to the individual concerned without undue delay, in clear and plain language[3]. This communication is not necessary in three cases. The data have been rendered unintelligible, for example by encryption. Subsequent measures ensure that the high risk can no longer materialise. Or the communication would involve disproportionate effort, in which case a public communication or a similar measure replaces it[3]. The supervisory authority can require the communication if it has not been made[3].

As for penalties, Article 83 provides for administrative fines. Infringements of the obligations of Articles 25 to 39, including Articles 33 and 34, can reach up to 10,000,000 EUR or, for a company, up to 2% of total worldwide annual turnover of the preceding financial year, whichever is higher. Infringements of the basic principles of Articles 5, 6, 7 and 9 can reach up to 20,000,000 EUR or 4%[5]. To set the fine, the supervisory authority takes into account, among other things, the way it became aware of the breach, and whether the organisation notified it[5]. A person who has suffered damage as a result of an infringement of the regulation has the right to compensation from the controller or the processor[5].

Where implementation stands

The CNIL examines each notification within 24 working hours, looking at the level of risk and at the measures taken before and after the breach[1]. It may send back advice, remarks or questions by email within 72 hours, only where needed. If there is no reply within two months, the controller may consider that it has no remarks[1]. It may close the procedure or require that the individuals be informed[4]. It also checks the register, the deadlines and the content of notifications, and may impose penalties[1].

Its list of penalties, dated 14 April 2026, contains cases linked to data breaches[6]. Two decisions of 8 January 2026 concern telephone operators, with the themes of failure to secure data and the obligation to inform the individuals concerned of a breach: an administrative fine of 27 million euros and an injunction for a mobile operator, and a fine of 15 million euros and an injunction for a fixed-line operator[6]. More modestly, two decisions of 7 December 2020 concern doctors for a failure to ensure data security and to notify a breach, with penalties of 3,000 euros and 6,000 euros[6].

Sources

  1. CNIL, “Violations de données personnelles : les règles à suivre”, 19 June 2018. https://www.cnil.fr/fr/violations-de-donnees-personnelles-les-regles-suivre (accessed 10 November 2026)
  2. CNIL, “CHAPITRE II - Principes”. https://www.cnil.fr/fr/reglement-europeen-protection-donnees/chapitre2 (accessed 10 November 2026)
  3. CNIL, “CHAPITRE IV - Responsable du traitement et sous-traitant”. https://www.cnil.fr/fr/reglement-europeen-protection-donnees/chapitre4 (accessed 10 November 2026)
  4. CNIL, “Notifier une violation de données personnelles”, 24 May 2018. https://www.cnil.fr/fr/services-en-ligne/notifier-une-violation-de-donnees-personnelles (accessed 10 November 2026)
  5. CNIL, “CHAPITRE VIII - Voies de recours, responsabilité et sanctions”. https://www.cnil.fr/fr/reglement-europeen-protection-donnees/chapitre8 (accessed 10 November 2026)
  6. CNIL, “Les sanctions prononcées par la CNIL”, 14 April 2026. https://www.cnil.fr/fr/les-sanctions-prononcees-par-la-cnil (accessed 10 November 2026)