Session replay: the CNIL publishes its recommendation (05/11/2026)
On 5 November 2026 the French CNIL published its recommendation on the tools that replay your visitors' journey. The verdict: prior consent is mandatory, with no exemption. Here is what it changes for an SME that runs a website, and what to check in each of the four countries we work in.
In short
On 5 November 2026 the CNIL published its recommendation on session replay tools, adopted by deliberation no. 2026-114 of 8 October 2026 and published in the French Official Journal no. 0259 the same day[1][2]. These tools reconstruct a visitor's full journey on a website or app: mouse movements, clicks, keystrokes, scrolling. The CNIL settles the question many publishers had left open: these trackers fall under Article 82 of the French Data Protection Act, so they require prior consent, and no exemption applies to them[1][2].
What the recommendation says
The final text follows a long process: public consultation from 25 February to 22 April 2026, adoption on 8 October, publication on 5 November[1][2]. It addresses two distinct parties: the provider, who designs the solution and sets the defaults, and the publisher of the website or app, who deploys it[1]. Both are bound by the minimisation principle.
Four requirements shape the text.
- Consent, with no exception. Read and write operations on the terminal neither exclusively facilitate electronic communication nor are strictly necessary to deliver the service, so no exemption is available[2].
- Dedicated information at the first level. The CNIL recommends specific information about session replay at the first level of the consent management platform, because the technology is still poorly understood by the public[2].
- Purposes defined before deployment. Purposes must be specified, explicit and legitimate, and settled before the tool is switched on — not discovered afterwards in the recordings[1].
- Graduated masking. The provider must offer automatic and manual masking of images, forms, text fields, keyboard movements and chatbot content, with the most protective level applied by default when nothing has been configured[2]. The CNIL specifically asks that mouse movements be masked in authentication areas, to avoid incidentally capturing a credential[1][2].
Retention periods, by purpose
This is the most directly actionable part, because it carries figures. The recommendation distinguishes by use[2]:
| Purpose | Recommended retention |
|---|---|
| Detecting technical errors | A few months |
| Improving usability | A few months |
| Supporting customer service | A few hours after the session ends |
In other words, a recording kept for thirteen months just because that is the tool's default setting does not hold up. And if the user withdraws consent, the data must be deleted unless another legal basis justifies keeping it[2].
What it changes for an SME
The typical case is not a large group. It is a thirty-person company that installed a session replay tool during a website rebuild, to understand why the quote form was being abandoned halfway through. The tool stayed. It is still running, outside the cookie banner, with its original settings.
Three immediate consequences.
One. The tool is probably loading before consent. That is precisely the ground on which the CNIL has sanctioned trackers dropped without agreement — we covered it in our analysis of the 7 million euro fine against Fnac Darty over mobile app trackers. The difference now is that there is no grey area left to invoke.
Two. The recordings probably contain data that should never have been collected. A contact form replayed keystroke by keystroke is a name, a phone number, sometimes a case reference. A replayed checkout is a delivery address. If the site is a shop, that risk compounds with the state of the technical stack: see our piece on the Drupal Commerce flaw exploited in late October 2026.
Three. Nobody internally knows which retention period is set. It is the easiest point to fix and the one you can verify in ten minutes.
Netherlands, Belgium, France, Luxembourg: one rule, four regulators
Let us be precise about scope: the CNIL's recommendation is French doctrine. It does not apply directly to a Dutch, Belgian or Luxembourg company. But the consent obligation it interprets comes from Article 5(3) of the ePrivacy Directive, transposed in all four countries. And an SME established in one of them that addresses the French market is covered by the CNIL's reading.
| Country | National provision | Who enforces it |
|---|---|---|
| France | Article 82, Data Protection Act | CNIL[1] |
| Belgium | Article 10/2 of the Act of 30 July 2018 — the definition also covers pixels, local storage and fingerprinting | APD / GBA[4] |
| Netherlands | Article 11.7a of the Telecommunicatiewet | ACM for Article 11.7a; AP for the GDPR side — the AP has proposed taking over that supervision, without the transfer being enacted[5] |
| Luxembourg | Article 4(3) of the amended Act of 30 May 2005 | CNPD[6] |
We give no legal advice: for a specific situation, the national text and the competent authority govern. The useful takeaway lies elsewhere — as of today, French doctrine is the most detailed on these tools, and it is the one providers will build into their default settings. The other markets will benefit by knock-on effect.
The costliest trap: the provider's status
The recommendation qualifies the roles precisely, and that is where real liability sits. For read and write operations on the terminal, the provider is a joint controller. But as soon as it reuses the collected data for its own purposes — product improvement, statistical models, algorithm training — it becomes the sole controller of that subsequent processing[2].
Practical consequence: the question to put to your supplier is not whether it is GDPR compliant. It is whether it reuses the sessions recorded on your site for its own purposes, and where that is written in the contract. The answer sits in the terms, rarely in the sales deck. It is also a good moment to refresh your processor register: the same logic applies to any analytics or AI tool wired into your site, as we set out on our cybersecurity for SMEs page.
To do this week
- Open your site in a private window, reject all cookies, then list the outgoing network requests. If a session replay tool loads anyway, that is the first thing to fix.
- Inventory the tools involved: Hotjar, Microsoft Clarity, Contentsquare, Smartlook, FullStory, or a module built into your CMS or CRM. Name one owner per tool.
- In each tool's console, read off the configured retention period and compare it with the CNIL's benchmarks: a few months for error detection and usability, a few hours for customer support[2].
- Turn on masking for every form field, authentication area and chatbot dialogue. Verify it on a real recording, not on the ticked box.
- Add dedicated wording about session replay at the first level of your banner, not only in the detailed list[2].
- Write down the purpose you are pursuing before launching any new measurement campaign[1].
- Register whoever manages your site for the CNIL webinar on Tuesday 17 November 2026 devoted to this recommendation[3].
At CyberNovaLabs.io
We audit the consent banner, the trackers actually dropped and the retention periods on the sites we build and the sites we take over, across the four countries we operate in — from Brussels-based SMEs to Dutch, French and Luxembourg companies. The check is factual: we measure what leaves your site rather than reading the vendor's documentation. If you want to know what your site actually records today, book a call with us — thirty minutes is enough to produce the inventory. Priced on quotation.
Sources
- CNIL — Outils de rejeu de session : la CNIL publie sa recommandation pour guider les acteurs (05/11/2026)
- Légifrance — Délibération n° 2026-114 du 8 octobre 2026 portant adoption d'une recommandation concernant les outils de rejeu de session, JO n° 0259 du 05/11/2026
- CNIL — Webinaire « Outils de rejeu de session : la CNIL présente sa recommandation », 17 novembre 2026
- Autorité de protection des données (APD/GBA) — Cookies et autres traceurs, article 10/2 de la loi du 30 juillet 2018
- ACM — Uitvoeringstoets wijzigingsvoorstel cookiebepaling (article 11.7a Telecommunicatiewet)
- CNPD — Loi modifiée du 30 mai 2005 concernant la protection de la vie privée dans le secteur des communications électroniques (texte coordonné)
Qualified meetings, no lock-in.
Criteria in writing before launch, pay per meeting or monthly, stop with a simple email.
Read next
NGINX: five critical flaws patched urgently (18/11/2026)
Five critical flaws in NGINX, the software receiving traffic for more than 225 million websites, were fixed on 18 November 2026. Four authorities warned the same day. Your site can be exposed without having a single defect of its own.
Read the article →November 20, 2026 · 8 min readNIS2 Luxembourg: are estate agencies and syndics in scope?
Real estate appears in neither Annex I nor Annex II of the Luxembourg Act of 5 May 2026. But your supervisory authority already exists: the AED, on money laundering. Position as of 20 November 2026.
Read the article →November 6, 2026 · 7 min readAI and B2B email prospecting: 500 emails without spam
A language model writes 500 personalised emails in an hour. Gmail does not grade your prose: it counts complaints and checks your authentication. Here are the real thresholds, the four legal regimes across France and the Benelux, and the checklist to run before you hit send.
Read the article →November 6, 2026 · 8 min readNIS2 Belgium: are transport and logistics firms in scope?
Road freight is almost never a NIS2 entity in Belgium. Ports, rail, airports and courier services are. Here is how to settle your own case on one page, and what the CCB has expected since 18 April 2026.
Read the article →November 5, 2026 · 7 min readSymfony and Laravel patched same day: 9 advisories (04/11/2026)
Nine Symfony advisories and a Laravel patch on the same day, both relayed by CERT-FR. Four of these flaws repair an earlier incomplete fix, so having patched in October is not enough. The exact versions and the questions to ask.
Read the article →November 5, 2026 · 9 min readNIS2 France: are software vendors and IT providers in scope?
Publishing software does not put you in NIS2 scope; running, hosting or securing a customer's systems does. And in France, regulated digital entities fall outside the national framework, under a directly applicable European regulation. Position as of 5 November 2026.
Read the article →