Docteur Bet
Cookies

Five cookies at most, and only if you want them

This site sets two audience-measurement cookies and up to three campaign-measurement cookies (Google and Meta), and nothing else. They are only placed after you agree, and the site works exactly the same if you decline. This page says which ones, why, and how to change your mind.

Last updated: 12 October 2026.

What is set, and when

Nothing until you answer. While the banner is waiting, no measurement script is loaded and no request goes to Google or Meta. That is not a turn of phrase: open your browser's Network tab and there is nothing there.

If you accept, Google (Analytics and Ads) and Meta (Facebook, Instagram) set at most five cookies:

CookieSet byLifetimeWhat it does
_gaGoogle13 monthsTells one visitor from another, without knowing who
_ga_XXXXXXXXGoogle13 monthsLinks the pages of a single visit together
_gcl_auGoogle90 daysTells us that a sign-up followed one of our Google ads
_fbpMeta90 daysTells us that a sign-up followed one of our Meta ads
_fbcMeta90 daysOnly set if you arrive by clicking a Facebook or Instagram ad

That is all. The last three only measure our campaigns: how many sign-ups an ad brought in. No third-party cookies beyond those five.

What we use it for

To know how many people read a page, where they arrive from, whether they come back, and which ads lead to a sign-up. Nothing more. The only events measured are page views, creating an account, leaving for the payment page, and starting a trial. At Meta, those three events carry their standard names — CompleteRegistration, InitiateCheckout and StartTrial, the last one with the chosen plan and its price. If you accept, the email address you type into a form on the site (sign-up, log-in) is also sent to Meta, irreversibly encrypted (hashed) in your browser, to link a sign-up to an ad: this is Meta's "advanced matching", switched on on 12 October 2026. Neither the password nor any other field is sent.

We sell nothing on. If you accept, Google receives ad_storage and ad_user_data as granted — that is what lets a sign-up be linked to an ad; ad_personalization stays permanently denied. Meta uses these measurements to count the results of our ads and to optimise their delivery, that is, to show them to the people most likely to sign up.

Our commitment, made on 12 October 2026: we create no retargeting audience from your visits — neither at Google nor at Meta. If that were ever to change, this page would be rewritten first, and you would be asked for your consent again.

Two other cookies exist, strictly necessary and set without consent: db_session keeps you signed in for 30 days if you sign in, and db_pays keeps for one year the country you chose without being signed in. Neither measures anything. See the privacy policy.

Declining costs you nothing

The site is identical either way: same content, same speed, same behaviour. Nothing is reserved for those who accept, and nothing is degraded for those who decline.

The two buttons on the banner deliberately share the same size, colour and weight. Declining must be as easy as accepting, otherwise the consent is not one.

Changing your mind

 

This button reopens the banner. Your new choice replaces the old one immediately, without a reload. You can come back here from the Cookies link at the bottom of every page.

If you withdraw, measurement stops at once. Cookies already set expire on their own; you can also delete them from your browser settings, at any time and without telling us.

Where your choice is kept

In your browser's local storage, under the key db-consentement, in this form:

{ "v": 3, "mesure": false, "date": "2026-10-12T09:14:22.031Z" }

It is not a cookie: it is never sent to our server. It stays on your device, and its only job is to stop us asking again on every page.

It expires after thirteen months, and becomes void if we add a purpose or a recipient — consent given for audience measurement alone would not cover anything else. That is what happened on 12 October 2026: campaign measurement, then Meta, were added, and everyone was asked again.

How to check

Do not take our word for it.

Before answering the banner, open the developer tools, Network tab, and reload: no request goes to googletagmanager.com, google-analytics.com or connect.facebook.net. Application or Storage tab: no cookies.

Decline, reload: still true.

Accept: the _ga and _fbp cookies appear, and so do the requests to Google and Meta.