Privacy

Meal Prep Roulette works with no account at all. In that mode everything — your menu, your grocery list, what you've liked, your filters, your theme — is kept in your browser's local storage on that device. It is never sent anywhere, and clearing your browser data removes it permanently.

Local storage here holds the app itself, not tracking. There are no advertising or analytics cookies, so there is no cookie banner. The one cookie-like thing the site sets is the sign-in token described below, which exists only to keep you signed in.

Accounts are handled by Supabase, which stores your email address and, if you signed in with Google, the basic profile Google returns. Signing in also stores your app data — menus, cooking history, your own recipes, grocery lists — so it reaches your other devices.

You can sign in with a password, a magic link, or Google. Passwords are handled entirely by Supabase and never reach this app.

When you press ✨ Surprise me, the filters for that one recipe — the meal type, the skill level, any diet or sensitivity settings, and the names of recipes you already have so it doesn't repeat one — are sent to Anthropic, which writes the recipe. No account details, email address or menu history goes with it.

The app also records that a generation happened, and what it cost, against your account. That exists so spending can be seen at all; it is not shared with anyone.

When you share a grocery list or a week of meals, the app creates a row holding just that content and gives you a link containing a random identifier. Anyone with the link can open it — that is what makes it shareable without the other person needing an account — so treat it like a key. Shared rows expire after about 30 days, and you can stop sharing at any time.

Sharing one of your own recipes is similar, with three differences worth knowing. The row holds the recipe and nothing about who shared it — not your account, not your email — so it cannot be traced back to you by us or by anyone who opens it. It lasts 90 days from the last time somebody opens the link, so a recipe people keep coming back to stays alive while a forgotten one is deleted. And because the row does not know it is yours, a recipe link cannot be withdrawn — there is no “stop sharing” for one, and the 90 days start again each time it is opened. Send one only to people you would be happy to keep having it.

Recipe links sent before this changed carry the whole recipe inside the link itself, which never reaches a server at all. Those keep working exactly as they did.

• Vercel — hosts the site and serves the pages you are reading.
• Supabase — accounts, sign-in, and the stored data described above.
• Anthropic — writes ✨ recipes, from the filters described above.
• Google — only if you choose “Continue with Google” to sign in.

Each of these keeps its own operational logs (a web server records requests, for instance). Nobody is paid to receive your data, and none of it is sold, rented, or used for advertising.

Account data is kept while your account exists. Shared list and menu rows expire on their own after about 30 days.

You can remove your data yourself, at any time, without asking anyone:

• Sign out (☰ menu) clears the account's data from that device.
• ♻️ Reset current account data (☰ menu) deletes the stored data for your account on the server and wipes it from the device.
• Clearing your browser's site data removes everything kept locally.

Depending on where you live, you may have rights to see, correct, export or delete personal data held about you — under laws such as the Texas Data Privacy and Security Act, the California Consumer Privacy Act, or the GDPR if you are in the UK or EU. The self-service controls above are designed so you can exercise the important ones immediately rather than by request.

The app does not sell personal information or share it for cross-context behavioural advertising, and it makes no automated decisions about you.

Meal Prep Roulette is not intended for children under 13, and accounts should not be created by them.

Use 📬 Feedback to the chef — it reaches a real person, and you can leave an email address or not.

For anything about your own data, the controls under Keeping it, and getting rid of it are faster than asking: they act immediately and need nobody's permission.

The form records which page you sent it from and which build was running, so a bug report is fixable rather than a guessing game. It says so on the form itself.

If this page changes, the date at the top changes with it. There is no mailing list to announce it to — which is rather the point.