Privacy policy

Last updated: 6 September 2026

BolDeCuisine (“we”) publishes the BolDeCuisine mobile app and website, a community for Thermomix® TM7 users. This policy explains what data we collect when you use the app, why, and what your rights are.

Data controller: Cédric, reachable at cedric@boldecuisine.com.

Data we collect

When you create an account and use the app, we collect:

  • Account information — name and email address, used to sign you in.
  • Content you post — messages in the forum or in a private conversation, and photos you share in one.
  • Event registrations — the workshops and meet-ups you sign up for.
  • Push notification token — to send you notifications (new messages, recipes, events), if you allowed them.
  • App usage — when you open and close the app, and which screens you spend that time on. The screen, never the item: “a recipe page”, never which recipe.
  • Minimal technical data — error logs and device information needed to run the service and support you.

We neither collect nor sell data for advertising purposes, and the app embeds no third-party advertising tracker.

Why we use this data

  • To run your account and sign you in securely.
  • To show and keep up the community's content: recipes, videos, forum, events, newsletters.
  • To send you the notifications you chose to switch on.
  • To put you in touch with your Thermomix® advisor by private message.
  • To measure how the app is used — how many members open it, how often, and which parts they use — so your advisor knows what their community makes use of.
  • To keep the app secure and diagnose technical problems.

Where your data is stored

The app's data is hosted by Supabase (database, authentication and file storage), our infrastructure provider. We share your data with no other third party beyond the processors strictly needed to run the service (hosting, push notification delivery).

How long we keep your data

The usage data described below is the exception: it is deleted automatically after twelve months, whether or not your account is still active.

Your data is kept for as long as your account is active. If you delete your account, your personal information and your content are deleted or anonymised within a reasonable time, subject to any legal retention obligations.

Website audience measurement

There is none. The boldecuisine.com website carries no audience-measurement tool, no cookie, no pixel and no third-party tracking script: your visit is not analysed, not profiled, and not passed to anyone. The typefaces are served from this site rather than from a CDN, so beyond the pages themselves your browser contacts no other server. That is also why this site shows no cookie banner — it has nothing to ask you. The mobile app likewise contains no advertising tracker.

One thing is counted, and it says nothing about you: our marketing supports (magnets, flyers, cards, online ads) point at a short address of the form boldecuisine.com/s/xxx, which adds 1 to a counter before forwarding you to the page you were promised. That counter holds “this support brought 14 visits on 12 March”, and nothing else: no IP address, no cookie, no identifier, no line about you — there is nobody in it. It exists so we know whether a printed support is worth printing again, or an ad worth continuing.

Three more counters, built in exactly the same way, follow what happens next: how many people left for the App Store or Google Play from that support (the boldecuisine.com/g/xxx address), how many installed the app, and how many created an account. On Android the install is tied back to the support by the “referrer” Google Play hands the app on first launch; Apple offers no equivalent, so those last two counters stay at zero on iPhone. These are again totals per support per day: no visit identifier, no device identifier, and no link between an account and the support its owner came through. Nobody is followed from one step to the next — these are four numbers side by side.

For this to work, the home page reads the support's code from the address (the “?s=xxx” the redirect adds) so it can point the download buttons at it. That code names the support, never you; it is not saved in your browser, not passed to anyone, and it is gone as soon as you leave the page.

One single thing is saved in your browser: which platform (iPhone or Android) you chose to view the screenshots for on the home page, so they come back the same way next time. It is a display preference, it never leaves your device, and clearing the site's data removes it.

Usage measurement in the app

The app does measure usage — said here rather than left to be assumed otherwise. It records when you open and close it, and which screens you spend that time on, so that the advisor running your community can tell whether it is being used: how many members open it in a week, for how long, and which parts they use.

Three limits hold it in place. We measure it ourselves, on our own infrastructure: no third-party analytics tool is embedded in the app, and nothing leaves the processors listed above. It records screens and never items: nothing in it says which recipe, which message or which event you opened. And it is kept for twelve months, then deleted automatically.

Only the advisor or advisors of your own community can see it, and us. Never another community, and never anyone else.

Your rights

Under the GDPR you have the right to access, rectify, erase, restrict and port your data, as well as the right to object. To exercise those rights, contact us at cedric@boldecuisine.com. You can also edit your profile or delete your account from within the app.

Children

BolDeCuisine is not aimed at children and is not intended to be used by anyone under 16.

Changes to this policy

We may update this privacy policy. We will tell you about any significant change in the app or by email.

Contact us

For any question about this policy or your personal data: cedric@boldecuisine.com.