What we know about you, and why
An account if you create one, a payment if you subscribe, and audience and campaign measurement (Google and Meta) only if you accept it. No retargeting audience built from your visits, nothing sold on. This page says what is true, what changed, and how to check it.
Last updated: 12 October 2026.
What does not exist here
- Nothing is sold. We do not sell or rent any data, to anyone.
- No retargeting audience. Our commitment, made on 12 October 2026: we build no retargeting audience from your visits, neither at Google nor at Meta. Google's ad-personalisation signal is permanently refused. Meta uses the measurement to count and optimise the delivery of our ads; we do not ask it to retarget you. If that were ever to change, this page would be rewritten first, and your consent asked again.
- No tracking from one site to another on our part. What we measure stops at this domain and at our own ads.
- No needless requests to third parties. Fonts are served from our own server, and club crests pass through it: your browser never contacts SportMonks.
Your account, if you create one
You do not need an account to read the site. You need one for the web app, for tracking your bets with virtual stakes, and for subscribing. It is the same account as in the mobile app: our server manages it, and the site only relays it.
- What we keep: your email address, your country (it decides which operators we are allowed to show), and your password, which the site passes to our server without ever keeping it itself. Your first name and photo if you add them.
- Signing in with Google or Apple: the sign-in page then loads their script, and they pass us your email address. These scripts are loaded on that page only.
- The anti-bot check: at sign-up and sign-in, a Cloudflare Turnstile check verifies that you are not an automated program. Its script is loaded on the sign-in page only.
- Deleting your account is done from Account, without writing to us. Deletion erases the account on our server and cancels any web subscription still running.
Data specific to the app — notifications, tracked bets, purchases made in Apple's and Google's stores — is described in the app privacy policy.
Your subscription, if you subscribe
Payment happens on Stripe's secure page. Your card details are entered at Stripe and kept by Stripe: we never see them. We keep the state of your subscription (plan, trial, dates, cancellation) to know whether your account has Premium access. Invoices are kept for ten years, as accounting rules require. The details are in the terms of sale.
Cookies
Two are strictly necessary and need no consent:
db_session, set when you sign in, keeps your session for 30 days. The page's JavaScript cannot read it.db_payskeeps, for one year, the country you chose without being signed in.
Three to five more are only set if you accept audience and campaign measurement: _ga
and _ga_XXXXXXXX (Google Analytics, thirteen months) to count the pages read; _gcl_au
(Google Ads, ninety days) and _fbp (Meta pixel, ninety days) to know that a sign-up followed
one of our ads; _fbc (Meta, ninety days), only if you arrive by clicking a Facebook or
Instagram ad. The only events we measure this way are page views, creating an account,
leaving for the payment page, and starting a trial — at Meta under their standard names
CompleteRegistration, InitiateCheckout and StartTrial, the last one with the 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.
Declining costs nothing: the site is identical either way. The Cookies link at the bottom of every page reopens the banner at any time, and withdrawing your consent stops the measurement immediately.
What our host sees, and what we draw from it
Like any server, ours records the requests it receives in its technical logs: IP address, page requested, date, browser type. They are hosted in the European Union, in Frankfurt, and Apache deletes them after fourteen days.
These logs serve diagnosis, security, and counting the site's audience. That counting produces nightly totals per day and per page: pages read, visitors, referrers. Only those numbers are kept. No IP address is copied anywhere else, nothing is cross- referenced with another source, nothing is passed on, and nothing feeds advertising or targeting.
That particular count needs no consent: audience measurement that is strictly internal, aggregated, without a tracker in your browser and without following anyone from one site to another falls within the exemption set out by the CNIL, the French data protection authority. It therefore keeps working whether you accept Google Analytics or not — it is our fallback if you decline.
If you use Docteur Bet from an AI assistant
Our MCP server (mcp.docteurbet.fr, see its page) lets an assistant such as Claude or
ChatGPT read our public probabilities. It requires no account and only receives the
assistant's technical request — a team name, a competition, a match identifier — never your
conversation.
For each call it records the name of the tool used and the time, and nothing else: no IP address, no request content. As for the site, the web server keeps its technical logs for fourteen days, for diagnosis and security. This data is not cross-referenced, passed on or used for advertising.
What becomes of a form
The site's forms — contact, requests by sector or product, applications — send their content
by email to contact@docteurbet.fr, with any attachment. Nothing is written to a database,
and there is no customer-relationship tool behind them.
Where your data lives
Our server, our database and its logs are hosted by Amazon Web Services in the Frankfurt region, Germany: inside the European Union. Google (measurement, if you accept it; Google sign-in), Meta Platforms Ireland Ltd (campaign measurement, if you accept it), Apple (Apple sign-in), Cloudflare (anti-bot check) and Stripe (payment) each process the data they need, under their own policies. Google and Meta are American services: accepting measurement means accepting a possible transfer outside the European Union, under the EU–US Data Privacy Framework.
Your rights
You can access your data, have it corrected or erased, and object to measurement at any time. Most of this needs no help from us: your profile and country can be changed from Account, deletion too, and measurement is withdrawn through the Cookies link. For anything else, write to us.
How to check
Do not take our word for it. Open your browser's developer tools, go to the Network tab, and reload this page.
If you have not answered the banner yet, or if you declined: every request from this page goes to this domain and no other, and no measurement cookie appears in the Application or Storage tab.
If you accepted: you will see the requests to googletagmanager.com and
connect.facebook.net, and the measurement cookies. That is exactly what you authorised, and nothing more.
If this changes
This page was rewritten on 12 October 2026, the day campaign measurement — Google, then Meta — was added, and the banner asked for your consent again before anything was sent. That is the commitment we made right here.
It holds from now on: if we ever add a tracker, a new advertising purpose — a retargeting audience, for instance — or any mechanism that would follow a reader from one page to the next, this page will be rewritten first, and proper consent will be requested. We will not do it quietly.
Writing to us
A question about this page, a request about your data: contact@docteurbet.fr. You can also lodge a complaint with the CNIL (cnil.fr).