Privacy & GDPR

CNIL Fine: Fnac Darty Pays €7M for App Tracking After a No

CNIL fine of €7 million for Fnac Darty: its app kept sending user IDs and viewed products to a third-party API after users refused. What apps should check.

By Jasper Koers Published 5 min read

On this page
  1. What the Fnac app did
  2. The timeline: from noyb complaint to CNIL fine
  3. Why "personalisation" was not exempt under Article 82
  4. No cookie, still consent: what this means for SDKs and APIs
  5. Checklist: make sure a "no" actually stops tracking
  6. What this means for your analytics

On 29 October 2026 the French data protection authority, the CNIL, published a €7 million fine against the Fnac Darty group for tracking in the Fnac mobile app. The CNIL's announcement and the full decision SAN-2026-015 on Légifrance, adopted on 22 October, split the fine into €6 million for Fnac Darty Participations et Services and €1 million for Fnac Direct, treated as joint controllers of the app. Both must prove compliance within one month or pay €10,000 per day of delay.

What makes this CNIL fine worth reading closely is not the amount. It is that no classic cookie was involved: the app called an API on a third-party domain, and the CNIL still applied the cookie rules. And it kept doing so after users had said no.

Not legal advice. This article summarises a published regulatory decision. Check your own situation with your DPO or a lawyer.

What the Fnac app did

According to the decision, the app performed read and write operations on users' phones through an API whose name and domain are redacted in the published text. Each request contained:

  • an identifier assigned by Fnac to the user, and
  • activity data, such as the products the user viewed.

That data was used to show personalised product recommendations, to suggest complementary products (accessories, consumables, related services) and similar products, and to train the recommendation algorithm.

The critical finding: the requests continued after users clicked "Continuer sans accepter" ("continue without accepting") in the app's consent banner. The CNIL calls the result a substantial infringement of the right to privacy and singles out the ignored refusal.

The decision gives the scale too: over 1.5 million downloads in France between March 2023 and March 2024, and about 37,400 daily users on average.

The timeline: from noyb complaint to CNIL fine

The case started with a complaint by noyb, filed on 15 September 2023 as one of three French complaints against apps (the others targeted SeLoger and MyFitnessPal). noyb alleged that the apps shared users' data with third parties as soon as they were opened, without a real choice.

Date Step
15 Sep 2023 noyb files the complaint
19 Sep 2023 Companies say they fixed a misconfigured tracker in the Android app
6 Mar 2024 CNIL carries out an online inspection of the app
24 Sep 2024 CNIL publishes its recommendation on mobile apps
19–20 Dec 2024 The API is switched off on Android and iOS; a replacement goes live in January 2025
1 Oct 2026 Hearing before the CNIL's restricted committee
22 Oct 2026 Decision SAN-2026-015 adopted
29 Oct 2026 Decision published

The API being switched off did not end the case. The CNIL ruled on the facts at the time of the inspection, and imposed the injunction because the companies had not shown, by the close of the investigation, that their replacement tool obtains consent where required.

Why "personalisation" was not exempt under Article 82

The legal basis is Article 82 of the French loi Informatique et Libertés, which implements Article 5(3) of the ePrivacy Directive. It requires prior consent before reading or writing information on a user's device, with two exemptions: operations whose sole purpose is to enable an electronic communication, and operations strictly necessary for an online service the user expressly requested.

Fnac argued the second exemption applied: users downloaded the app, opened it and accepted the terms, so recommendations were part of what they asked for. The CNIL went through each purpose and disagreed:

  • Personalised recommendations and commercial targeting: not exempt.
  • Complementary products: not strictly necessary for the service, so not exempt.
  • Similar products: could in theory be exempt, but because they ran through the same single operation as non-exempt purposes, consent was needed for all of it.
  • Training the algorithm: tied to commercial recommendations, so consent was needed.

The bundling point is easy to miss and broadly relevant. If one request serves an exempt and a non-exempt purpose at once, the exempt purpose does not rescue the request.

The CNIL also rejected the argument that the rules were unclear before its 2024 mobile app recommendation, pointing to guidance from 2013 and 2020 and earlier sanctions. Cooperation with the inspection was not treated as mitigating either. The fine was set with reference to the turnover of the wider group, which the CNIL put at over €10 billion in 2025.

The rule in Article 82 is about access to the device, not about cookies. An SDK that generates or reads an identifier on the phone and sends it to a third party is in the same position as a third-party cookie on a website. The CNIL said as much in its announcement, citing established case law that trackers used for personalisation and commercial targeting need consent. noyb's Lisa Steinfeld Leiser summed it up: "processing people's data for personalised advertising requires consent".

For web shops this is familiar ground. We covered how to measure revenue without cookies in privacy-first e-commerce analytics, and the CNIL's string of smaller simplified sanctions for cookie mistakes earlier this year. The Fnac case shows the same logic applied to an app, at a much higher price.

Checklist: make sure a "no" actually stops tracking

If you run an app or a web shop, these are the checks the Fnac decision points to:

  1. List every SDK and outbound API call in your app and on your site, including the ones added by marketing, recommendation or search vendors. Know which domains each one contacts and what identifier it sends.
  2. Map each call to a purpose and ask honestly whether it is strictly necessary for what the user asked for. Personalisation, recommendations, algorithm training, advertising and cross-device matching are not, according to the CNIL.
  3. Split multi-purpose requests. If you want to rely on an exemption for one purpose, it needs its own operation, separate from anything that needs consent.
  4. Test refusal, not just acceptance. Install the app fresh, refuse, and inspect the network traffic with a proxy. On the web, do the same in the browser's developer tools. Nothing non-exempt should leave the device.
  5. Test on every platform and release. Fnac said it fixed the Android version within days; the iOS app and later releases still need the same check.
  6. Keep evidence. The injunction asks the companies to demonstrate compliance. Screenshots, traffic captures and a vendor register make that possible.
  7. Watch the banner wording. If the button says "continue without accepting", the app has to behave that way.

For a broader view of what regulators expect from analytics specifically, see our GDPR compliance guide for web analytics. Enforcement is also picking up elsewhere: the Dutch regulator recently started investigating misleading cookie banners.

What this means for your analytics

The cleanest way to pass the refusal test is to have nothing to switch off. ClearAnalytics sets no cookies, stores nothing on the visitor's device and does not share visitor data with third parties or use it for advertising. It is designed to fit the profile regulators describe for audience measurement that should not need consent, though you should still check your full setup. The pricing page shows the free tier if you want to try it next to your current tools.

Frequently asked questions

Why was Fnac Darty fined by the CNIL?

The Fnac mobile app read and wrote information on users' phones and sent a user identifier and browsing data to a third-party domain for recommendations without valid consent. The requests also continued after users refused.

How much was the CNIL fine against Fnac Darty?

€7 million in total, €6 million for Fnac Darty Participations et Services and €1 million for Fnac Direct. The companies must also prove compliance within one month or pay €10,000 per day of delay.

Do apps need consent for SDKs and API calls that track users?

Under Article 82 of the French data protection act, which implements the ePrivacy rules, reading or writing information on a device needs consent unless it is strictly necessary for the service the user asked for or for transmitting a communication. The technology used, cookie, SDK or API, does not change that.

Is product recommendation strictly necessary under Article 82?

The CNIL said personalised and complementary product recommendations and algorithm training are not. Showing similar products could in theory qualify, but not when it runs through the same operation as non-exempt purposes.

  • cnil
  • fines
  • app-tracking
  • consent
  • eprivacy

Back to blog Read as markdown

Enjoyed this article?

Try ClearAnalytics for free and get privacy-first analytics for your website.