What French law says
In France, the core text is article 82 of the Data Protection Act of 6 January 1978 (loi Informatique et Libertés), which transposes the European “ePrivacy” directive. It requires a website publisher to inform visitors clearly about what trackers are for and how to refuse them, and to obtain consent before reading or storing anything on their device. Two exceptions: trackers whose sole purpose is to enable electronic communication, and those strictly necessary for a service the visitor has asked for.
The CNIL set out how to apply this text in guidelines (adopted in 2019, amended on 17 September 2020) and a recommendation of the same date, backed by a questions-and-answers page. “Cookie” there also covers pixels and the browser’s local storage: what matters is what the tracker does. The emails and texts you send your guests follow other rules, set out in our article on newsletters, SMS and GDPR.
Consent, as the CNIL sees it
- Before, not after: until the visitor clicks, only exempt trackers may run.
- Through an action: clicking “Accept”, ticking a box. Carrying on browsing is not consent, and neither is accepting terms of use.
- Rejecting as easily as accepting: if one click accepts, one click must reject. The CNIL recommends a “Reject all” button at the same level as “Accept all”. A refusal hidden on a second screen does not meet the requirement.
- Withdrawing at any time, just as easily: a “Manage cookies” link in the footer of every page is the usual answer.
- Keeping the choice without nagging: acceptance or refusal is stored so the question is not asked on every page. The CNIL says keeping it for six months is good practice, to be assessed case by case.
Trackers that need no consent
The CNIL lists the trackers exempt from consent. For a restaurant, the most common are the one that remembers the visitor’s cookie choice, login for a members’ area, the basket if you sell gift vouchers online, expected interface preferences such as language, and load balancing across servers.
Audience measurement, under conditions
Counting visits can be done without consent if the tool only measures your own site’s audience, on your behalf alone, and produces only anonymous statistics, with no cross-matching with other processing and no tracking of the visitor across other sites. The CNIL also recommends a tracker lifetime of about thirteen months, with no automatic extension, and keeping the data collected for twenty-five months at most, with visitors informed, for instance in your privacy policy.
Third-party tools on a restaurant website
This is where it all happens. Your site itself sets little; the services you embed in it set the rest. What the site should show first is the subject of our article on restaurant website essentials.
| Embedded element | What to check |
|---|---|
| Booking widget | What its publisher sets, and whether it documents it |
| Interactive map | The provider’s trackers, and consent asked before showing it |
| Embedded video | Consent asked before the player loads |
| Social media buttons | Consent asked if the network sets trackers |
| Advertising pixel | Always subject to consent |
| Web fonts | Where they are hosted: ask your web provider |
For a video or a map, the CNIL states that the site publisher collects consent before the provider sets any tracker that requires it, either in the banner or through a placeholder that stands in for the content until the visitor clicks. Refusal must never block access to the site. Share buttons often let the network set trackers for other uses, such as advertising: consent is then required.
A link rather than an embed, where you can
Replacing an embedded element with a link shortens the list. A picture of your location that links to a map service loads nothing until the visitor clicks. The same goes for bookings: besides the code to embed in a page, gonnabook.it gives you a “Direct link” to your booking page, which a button on your site can open without embedding any third-party code. To compare the options, see adding a booking widget to your website.
Take stock in an hour
The French administration sums up the process in four steps: identify the trackers, work out whether they need consent, collect it before using them, let visitors withdraw it. The first one is within your reach.
- List what you have added: booking widget, map, videos, pixel, analytics, review widget, special font.
- See what the site sets: open a private window, load your site without touching the banner, then look at the site’s cookies and storage in the browser’s developer tools. Anything that appears before you click must be exempt.
- Sort and fix: remove what you no longer use, swap for a link what you can, block the rest until the click.
- Update your privacy policy, which lists the trackers and their purposes.
Repeat with every addition. For your guest data, the article on GDPR and your guest list explains what your restaurant is allowed to do.
Frequently asked questions
Does every restaurant website need a cookie banner?
Under French rules, no. Consent is only required for trackers that are not strictly necessary for the site. If your site only uses exempt trackers, such as remembering the language or audience measurement that meets the CNIL’s conditions, no consent banner is needed. As soon as an advertising pixel, a video or a social button sets trackers, you need one.
How long should the visitor’s choice be kept?
In its questions and answers, the CNIL says that keeping the visitor’s choice, acceptance or refusal, for six months is good practice, to be assessed case by case. The aim is not to ask again at every visit without letting consent run forever. Visitors must be able to change their mind at any time, through a link available on every page.
Does an embedded video or map need consent?
If the provider sets trackers that require consent, yes. The CNIL states that the site publisher must collect that consent before the tracker is set, in the banner or through a placeholder that replaces the video or map until the click. Refusal must not block access to the site. A clickable image linking to the service avoids the question.
Sources
- Légifrance, Loi n° 78-17 du 6 janvier 1978, article 82, version in force, accessed 18 November 2026 (in French).
- CNIL, Les lignes directrices modificatives et la recommandation de la CNIL, accessed 18 November 2026 (in French).
- CNIL, Questions-réponses sur les lignes directrices modificatives et la recommandation “cookies et autres traceurs”, questions 21 to 23, accessed 18 November 2026 (in French).
- CNIL, Cookies et traceurs : que dit la loi ?, exempt trackers, accessed 18 November 2026 (in French).
- CNIL, Cookies : solutions pour les outils de mesure d’audience, accessed 18 November 2026 (in French).
- Entreprendre.service-public.fr, Gérer les cookies et autres traceurs sur le site internet d’une entreprise, DILA, accessed 18 November 2026 (in French).