WhatsForDinnerEspañol

Privacy policy

Last updated: August 28, 2026

The short version

WhatsForDinner has no accounts and no cloud of ours. Your meal plan lives in a local database on your phone. If you share it with your household, it syncs through your own iCloud — never through a server of ours. We cannot read it, and neither can anyone else.

What stays on your device

Meal slots, dishes, ingredients and supplies, plan entries, pantry items, and preferences — all of it is stored in a local SQLite database on your device. There is no server of ours that holds a copy of your plan. You can export a copy yourself at any time — it goes wherever you send it, and never to us.

What leaves your device

Three things, and only three:

What we do not collect

No analytics profiles. No advertising SDKs. No food-database queries — the app has no food database. Meal and shopping reminders are scheduled locally on your device and never touch a server.

This website

sowhatsfordinner.app runs the Google tag so we can tell which ads bring people here. It sets a first-party cookie (_gcl_au) that records the ad click, and reports page views and App Store clicks to Google Ads.

It also runs Vercel Web Analytics and Speed Insights, which count page views and measure how fast pages load and respond. Neither sets a cookie, and neither follows you to other sites — they report totals for the page, not a profile of you.

That is all the site measures — it has no account, no login, and nothing about you to attach a visit to. Blocking cookies or scripts for this site costs you nothing: every page works the same either way.

No other trackers, and no analytics profiles.

Contact

Questions about this policy: support@sowhatsfordinner.app.