In mid-November 2026, a French polling group stated publicly that it had identified a cybersecurity incident affecting one of its internal information systems. According to the company statement quoted by AFP via Le Figaro, the group identified a cybersecurity incident affecting an internal information system, filed a complaint with the competent authorities on 11 November 2026, activated its incident response procedures to contain the incident, called in an external response team to support the investigation, and undertook to contact directly any client, project or business partner whose information might prove affected, while assuring that the incident had no effect on its operations. The statement adds that the investigation is still running and that the group cannot comment further for now. American search interest in the word “cyberattack” exceeded 100,000 queries with growth of 1,000 percent in the 24 hours measured on 17 November 2026, and French national newspapers reported the same incident on 16 November 2026. At the drafting date, no theft or leak of personal data has been established by an official source, no liability has been established, signed contracts prevail over any general analysis, and only a court can decide individual cases. The following developments are general in scope: they describe the checks and steps that are useful in any comparable situation and do not describe the situation of Ipsos, about which this article makes no finding.
I. After a cyberattack in France, what does the law require of the organisation that was hit?
French law does not treat a cyberattack as a mere technical incident. As soon as personal data may be involved, the General Data Protection Regulation (GDPR) imposes a strict timetable on the controller, and French criminal law punishes the attackers. The victim organisation has duties; the attackers face prison terms.
A. Do I have to notify the CNIL within 72 hours after a personal data breach?
Yes, as a rule. Article 33 of the GDPR provides: “le responsable du traitement en notifie la violation en question à l’autorité de contrôle compétente conformément à l’article 55, dans les meilleurs délais et, si possible, 72 heures au plus tard après en avoir pris connaissance, à moins que la violation en question ne soit pas susceptible d’engendrer un risque pour les droits et libertés des personnes physiques. Lorsque la notification à l’autorité de contrôle n’a pas lieu dans les 72 heures, elle est accompagnée des motifs du retard.” (the controller notifies 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; where notification is late, it states the reasons for the delay). In France, that authority is the CNIL. The 72-hour clock runs from awareness of the breach, not from the attack itself, and the only exemption is a breach unlikely to create any risk, which an organisation should never assume lightly.
The CNIL applies the same timetable on its CNIL notification guide: an initial notification is expected within 72 hours where possible after the breach is established, and where notification comes later, the reasons for the delay must be explained in the filing. The CNIL also states the general rule in plain terms in the same CNIL notification guide: where the incident poses a risk to the privacy of the persons concerned, it must be notified, and in case of doubt the organisation should notify and let the CNIL say whether the individuals must be informed. This matches the practice of a French data protection practice handling breach notifications and CNIL procedures: document first, notify fast, and keep the evidence of every step.
Documentation is itself a legal duty. The CNIL requires the controller to record the nature of the breach, the categories and approximate number of persons concerned, the categories and approximate number of records affected, the likely consequences, and the measures taken or planned to prevent recurrence or mitigate harm. The summary document of the CNIL notification serves as that internal record. An organisation that notifies without documenting, or documents without notifying, remains exposed.
When the breach is likely to create a high risk for the individuals, a second duty arises toward the victims themselves. Article 34 of the GDPR provides: “Lorsqu’une violation de données à caractère personnel est susceptible d’engendrer un risque élevé pour les droits et libertés d’une personne physique, le responsable du traitement communique la violation de données à caractère personnel à la personne concernée dans les meilleurs délais.” (when a personal data breach is likely to result in a high risk to the rights and freedoms of a natural person, the controller communicates the breach to the data subject without undue delay). The polling group in the November 2026 incident applied exactly that logic when it undertook to contact directly anyone whose information might prove affected, according to the company statement quoted by AFP. Communication to victims must describe the breach in clear language, indicate a contact point, and explain the measures offered to limit harm.
B. Should a complaint be filed with the police after a cyberattack in France?
Filing a complaint is strongly advised and often decisive. The CNIL advises in its CNIL notification guide that where the notified breach follows a cyberattack, the organisation should file a complaint at the nearest police station or gendarmerie and keep all technical evidence available to investigators. The November 2026 complaint filed on 11 November, reported by Ouest-France, which confirms that a complaint was filed, follows that recommendation. A complaint opens a criminal investigation, preserves the chain of evidence, and supports later claims before the criminal court or the insurer.
French criminal law punishes every stage of an intrusion. Article 323-1 of the Criminal Code provides: “Le fait d’accéder ou de se maintenir, frauduleusement, dans tout ou partie d’un système de traitement automatisé de données est puni de trois ans d’emprisonnement et de 100 000 € d’amende.” (fraudulent access to or persistence in all or part of an automated data processing system carries three years of imprisonment and a 100,000 euro fine). Where the intrusion deleted or altered data, or disrupted the system, the penalty rises to five years and 150,000 euros. Article 323-2 punishes interference with the operation of such a system: “Le fait d’entraver ou de fausser le fonctionnement d’un système de traitement automatisé de données est puni de cinq ans d’emprisonnement et de 150 000 € d’amende.” (obstructing or distorting the operation of an automated data processing system carries five years of imprisonment and a 150,000 euro fine). Article 323-3 covers data theft and manipulation: “Le fait d’introduire frauduleusement des données dans un système de traitement automatisé, d’extraire, de détenir, de reproduire, de transmettre, de supprimer ou de modifier frauduleusement les données qu’il contient est puni de cinq ans d’emprisonnement et de 150 000 € d’amende.” (fraudulently adding data to an automated system, or fraudulently extracting, holding, reproducing, transmitting, deleting or altering the data it contains, carries five years of imprisonment and a 150,000 euro fine). Each provision raises the penalty to seven years and 300,000 euros when the targeted system processes personal data on behalf of the State.
Personal data collected or disclosed through the attack triggers a second set of offences. Article 226-18 of the Criminal Code provides: “Le fait de collecter des données à caractère personnel par un moyen frauduleux, déloyal ou illicite est puni de cinq ans d’emprisonnement et de 300 000 euros d’amende.” (collecting personal data by fraudulent, unfair or unlawful means carries five years of imprisonment and a 300,000 euro fine). Article 226-22 punishes anyone who, having lawfully received personal data in the course of recording, filing, transmitting or otherwise processing it, discloses it without authorisation to an unentitled third party where disclosure would harm the standing or private life of the person concerned: “Le fait, par toute personne qui a recueilli, à l’occasion de leur enregistrement, de leur classement, de leur transmission ou d’une autre forme de traitement, des données à caractère personnel dont la divulgation aurait pour effet de porter atteinte à la considération de l’intéressé ou à l’intimité de sa vie privée, de porter, sans autorisation de l’intéressé, ces données à la connaissance d’un tiers qui n’a pas qualité pour les recevoir est puni de cinq ans d’emprisonnement et de 300 000 euros d’amende.” Negligent disclosure of the same data carries three years and 100,000 euros, and proceedings require a complaint from the victim or their representatives. Proceedings that ignore these texts, or confuse the intrusion with the later misuse of the stolen data, plead the wrong offence and weaken the case.
Evidence handling decides the outcome of both the criminal case and any later dispute with an insurer. The organisation should freeze logs, keep disk images, record who accessed the affected systems and when, and store every message exchanged with hosts, providers, and the response team. Screenshots alone rarely suffice; time-stamped exports, hash values, and written incident minutes carry far more weight before investigators and courts. Individuals should do the same on their side: save the breach notice, bank statements showing disputed transactions, and any correspondence with the controller, since compensation turns on documented loss, not on general assertions.
II. Compensation and punishment: what can victims obtain and what do courts actually award?
Victims of a data breach have two paths: compensation for their loss under civil and European law, and punishment of the attackers under criminal law. Recent French case law shows both paths working, but also sets a firm limit: a bare violation of the GDPR, without proven harm, does not by itself create a right to damages.
A. Can I get compensation after a data breach in France?
Yes, if real harm is shown. Article 82(1) of the GDPR provides: “Toute personne ayant subi un dommage matériel ou moral du fait d’une violation du présent règlement a le droit d’obtenir du responsable du traitement ou du sous-traitant réparation du préjudice subi.” (any person who has suffered material or non-material damage as a result of an infringement of the Regulation has the right to receive compensation from the controller or processor for the damage suffered). Material damage covers bank fraud, lifecycle costs of identity theft, and professional loss; moral damage covers anxiety, loss of control over personal data, and reputational harm.
The Cour de cassation clarified the conditions in a Social Chamber ruling of 24 June 2026 (appeal no. 24-22.792, partial cassation), published at the official record of the decision. The Court restates the text first: “Aux termes de ce texte, toute personne ayant subi un dommage matériel ou moral du fait d’une violation du présent règlement a le droit d’obtenir du responsable du traitement ou du sous-traitant réparation du préjudice subi.” It then recalls the Court of Justice of the European Union (4 May 2023, case C-300/21, Österreichische Post, as restated by the Cour de cassation in the decision linked above): “la simple violation des dispositions de ce règlement ne suffit pas pour conférer un droit à réparation” (the mere infringement of the Regulation is not sufficient to confer a right to compensation). Three practical consequences follow. First, the victim must prove specific harm and its extent; an infringement invoked in the abstract fails. Second, no national rule may require the moral harm to reach a seriousness threshold before compensation is granted. Third, the amount is set under each Member State’s own damages rules, subject to the EU principles of equivalence and effectiveness. A letter that says “my data was breached, pay me” without describing any concrete loss therefore goes nowhere; a file that documents fraudulent withdrawals, blocked accounts, hours spent restoring identity, or medically attested anxiety stands a real chance.
French civil liability supports the same claim independently of the GDPR. Article 1240 of the Civil Code provides: “Tout fait quelconque de l’homme, qui cause à autrui un dommage, oblige celui par la faute duquel il est arrivé à le réparer.” (any act of man which causes damage to another obliges the person by whose fault it occurred to repair it). A company that stored credentials in plain text, ignored patches, or granted excessive access rights commits a fault; the victim who proves resulting loss obtains repair. Criminal negligence in handling personal data is itself punished: Article 226-16 of the Criminal Code punishes processing carried out without the formalities required by law, including by negligence, with five years of imprisonment and 300,000 euros: “Le fait, y compris par négligence, de procéder ou de faire procéder à des traitements de données à caractère personnel sans qu’aient été respectées les formalités préalables à leur mise en oeuvre prévues par la loi est puni de cinq ans d’emprisonnement et de 300 000 euros d’amende.”
The criminal court can also compensate the victim directly. In a Criminal Chamber ruling of 2 September 2025 (appeal no. 24-83.605, dismissal), published at the official record of the decision, a network administrator convicted of attacking his employer’s automated data system received a three-month suspended prison sentence, and the Cour de cassation upheld 10,000 euros for the employer’s moral harm, holding that “la perte de confiance éprouvée par M. [G], suite aux agissements de M. [L], était constitutive d’un préjudice moral découlant directement du délit prévu par l’article 323-1 du code pénal retenu à la charge du prévenu.” (the loss of trust felt following the acts was moral harm flowing directly from the Article 323-1 offence). Victims who join the criminal proceedings as civil parties can therefore obtain damages in the same trial that punishes the attacker, provided they prove the link between the offence and their loss.
B. What is the penalty for hacking in France and what should I do now in practice?
The scale of penalties is severe and cumulative. Fraudulent access or persistence (Article 323-1) carries three years and 100,000 euros, five years and 150,000 euros where data was deleted, altered, or the system disrupted. Obstructing or distorting the system (Article 323-2) and stealing or altering its data (Article 323-3) each carry five years and 150,000 euros. Fraudulent collection of personal data (Article 226-18) carries five years and 300,000 euros; unauthorised disclosure harming reputation or privacy (Article 226-22) carries five years and 300,000 euros, or three years and 100,000 euros by negligence. Where the system processes personal data for the State, Articles 323-1 to 323-3 rise to seven years and 300,000 euros. Legal entities face fines under the terms of Article 131-38 of the Criminal Code plus the penalties of Article 131-39 for offences in this section. These are maximum sentences set by statute; the court fixes the actual penalty from the facts, the harm, and the record of the defendant.
For a person who learns that their data may have been caught in a breach, the useful steps are concrete and immediate. First, read the controller’s notice carefully and keep every message, receipt, and log: proof decides compensation cases, as the 24 June 2026 ruling shows. Second, change exposed passwords, enable two-factor authentication, and warn the bank where payment data is involved. Third, check accounts and credit files for unknown transactions, and report fraud fast to the bank and on the national assistance platform for cyber victims. Fourth, if harm appears, file a complaint and consider joining the criminal case as a civil party, or sue the controller for compensation under Article 82 of the GDPR and Article 1240 of the Civil Code with documented loss. Fifth, anyone may complain to the CNIL, which can investigate and sanction the controller separately from any court award to victims.
For the organisation, the checklist mirrors the duties above: contain and preserve evidence, call in a response team, document the breach, notify the CNIL within 72 hours where risk exists, inform exposed individuals where the risk is high, and file a complaint while keeping technical evidence for investigators. An organisation that follows this sequence protects victims, limits its own exposure to sanctions, and keeps its contracts and insurance operational.
Insurance and contracts add a final layer. Many organisations hold cyber cover that reimburses investigation costs, notification expenses, and third-party claims, but policies set strict notice duties and approved response channels; warning the broker late or hiring outside the agreed panel can reduce cover. Service contracts with hosts and processors allocate responsibility for security updates, backups, and breach cooperation, and those clauses decide who pays when the dust settles. Reading the policy and the processor agreements within days of discovery, alongside the CNIL notification, prevents a procedural mistake from becoming a financial one.
Keeping a dated file from day one changes the outcome. Victims who store the breach notice, bank alerts, receipts for replacement documents, and notes of time spent restoring accounts can show a judge a concrete, itemised loss instead of a general complaint. A complaint to the CNIL can run in parallel: the authority may investigate the controller and order corrective measures, while the court decides on individual compensation.
Conclusion
A cyberattack that may touch personal data triggers two clocks in France: notification to the CNIL within 72 hours where a risk exists, and direct information of exposed individuals where the risk is high, exactly as Articles 33 and 34 of the GDPR require. Attackers face up to five years of imprisonment and heavy fines under Articles 323-1 to 323-3 and 226-18 to 226-22 of the Criminal Code. Victims obtain compensation where they prove concrete material or moral harm under Article 82 of the GDPR and Article 1240 of the Civil Code, as the Cour de cassation confirmed on 24 June 2026 and 2 September 2025. At the date of writing, the November 2026 incident affecting a French polling group’s internal system has produced no finding of data theft by an official source, no established liability, and an investigation the company describes as ongoing; signed contracts prevail over any general analysis, and only a court decides. Anyone concerned should keep every document, follow the controller’s notices, and act on documented facts rather than rumour.
Read also
- Microsoft outage today: Outlook and Teams down while you work with France — proof, deadlines and refunds under French law
- Supermarket freezers hacked across Europe: your rights in France after a food cyberattack (refunds, data breach, complaint)
- AO3 Down After Hack: What to Do to Protect Your Account and Your Data Rights in France and the EU