Skip to content

Consent · 16 November 2026

No cookie, still a tracker: what the CNIL's Fnac Darty fine says

On 22 October 2026 the CNIL's restricted committee adopted deliberation SAN-2026-015 and fined two Fnac Darty companies €7 million for a tracker in the Fnac mobile app used without consent. The decision was published on 29 October 2026. This note restates what those primary sources say, then separates that from what we infer for a website. It is not legal advice.

What the CNIL decided

The restricted committee fined Fnac Darty Participations et Services €6 million and Fnac Direct €1 million for a breach of article 82 of the French Data Protection Act (loi Informatique et Libertés). Those figures are in both the CNIL's 29 October 2026 announcement and the operative part of the deliberation on Légifrance.

The case began with a complaint from None Of Your Business (NOYB). In March 2024 the CNIL inspected the Fnac mobile app; the deliberation records an online inspection on 6 March 2024. The CNIL found that API requests were sent to a third-party domain. Those requests contained a user identifier assigned by Fnac and information about the user's activity, such as products viewed.

The CNIL found that this tracker was used to show personalised products from the user's browsing history, complementary products such as accessories, consumables or related services, and similar products, and to train the recommendation algorithm. It held that those purposes were not solely to carry or facilitate electronic communication, and were not strictly necessary to provide an online communication service the user had expressly asked for. They therefore fell outside the exemptions in article 82 and required prior consent.

The CNIL also found that the requests continued after the user clicked “Continuer sans accepter” (“Continue without accepting”) on the consent banner. The restricted committee treated that as a failure to honour a refusal.

The deliberation also issues an injunction: both companies must show that the processing now complies with article 82, with evidence sent to the restricted committee within one month of notification. After that month, the injunction carries a penalty of €10,000 per day.

Why “no cookie” is not the test

Article 82, which transposes the ePrivacy rule into French law, is not limited to cookies. It covers storing information on a user's device, or accessing information already stored there. The CNIL treated an identifier sent in a request to a third-party domain as a tracker.

The CNIL's announcement states that the restricted committee also relied on its established approach to trackers used for personalisation and commercial targeting, which fall outside the exemptions. The deliberation adds a further point: the same single tracker served several purposes. Even if showing similar products could, in some implementations, be strictly necessary, that purpose could not be separated from the others here. A tracker that serves several purposes is exempt only if none of those purposes requires consent.

What we infer from that, and what the decision does not itself say about websites: if you only look for a cookie in the browser, you can miss a tracker that lives in a request payload. The test is access to, or storage of, information on the device — not whether the Network row happens to be labelled “cookie”.

What the decision does not say

This decision is about a mobile app and product recommendations. It does not name any web analytics vendor. It does not approve or prohibit a cookieless pageview count. It is not legal advice, and we are not a law firm. Your counsel owns the call for your site.

A five-minute check after Reject

You can see what your own site does after Reject without waiting for a regulator. Open the site in a private window, open DevTools, and do not grant consent. Click Reject. Then look at Network for requests to other domains, and read those payloads for a stable identifier. Also look at Application → Cookies and localStorage. The same walkthrough, with script-size and request checks, is in Privacy-friendly analytics: 5 checks you can run on any script.

Where a cookieless pageview count sits

Cookie Free Analytics records a pageview, the source, five UTM tags, and a named goal if you fire one. The script does not set a cookie or a localStorage identifier. How a visitor is counted, and what the script sends, is on /methodology and /docs/what-the-script-sends. That is a description of this product, not a finding in SAN-2026-015.

Ad tags, heatmaps and anything that still recognises someone still need their own consent path. A cookieless pageview count does not make those tags lawful. Counsel decides. The same question, in English and in French, is on Do I need a cookie banner for analytics? and at /fr/do-i-need-a-cookie-banner. The hole that appears in a cookie report after Reject is explained on the consent gap.

Questions

Is a tracker without cookies still covered by consent rules?
Under the rule the CNIL applied here, yes. Article 82 of the French Data Protection Act covers reading or writing information on a device, not only cookies. In this case the tracker was a user identifier assigned by Fnac, and information such as products viewed, sent to a third-party domain.
Did the CNIL fine concern web analytics?
No. The decision concerns a tracker in the Fnac mobile app, used for product recommendations and to train a recommendation algorithm. It does not name a web analytics vendor, and it is not a ruling on a cookieless pageview count.
What should I check on my own site?
Open the site in a private window, open DevTools, and click Reject. Look for requests to other domains, and for persistent identifiers in those payloads, in cookies, and in localStorage. A five-check walkthrough is in Privacy-friendly analytics: 5 checks you can run on any script. Your counsel owns the call for your site.

Do I need a cookie banner? · Consent gap · Five checks · What the script sends · How a visitor is counted

All notes · How a visitor is counted