Skip to content

Inth is now agentic by default. Use it from Claude, ChatGPT or Cursor.

See how
Opens the cited record in a new tab

GDPR and ePrivacy cookie rules: how the CNIL enforces Article 82

In the EU, storing or reading anything on a visitor's device needs prior consent unless it is strictly necessary. That covers cookies, local storage, pixels and fingerprinting scripts. The rule comes from the ePrivacy Directive, with consent defined by the GDPR.

Source review
17 October 2026

What the law says

France's CNIL has issued the largest cookie fines in this library, and its decisions show three recurring failures:

  • cookies set on arrival;
  • refusal harder than acceptance;
  • choices that were not respected.

ePrivacy Directive, Article 5(3) (Directive 2002/58/EC, consolidated):

Member States shall ensure that the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user is only allowed on condition that the subscriber or user concerned has given his or her consent, having been provided with clear and comprehensive information … about the purposes of the processing.

There are two exceptions. Storage or access is allowed "for the sole purpose of carrying out the transmission of a communication over an electronic communications network". It is also allowed where it is "strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service".

GDPR consent. Consent is "any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement" (Article 4(11)). "It shall be as easy to withdraw as to give consent" (Article 7(3)).

France, Article 82 of the Loi Informatique et Libertés transposes Article 5(3). It requires clear and complete information about the purpose of any reading or writing on the device and "Des moyens dont il dispose pour s'y opposer". It permits these operations only once the user "ait exprimé, après avoir reçu cette information, son consentement". The text is quoted in CNIL deliberation SAN-2020-013, para. 20.

The elements of a breach are:

  • a read or write operation on the user's device;
  • not strictly necessary and not for transmission;
  • without prior, informed, freely given consent.

Who can sue and what they can recover

  • Regulators. For breaches of the French law, the CNIL's restricted committee can order compliance with a periodic penalty "which may not exceed EUR 100 000 per day of delay". It can impose a fine of up to €10 million or 2% of worldwide turnover, "increased to EUR 20 million and 4%" in the cases in GDPR Article 83(5) and (6). The text is Article 20-IV of the Loi, as quoted in SAN-2025-004, para. 218 (CNIL English translation). Under the GDPR itself, consent failures can reach "20 000 000 EUR, or … 4 % of the total worldwide annual turnover" (Article 83(5)).
  • Individuals. "Any person who has suffered material or non-material damage as a result of an infringement of this Regulation shall have the right to receive compensation" (GDPR Article 82(1)). Individuals can also complain to the CNIL, as the complaint behind the Bing decision did.
  • Limitations period (labelled uncertain). Neither instrument sets one for compensation claims; national rules apply, and we have not confirmed them.
  • Which regulator. The GDPR's one-stop-shop does not apply to cookie rules. France's Conseil d'État held that the "guichet unique" mechanism was not provided "pour les mesures de mise en oeuvre et de contrôle de la directive 2002/58/CE", which belong to national authorities (Conseil d'État, No. 449209, 28 January 2022, para. 12). That is why the CNIL can fine companies established in Ireland or Luxembourg.

How it is used against websites and apps

The CNIL inspects sites online and on complaint. It records which cookies are written when a visitor lands, before and after clicking "Refuse", and compares the banner's options. Typical findings are:

  • advertising cookies set on first load;
  • an "Accept" button with no equal "Refuse";
  • information that does not name purposes;
  • cookies still written after refusal.

How regulators and courts have ruled

DecisionBodyDateAmount and finding
Google, SAN-2020-012CNIL7 December 2020€100,000,000 (€60 million Google LLC, €40 million Google Ireland); Article 82 (deliberation). Upheld by the Conseil d'État on 28 January 2022 (No. 449209)
Amazon Europe Core, SAN-2020-013CNIL7 December 2020€35,000,000. Cookies written on arrival at amazon.fr (deliberation). Upheld on 27 June 2022 (No. 451423)
Google, SAN-2021-023CNIL31 December 2021€150,000,000 (€90 million and €60 million). One click to accept, several to refuse on google.fr and youtube.com (deliberation)
Facebook IrelandCNIL31 December 2021€60,000,000. Same finding on facebook.com (CNIL announcement, archived)
Microsoft Ireland (Bing), SAN-2022-023CNIL19 December 2022€60,000,000. Advertising cookies set without consent; no button to refuse "as easily as accepting" (deliberation)
Shein, SAN-2025-005CNIL1 September 2025€150,000,000. Cookies set without consent, choices not respected, inadequate information (CNIL)
Google, SAN-2025-004CNIL1 September 2025€325,000,000 (€200 million and €125 million). Two findings: ads inserted between Gmail emails without consent, under France's electronic marketing rule (Postal and Electronic Communications Code, Article L. 34-5), and account-creation design that steered users to personalised-ad cookies (Article 82) (CNIL)

What the decisions establish.

  • Arrival. Writing advertising cookies when a page loads breaches Article 82 (Amazon, Bing, Shein).
  • Symmetry. Refusal must be as simple as acceptance. The Google 2021 order required "un moyen de refuser … présentant une simplicité équivalente au mécanisme prévu pour leur acceptation" (SAN-2021-023).
  • Proof and scrolling. Scrolling is not consent, and operators must be able to prove consent (CNIL guidelines announcement, 19 July 2019).
  • Jurisdiction. The Conseil d'État, citing the CJEU's Planet49 (C-673/17), confirmed that GDPR consent conditions apply to device access while enforcement stays national (No. 449209, para. 12).

Status and what is changing

Status, 17 October 2026: Article 5(3) and Article 82 are in force. The 2025 Google decision (€325 million) is the largest CNIL fine in the library, but it also covers the Gmail advertising breach, so it is not a pure cookie fine. The appeal status of the 2025 Google and Shein decisions is not stated in the sources reviewed. Related EU decisions on other GDPR duties are summarised below and on their own pages: Meta Ireland on data transfers and TikTok on children's defaults.

Other GDPR duties in the library: transfers and account defaults

Two Irish decisions in the library rest on GDPR duties that have nothing to do with cookies. In both, the Data Protection Commission acted as lead authority after a binding decision of the European Data Protection Board.

  • International transfers. Without an adequacy decision, a controller may transfer personal data to a third country "only if the controller or processor has provided appropriate safeguards, and on condition that enforceable data subject rights and effective legal remedies for data subjects are available" (Article 46(1)). In Meta Ireland, the DPC found that Facebook transfers to the US under standard contractual clauses breached Article 46(1) after Schrems II. On 12 May 2023 it fined Meta Ireland €1.2 billion and ordered it to suspend the transfers (DPC decision page). The EU-US Data Privacy Framework has given transfers to certified US companies a new basis since 10 July 2023 (European Commission).
  • Data protection by design and by default. Article 25(2) requires measures ensuring that "by default personal data are not made accessible without the individual's intervention to an indefinite number of natural persons" (Article 25). In TikTok, the DPC imposed three fines totalling €345 million on 1 September 2023 (€100 million, €65 million and €180 million) over public-by-default accounts for 13 to 17-year-olds, Family Pairing and transparency. It found no age-verification infringement (DPC announcement).

The fine ceilings differ. Breaches of Article 25 can reach €10 million or 2% of worldwide annual turnover; transfer breaches under Articles 44 to 49 can reach €20 million or 4% (Article 83(4)(a) and (5)(c)). Unlike cookie rules, these duties fall under the GDPR's one-stop-shop, which is why the Irish DPC led both cases.

What Inth does here. Inth has no capability for international data transfers or for in-app account defaults. Code audit's data flow mapping and vendor call graph show which external services your code sends personal data to, which your privacy team can use as an input to a transfer assessment. The legal analysis, and the design of an app's own settings screens, are outside what Inth checks.

What this means for your implementation

  • Load no advertising or analytics cookie, pixel or SDK until the visitor opts in, for EU and UK traffic.
  • Give "Reject all" the same prominence and number of clicks as "Accept all" on the first layer.
  • Make withdrawal as easy as consent, for example a persistent link that reopens the banner.
  • Keep a record of each consent: time, choice, banner version and policy.
  • Re-test after every tag manager change; the CNIL tests the live site.

How Inth catches this

  • Code audit: flags a pull request that adds a tag, SDK or cookie write outside the consent check.
  • Website audit: records cookies and requests on first load, after "Reject" and after "Accept", with the page, time, visitor region and consent state. These are the observations CNIL inspectors make.
  • Consent banner: in the EU/EEA, UK and Switzerland the default policy is opt-in, so nothing optional loads until the visitor chooses. Google Consent Mode v2 defaults to denied and sends an update on choice.
  • Evidence: consent records with each visitor's choice, country and policy.

Inth Consent applies the policies you choose. Your legal team decides which rules your business follows, including the wording of each purpose.

Illustrative pattern, not the defendant's code (Google Consent Mode v2):
// Before: Google tags run with full storage on first load
gtag('config', 'G-XXXX');

// After: storage denied by default, updated only when the visitor accepts
gtag('consent', 'default', {
  ad_storage: 'denied', ad_user_data: 'denied',
  ad_personalization: 'denied', analytics_storage: 'denied',
});
// on accept: gtag('consent', 'update', { ad_storage: 'granted', analytics_storage: 'granted', ... })
gtag('config', 'G-XXXX');

Cases in the library

Sources and limits

Source review: 17 October 2026. Amounts are those stated in the decisions and CNIL announcements; currencies are euros and are not converted. This page is not legal advice. Inth wrote the technical checks; they cannot decide which laws apply or prove compliance.