Privacy and data
The short version: without an account, we don’t know who you are. With an account, we know your email, your username and your favourites — nothing else.
The site works without an account
Rabiot is fully usable without an account, forms or identifiers: in that case we do not collect or process any personal data within the meaning of the GDPR. An account is optional and serves one purpose only: keeping your favourite recipes across your devices.
What we collect if you create an account
Your email address, your password (stored hashed, never readable by anyone — not even us), your username, your list of favourite recipes and the creation dates. That’s all: no name, no browsing history, no profiling. This data is strictly necessary to provide the service you asked for (legal basis: performance of a contract, Article 6(1)(b) GDPR).
For how long?
As long as your account exists. You can delete it at any time, in one click, from the “My account” page: deletion is immediate and permanent (account, username and favourites). Technical database backups are purged within 30 days at the latest.
Still no cookies, no trackers
The site sets no cookies and embeds no analytics or advertising tools. If you sign in, your session is kept in your browser’s local storage (localStorage), on your device — not in a cookie, and never shared with a third party. Fonts are hosted with the site: no request is ever sent to a third-party service.
What’s in your stash stays with you
The list of ingredients you select is stored only in your browser’s local storage, on your device, with or without an account. It is never sent to a server. You can erase it at any time by clearing your browser data.
Your rights
Everything is self-service from the “My account” page: access and portability (a button exports your data as JSON), rectification (username, email and password can be changed), erasure (account deletion button). You can also lodge a complaint with your data protection authority (CNIL in France, cnil.fr).
Who hosts what?
Account data and the recipe catalogue are stored in a Supabase database, a processor within the meaning of the GDPR. The public catalogue is baked into the pages when they are generated, server-side; your browser only talks to that database directly for account features (sign-in, favourites), never for simply browsing recipes.