Adaptive Recipes beta · Updated 8 October 2026
Privacy and storage
You can browse public recipes without an account. This notice explains the information used when you sign in, save recipes or plan a meal.
What we keep and why
Your account email and protected authentication credentials let you sign in and recover access. Your profile, recipes, ingredient nutrition links, favourites, cooking history and book settings provide the features you choose to use. Account data is used to provide the service; limited operational information helps prevent abuse and fix faults.
Nutrition targets entered in the meal builder are saved in this browser. They are not a medical record, and we do not use them to infer health conditions. Avoid putting sensitive personal information in recipe descriptions or photographs.
Private and public recipes
The recipe visibility control determines whether your recipe is private or public. Other users cannot read or edit your private recipes, ingredient links or private image files. Publishing makes the recipe and its photograph available to anyone. Profile avatars are public images; personal book covers are private.
A private recipe must use private storage for its uploaded photograph. Copies of previously published content already downloaded or cached elsewhere may remain.
Cookies and browser storage
| Purpose | Storage and duration | Your control |
|---|---|---|
| Sign-in | Supabase authentication in local browser storage, refreshed while your session is active. | Sign out to end the local session. |
| Confirmation and recovery | Session storage remembers the pending email and a short-lived, user-bound recovery marker. The recovery marker expires after 15 minutes. | Close the tab or finish recovery. Passwords and email-link tokens are not stored in these markers. |
| Meal choices | Recipe selection and nutrition choices in local storage until you clear them. | Use the clear button below or your browser controls. |
| Shopping lists | Ingredient amounts, extra items and bought checkboxes in local storage for up to 90 days after your last edit. Lists are kept separately for each account or guest, recipe and serving size. | Start again inside a list, use the clear button below, or clear your browser’s site data. Lists stay on this device. |
| Recipe draft and return destination | Session storage preserves an unsaved recipe draft for up to 24 hours and a sign-in destination for one hour. Existing-account drafts are bound to that account. | Saving removes the draft. Closing the tab removes session storage. |
| Privacy choice | Local storage remembers analytics consent for 90 days. | Change it at any time using Privacy choices. |
| Optional analytics | Cloudflare Web Analytics uses a cookie-free script on public recipe pages after you allow it. | Necessary only blocks it. Account and email-link pages do not load it. |
Essential storage supports the service you request. Optional analytics is off by default, and rejecting it does not limit cooking or account features. This beta has no advertising or marketing trackers. Future tracking changes will require updated information and appropriate choices.
Control this browser
Who processes information
Supabase provides authentication, the database and uploaded image storage; the project database is hosted in Frankfurt. Cloudflare hosts and protects the app, records operational logs and provides optional public-page analytics. Resend delivers account confirmation and recovery emails. These providers may process information internationally under their data-protection arrangements. External stock photographs load from Unsplash, which receives the requests needed to deliver them.
Optional analytics counts consented public-page visits through an isolated frame. It cannot read the parent page’s account URLs or browser storage. Technical fault reports remove emails, URL query strings and authentication tokens; they do not include recipe form bodies. Necessary hosting/security logs still operate when analytics is disabled.
Retention and your requests
Account information and your saved content remain while your account is active or until deletion is requested. Recipe write-limit events are removed after 30 days during subsequent account activity. Provider logs and backup copies follow their configured retention policies. Browser meal data remains on the device until cleared.
During this invited beta, the Adaptive Recipes operator can be reached through the person who sent your testing invitation. Use that contact to request access, correction, export or deletion of your account data, or to object to processing. Include the account email so ownership can be verified; never send a password or recovery link. You may also raise a concern with the Information Commissioner’s Office.