Privacy policy

1. What we collect

Very little, and only when you hand it to us.

• Nothing for pre-order. The Pre-order now button sends you to the App Store or Google Play. The pre-order happens there, under that store's privacy policy. This site takes no email address, no account and no payment for it. We see only the anonymous analytics event that the button was used.
• Shared weeks. When you share a week from the app, the card and its numbers, the meals, the list, the estimated totals, are published at a link on this site. Nothing about you travels with it: no name, no email, no device identifier. The shared pages on this site today are fixtures.
• Support messages: your name if you give it, your email, and what you wrote.
• Cookieless analytics. We use Vercel Web Analytics, which counts page views and a handful of named events (like "pre-order opened") without cookies, without fingerprinting, and without a persistent identifier for you. It records a hashed, rotating visitor id, your country, device type, and referrer. It can't follow you across sites.

We don't ask for your name, your address, your payment details, or your health information anywhere on this site. Please don't put health information in the support form.

2. Purchases

If you subscribe, Apple processes the payment. We use RevenueCat to check your subscription status. RevenueCat receives an anonymous identifier the app generates, your purchase and renewal history, and basic device details such as iOS version. It does not receive your name, email or payment details. RevenueCat's privacy policy is at revenuecat.com/privacy. You can restore purchases on any device signed in to the same Apple ID.

3. What we don't do

Plainly:

• We set no cookies of our own. None. So there's no cookie banner, because there's nothing to consent to.
• We run no advertising trackers, pixels, or third-party scripts that profile you.
• We do not sell your data. We do not share it for advertising. Not now, not at launch, not as the business model, ever.
• We send no marketing email. The site collects no email address for that purpose.

4. Where it lives

Support messages (and the entries from the retired early-access waitlist, see below) are stored in a Supabase (Postgres) database hosted in the United States. The website runs on Vercel, which also provides the analytics. Both are processors acting on our instructions; they don't get to use your data for their own purposes.

If you're outside the US, your data is transferred to and stored in the US when you submit it.

5. Why we use it

• To send you to the App Store or Google Play when you tap Pre-order now (the store handles the pre-order itself);
• To answer your support message;
• To see, in aggregate, which pages and steps work and which don't.

The legal basis, where one is required, is your consent (you typed it in and pressed the button) and our legitimate interest in running and improving a small site.

6. How long we keep it

Nothing from the pre-order flow is kept here; the store keeps your pre-order. The early-access waitlist that ran on this site before pre-order opened is closed: the entries it collected stay until the app has shipped or until you ask us to delete them, whichever comes first, and after launch we'll delete them (we email those addresses before we do).

Support messages are kept for up to 12 months so we can follow up, then deleted.

Analytics are aggregate and are retained by Vercel under their policy.

7. Your rights

You can ask us, at any time, to:

• Tell you everything we hold about you;
• Correct it;
• Delete all of it, including any entry from the retired waitlist;
• Send you a copy in a plain format.

Email support@wisedinner.com from the address in question. We confirm within 7 days and complete the request within 30. No forms, no account required. If you live somewhere with a data-protection regulator, you can also complain to them; we'd rather you told us first.

8. Under 16

The site isn't for people under 16 and we don't knowingly collect their data. If you think we have some, email us and we'll delete it.

9. Changes to this policy

If we change what we collect or why, we'll update this page with a new effective date, posted here at least 14 days before the change takes effect. Small wording fixes just get posted here.

Effective: September 24, 2026