On 22 October 2026, the restricted committee of France's data protection authority, the CNIL, fined Fnac Darty Participations et Services €6 million and Fnac Direct €1 million, €7 million in total. The CNIL announced the sanction on 29 October (deliberation SAN-2026-015). The finding is that the Fnac mobile app placed and read a tracker on users' devices without valid consent. This is not a case about a company that never asked. It is about a company that asked, was told no, and tracked anyway.
What the committee found
The published deliberation on Légifrance records that users could tap "Continuer sans accepter" (continue without accepting) in the app's consent banner. Even so, the companies went on reading and writing data on their devices through an API. According to the CNIL, the tracker sent a Fnac user identifier and product-activity data to a third-party domain. That data was used for personalised recommendations, complementary-product suggestions and training the recommendation algorithm.
The legal question was whether that tracking fell inside the exemptions in Article 82 of the French Data Protection Act. Article 82 transposes Article 5(3) of the ePrivacy Directive 2002/58/EC. It requires consent for storing or accessing information on a user's terminal, except where the access is for transmission or is strictly necessary to deliver a service the user explicitly requested. The committee held that the operations did not fall within those exemptions. They therefore could not run without prior consent. It ordered the companies to show within one month that their new tool collects consent where needed, on pain of €10,000 for each day of delay.
The case began with a complaint from the privacy group noyb. On 14 September 2023 noyb filed complaints in France against the Fnac, SeLoger and MyFitnessPal apps. The CNIL's online audit of the Fnac app took place on 6 March 2024, according to PPC Land's reading of the decision.
The strongest case for the fine
The case for severity is easy to state. Consent is only meaningful if refusal works. A banner whose "no" button changes nothing is theatre, and it corrupts the market for compliant firms, which pay for lower-yield, consent-based advertising and personalisation while rivals quietly do not. Mobile apps are also harder to inspect than websites: users cannot open developer tools, so regulators and complainants are often the only check. Reading the Fnac app's behaviour as a refusal-ignoring design is a reasonable reading of the record.
Why this is the right line, and where it could go wrong
On the facts reported, this enforcement is proportionate for one reason: the violation is objective. A user said no and the app behaved as though they had said yes. Regulators can test for that without making contested judgments about what counts as a reasonable business model. Enforcement of this kind raises compliance without punishing innovation. Firms learn that the consent signal must reach every SDK and API in the stack, not just the visible banner.
Three cautions apply.
- The exemption line is narrow. The committee found that product personalisation and algorithm training fall outside the "strictly necessary" exemption. That is consistent with the ePrivacy text, but it means even first-party recommendation features need consent when they rely on device-level identifiers. Regulators should keep distinguishing sharing an identifier with a third-party domain from purely local, privacy-preserving personalisation. Otherwise the rule will push developers away from the privacy-protective option.
- Penalties should track the harm. The Légifrance text says the rapporteur's report of 3 June 2026 proposed a fine and an injunction. Reports differ on the proposed figure, and I could not confirm an amount in the decision text. The fine is therefore best read as one calibrated to scale and conduct. The companies' own explanation, which the CNIL does not appear to have accepted as a defence, is a configuration error. A misconfigured SDK is a compliance failure but not the same as deliberate surveillance. Regulators should keep that gap visible in how they set fines.
- Compliance needs tooling, not just threats. Many app teams ship third-party SDKs whose default behaviour they do not fully control. A €10,000 daily penalty is a clear signal, but regulators and standards bodies would do more good by publishing testing methods and SDK-level guidance that teams can run before release.
Scale and reach
PPC Land reports that the Fnac app was downloaded more than 1.5 million times in France between March 2023 and March 2024, with an average of about 37,400 daily users. That is a real but not enormous user base. The case is not a Big Tech enforcement action, and its significance is precedent rather than size. It extends the CNIL's long-running cookie enforcement from websites to the in-app environment and shows that a complaint from a civil-society group can reach a decision on mobile tracking. For developers, the practical message is to audit what every SDK does after a user declines, not just what the banner shows.
What to watch
The next signals are whether the CNIL accepts the companies' revised consent tool within the one-month deadline, and whether it acts on the other two apps in noyb's September 2023 complaints. If it stays disciplined, focusing on cases where a refusal was demonstrably ignored, French enforcement can protect users without discouraging useful product features.