App tracking requires consent under Section 3-15 of the Norwegian Electronic Communications Act where the app reads or sends information from the user's device for personalisation, recommendations or analytics. The exemption for what is strictly necessary is narrow. In October 2026 CNIL fined Fnac Darty EUR 7 million for such tracking and held that session replay always requires consent.
On 22 October 2026 the French data protection authority CNIL fined the Fnac Darty group a total of EUR 7 million for tracking in its mobile app without consent. Two weeks later CNIL published a recommendation on tools that record user sessions, known as session replay, and held that such tools always require consent. Both decisions rest on the French implementation of the ePrivacy Directive, which in Norway is implemented in Section 3-15 of the Electronic Communications Act. They are therefore directly relevant to Norwegian organisations with apps or websites using tools for personalisation, recommendations and user analytics.
What does Norwegian law say about app tracking?
App tracking is governed by Electronic Communications Act § 3-15, which prohibits storing or gaining access to information on the user’s communications equipment unless the user has been informed and has consented. The provision is found in the Electronic Communications Act, which entered into force on 1 January 2025, and it implements ePrivacy Directive Art. 5(3). Consent must meet the requirements of the GDPR, so that it must be freely given, specific, informed and unambiguous under GDPR Art. 4(11) and GDPR Art. 7.
The provision is technology neutral. It covers cookies, but also software development kits in apps, scripts recording clicks and movements, and API calls sending an identifier from the user’s device to a server. In Guidelines 2/2023, the EDPB has adopted a broad understanding of what constitutes access to information on the user’s equipment. The rules for websites are discussed further in the article on cookie consent.
When is tracking exempt from the consent requirement?
Under the second paragraph of Electronic Communications Act § 3-15, the consent requirement does not apply to technical storage or access carried out solely for the purpose of transmitting communications, or strictly necessary to provide an information society service explicitly requested by the user. The exemptions are narrow. What matters is whether the tracking is necessary for the service the user has requested, not whether it is useful to the organisation.
Login, shopping baskets and security features normally fall within the exemption. Personalisation, recommendations, marketing, statistics and analysis of user behaviour fall outside it, even where the organisation considers that these features improve the service. The same understanding of the exemptions underlies both French decisions.
What does the Fnac Darty case teach about app tracking?
In decision SAN-2026-015, CNIL fined Fnac Darty Participations et Services EUR 6 million and Fnac Direct EUR 1 million. According to CNIL’s account of the decision, the mobile app sent requests via an API to a third-party domain containing an identifier assigned to the user by Fnac, together with information about the user’s activity, including which products the user had viewed. The purpose was to display personalised, complementary and similar products and to train a recommendation algorithm. The tracking continued even where the user had chosen not to consent.
CNIL found that the operations neither served to transmit communications nor were strictly necessary for the service, and that they therefore required prior consent. In setting the fine, CNIL took into account that users had expressly refused, that the app had a large number of users, and that CNIL has a consistent and well-established practice on tracking for personalisation and targeting. The companies were ordered to demonstrate a consent solution within one month, subject to a periodic penalty of EUR 10,000 per day of delay. The case began with a complaint from noyb.
The case shows that the data flow and the purpose are decisive, not the technique used. An app sending a user ID and viewing history to a provider of recommendation services is subject to the consent requirement in the same way as a cookie on a website. Using the data to train an algorithm is a separate purpose that is not strictly necessary for the user either.
Does session replay require consent?
Session replay requires consent, and CNIL held in its recommendation of 8 October 2026 that none of the exemptions from the consent requirement can be applied to such tools. The tools reconstruct the user’s navigation as a video, including mouse movements, touches, clicks, scrolling and in some cases the content of form fields, and CNIL describes the risk to privacy as high.
CNIL recommends that the use of such tools be disclosed specifically on the first layer of the consent banner, and that the purposes be defined before the tool is deployed. The tool should have a function masking data that are not needed, and mouse movements should be masked in areas where authentication codes may be captured. The content of chatbot conversations, both questions and answers, should be masked because it may reveal sensitive information. The number of recordings and the use of identifiers should be limited in light of the purpose.
| Measure under CNIL’s recommendation | What the organisation should do |
|---|---|
| Consent | Start recording only after consent, without pre-ticked boxes |
| Information | Mention session replay specifically on the first layer of the banner |
| Purpose | Define the purposes in writing before deployment |
| Masking | Mask form fields, authentication codes and chatbot conversations |
| Limitation | Limit the number of recordings and the use of identifiers |
The recommendation is not binding in Norway, but it rests on the same rule as Electronic Communications Act § 3-15. In our assessment, the Norwegian Data Protection Authority and Nkom would reach the same result on the consent requirement. Recordings capturing health data or other special categories in form fields or chatbot conversations will in addition require a condition under GDPR Art. 9.
Who is responsible when a vendor supplies the tracking tool?
The organisation that places the tool in its app or on its website is responsible for obtaining consent under Electronic Communications Act § 3-15 and is the controller of the data collected. CNIL notes that the vendor designs the solution and determines its settings and functions, while the organisation deploys the tool to analyse its users’ behaviour, and that the allocation of roles must be assessed in each case. Where the vendor uses the data for its own purposes, for example to develop its own models or services, it may become a joint controller under GDPR Art. 26. The consequences of joint responsibility are discussed in the article on joint controllership and the Xandr case.
Where the vendor is a processor, an agreement under GDPR Art. 28 is required. The agreement should prohibit the vendor from using recordings and event data for its own purposes, regulate masking and retention, and give the organisation access to the settings governing what is recorded. The requirements for such agreements are discussed in the article on data processing agreements for SaaS. Because session replay and extensive app tracking often involve a high risk, the organisation should also consider whether a data protection impact assessment is required under GDPR Art. 35.
What should organisations with apps and websites do?
Organisations should review all tools that read or send information from users’ devices, not only the cookies on their website. Further articles on data protection are available on the data protection topic page.
- Map all SDKs, scripts and API calls in the app and on the website that send identifiers or activity data to the organisation’s own or third-party servers.
- Assess for each tool whether its purpose is strictly necessary for the service the user has requested, and place all others behind consent.
- Test that the tools actually stop when the user refuses, also in the app and on later launches.
- Disclose session replay and personalisation specifically on the first layer of the consent solution.
- Enable masking of form fields, payment details, authentication codes and chatbot conversations in session replay tools.
- Review the contracts with vendors of analytics, recommendation and session replay tools, and prohibit use of the data for the vendor’s own purposes.
Questions and answers
Does the consent requirement for app tracking apply where no cookies are used?
Yes. Section 3-15 of the Electronic Communications Act applies to all storage of and access to information on the user's device, irrespective of technology. Software development kits, API calls sending a user ID from the app and scripts recording clicks and movements are covered in the same way as cookies.
Is session replay strictly necessary to provide the service?
No. CNIL has held that none of the exemptions from the consent requirement apply to session replay tools. Their purpose is to analyse and improve the service, not to provide the service the user has requested. The Norwegian rule in the second paragraph of Section 3-15 contains the same two exemptions.
Can a Norwegian organisation be fined for tracking without consent?
Yes. The Norwegian Data Protection Authority and Nkom supervise Section 3-15 of the Electronic Communications Act, and where consent is lacking there is normally also no legal basis under the GDPR for the further use of the data. Infringements of the GDPR may lead to administrative fines under GDPR Article 83.
- CNIL, sanction against Fnac Darty for tracking in its mobile app, SAN-2026-015 (22 October 2026, published 29 October 2026)
- CNIL, recommendation on session replay tools, deliberation No 2026-114 (8 October 2026, published 5 November 2026)
- noyb, Fnac Darty fined €7 million (29 October 2026)
- Norwegian Electronic Communications Act (ekomloven, 2024) § 3-15
- Directive 2002/58/EC on privacy and electronic communications (ePrivacy Directive) Art. 5(3)
- EDPB, Guidelines 2/2023 on Technical Scope of Art. 5(3) of ePrivacy Directive (version 2.0)
- General Data Protection Regulation (EU) 2016/679 Arts. 4(11), 7, 26, 28 and 35
Next legal review: 31 January 2027