As of November 14, 2026. On October 29, 2026, the CNIL, France's data protection authority, published a decision entitled "Cookies et application mobile : sanctions de 7 millions d’euros à l’encontre des sociétés FNAC DARTY PARTICIPATIONS ET SERVICES et FNAC DIRECT" (cookies and mobile app: fines totalling 7 million euros against the two companies) (CNIL page, consulted on November 14, 2026). The case is not about a misconfigured cookie banner, nor about an advertising SDK forgotten in the code: it is about API requests sent by a mobile app to a third-party domain in order to personalise recommendations. That is exactly the kind of feature a product team can ship without ever talking to a lawyer. What follows covers what the decision says, who is concerned, the questions to ask before putting a personalisation feature into production, and what remains open.

What the decision says

On October 22, 2026, the CNIL's restricted committee imposed fines totalling 7 million euros: 6 million euros against FNAC DARTY PARTICIPATIONS ET SERVICES and 1 million euros against FNAC DIRECT. The procedure started with a complaint from the association None Of Your Business (NOYB); the CNIL then inspected the mobile app in March 2024.

The mechanism described on the page is easy to grasp, which is what makes it instructive:

  • The channel: within the app, requests were sent through an API to a third-party domain.
  • The content: those requests carried an identifier assigned to the user and information about their activity, such as the products viewed.
  • The purposes: displaying personalised and complementary products in the app, suggesting similar products, and training the recommendation algorithm.
  • Consent: none was collected. The CNIL considers that these operations do not fall under the exemptions provided for trackers by Article 82 of the French Data Protection Act (loi Informatique et Libertés), and therefore could not be carried out without the prior consent of the people concerned.

The fine comes with an injunction: within one month of notification of the decision, the two companies must demonstrate that their new tool collects consent where it is required, subject to a penalty of 10,000 euros per day of delay.

Why a product manager should stop on this

Most teams associate consent with two visible objects: the cookie in a browser and the third-party SDK in an app. The CNIL page mentions no SDK at all. The starting point is an API call, the kind of integration a team adds in a few days to plug in a recommendation engine, an analytics tool or an emailing service. Nothing in the interface signals it to the user, and nothing signals it to the person writing the specification either.

Article 82 of Law No. 78-17 of January 6, 1978 sets the general rule: the user must be informed, and consent is required, except for what is "strictement nécessaire à la fourniture d’un service de communication en ligne à la demande expresse" (strictly necessary to provide an online communication service at the express request) of the user (Article 82 on Légifrance, consulted on November 14, 2026). The decision shows how that exemption reads for an everyday feature: personalising a storefront and training an algorithm were not deemed strictly necessary to the service the user asked for.

The consequence for a product fits in one sentence: the question is not "is there a cookie or an SDK?", but "which piece of data tied to this user goes to whom, and for what?". It is a product question before it is a technical one, because the specification decides the data flows.

Who is concerned, and from when

The injunction and the penalty only target the two companies fined, with a deadline running from notification of the decision. For other publishers, the decision creates no new rule: Article 82 already applies. It does, however, give a concrete reading of that rule, published on October 29, 2026, which concerns first of all:

  • mobile app publishers that send a user identifier to a provider to personalise content or products;
  • teams that train or fine-tune a recommendation model on user behaviour with a third-party service;
  • startups selling that kind of service to apps: their customers will ask about consent in tenders.

On the split of roles, the CNIL sheet "Applications mobiles : comment intégrer des SDK et respecter la vie privée des utilisateurs ?" (mobile apps: how to integrate SDKs and respect users' privacy), published on January 21, 2025, states that the publisher, as data controller, must ensure compliance, and that the SDK must respect users' consent where it is required (CNIL sheet, consulted on November 14, 2026). The same logic holds when the integration goes through an API rather than an SDK: the app is what triggers the transfer.

The questions to ask before going to production

None of these questions requires legal expertise. They belong in a specification review, just like performance or accessibility.

  1. Which domains receive data from the app? The list is built flow by flow: domain called, data sent, moment of sending. In the case fined, the identifier at stake had been assigned to the user by the publisher itself: an internal identifier does not escape the question. A simple test is to watch the traffic of a test phone at first launch, before the user has made any choice.
  2. What is each flow for? A flow that delivers the requested service (showing the basket, processing the payment) is not handled like a flow that personalises, measures or trains a model. One purpose per flow, written in the specification, keeps a flow that serves the service from also serving something else that nobody decided.
  3. Does the flow wait for consent? Order matters: a call sent before the user's choice cannot be taken back. The acceptance criterion is simple to write: without consent, no request to this domain for this purpose. And a refusal must be honoured for as long as it stands.
  4. What does the provider do with the data? A recommendation engine may use the events it receives on its own account, for instance to train a model shared across customers. The provider's contract and documentation must answer that; otherwise the question goes up before signature, not after launch.
  5. Could the proof be produced within a month? The injunction in the decision allows one month to demonstrate that a tool collects consent. A good maturity test is to ask whether the team could put that file together in that time: inventory of flows, purposes, consent screens, screenshots of tests without consent.
  6. What happens if the answer is no? Postponing a personalisation feature until consent is wired in is an ordinary product trade-off. The way to explain it without closing the door is the same as for saying no to a feature request: name the cost, offer a date, keep the request alive.

These points are worth adding to the team's definition of done rather than leaving them to an occasional review. The role that owns the backlog is often best placed to do it, as described in the article on wearing both the Scrum Master and Product Manager hats.

What remains open

Where "strictly necessary" ends. The decision concerns personalisation and algorithm training that the user had not expressly requested. The page does not say how a recommendation that the user switches on personally, through an explicit setting, would be treated. That case is judged against the text of Article 82, flow by flow.

The detail of the decision. The page published on October 29, 2026 summarises the deliberation; it does not describe the companies' new tool nor how the CNIL will check the demonstration it requires. A founder who wants to learn from it should read the deliberation itself, not stop at the commentary around it.

Server-side integrations. The decision targets requests sent from the app. Architectures where the app sends everything to its own server, which then passes data to third parties, are not covered by this page. The prudent course is to apply the same set of questions, purpose by purpose.

Going further

A roadmap is also judged by what it avoids shipping too early: on running a B2B product roadmap, see two years owning a B2B CRM roadmap. To discuss a specification or a launch plan, a slot can be booked from the contact page.

Sources

  • CNIL, "Cookies et application mobile : sanctions de 7 millions d’euros à l’encontre des sociétés FNAC DARTY PARTICIPATIONS ET SERVICES et FNAC DIRECT", published on October 29, 2026: cnil.fr (consulted on November 14, 2026).
  • Légifrance, "Article 82 - Loi n° 78-17 du 6 janvier 1978 relative à l'informatique, aux fichiers et aux libertés": legifrance.gouv.fr (consulted on November 14, 2026).
  • CNIL, "Applications mobiles : comment intégrer des SDK et respecter la vie privée des utilisateurs ?", published on January 21, 2025: cnil.fr (consulted on November 14, 2026).