Privacy

Mise is built and run by Claudia and Simon. We are the people who decide what data the app holds, so we’re the ones to ask about it.

The legal entity name, registered address and governing country are still to be confirmed. Until then, reach us through the contact page.

Everything below lives in our own database, keyed to your account.

• Your account. The user ID our sign-in provider gives us, your plan and trial end date, your subscription status, your time zone, and — if we’ve ever had to set your account to read-only or pause it — that state and a short internal note.
• Your household. For each person you add: their name, age band, sex if you give it, portion size, diet, dislikes, allergies, which meals they eat on weekdays and weekends, and an optional nutrition mode such as lactation or weight loss.
• Your planning. Planned meals and weekly sides, your shortlist for the week, per-meal headcount changes, shopping ticks and any items you add by hand, meal ratings for each person, favourites, your private edits to library recipes, any recipes you write, and your settings — swaps, vacation weeks, weekly budget, price region, organic preference.
• Support messages. Anything you send us from the support screen, and our replies.
• Payment status — not payment details. Your card never touches Mise. Stripe collects and holds it. We store only the Stripe customer ID, your subscription status, and the IDs of the Stripe events we’ve already processed so we don’t apply one twice.

Your email address, name and password (or social login) live with Clerk, our sign-in provider — not in our database. We read your verified email and first name from Clerk while a page is loading, to match household invitations and to say hello. The one place we do store an email is a household invitation: when you invite someone, we keep the address you typed until the invite is accepted or removed.

We only send email that is about your account: a welcome when you sign up, a reminder a few days before a free trial ends, a notice if a payment fails, a note when we reply to your support message, and — when you invite someone into your household — one invitation to the address you typed, naming you by first name. No newsletters, no marketing, and we never share addresses for anyone else’s mailing list.

Your time zone is captured once from your browser on first load, so “today” means your today rather than the server’s. You can change it in settings, and we never overwrite your choice.

This deserves its own paragraph. Mise asks for each household member’s age band and their allergies, and it lets you record a nutrition mode such as lactation or weight loss. For families that means the app holds details about children, and details that are health-related.

We treat that as the most sensitive data in the product. We ask for it for one reason: to size portions, to keep allergens out of your week, and to make the nutrition figures mean something. It is never sold, never used for advertising, and never shared with the grocery partners below. You can delete any household member at any time, which removes their details along with their meal ratings.

Mise is meant for the adult running a household, not for children to use themselves. If you’d rather not record a child’s name, use an initial or a nickname — nothing in the app needs their real one.

To run the thing you asked for: build your week, scale recipes to the people eating, work out the shopping list, estimate nutrition and cost, remember what your household liked, and keep your subscription and trial straight. We also read support threads so we can answer them.

We don’t profile you, we don’t run ads, and there is no analytics, session-recording or advertising script in the app.

• Clerk — sign-in and account management. Holds your email, name and credentials.
• Stripe — subscriptions and payment. Receives your email address when you start checkout, and collects your card details directly. We never see the card.
• Resend — sends our emails. Receives the recipient’s email address and the message, and nothing else from your account.
• Our database and hosting providers — a managed Postgres database and the platform the app runs on. They store the data above on our behalf; the connection to the database is encrypted.
• People you invite into your household — see below.
• Us. We can see account records and support threads through an operator console. We look when we need to help you or fix something, not to browse.
• Grocery partners — only if you tap the button, and only the list. See below.

When you invite someone into your household and they accept, they work inside your data — the same plan, shopping list, household members, favourites, ratings and settings. That includes children’s ages and allergies. Treat an invitation as full access, and only send one to someone you’d hand the whole plan to.

Billing and invitations stay with the household owner. Support conversations are not shared — yours are yours. You can remove a collaborator, or leave a household you joined, at any time.

Mise can hand your shopping list to a grocery service so you can order it. This only happens when you press the button, and only the items still unticked are sent — no name, no email, no household details.

• Instacart receives the item names and amounts, plus a link back to your shopping page, and returns a list page where you pick a store and check out.
• Walmart receives each item name as a product search, and we assemble the matched products into a cart link. That link carries our affiliate ID, so we may earn a commission if you buy.

Both integrations are switched off unless we’ve configured keys for them, and as things stand neither is live — if you don’t see the button, nothing has been sent anywhere. Once you land on a partner’s site, their privacy policy applies to what happens next.

We don’t use tracking or advertising cookies. The cookie Mise does set is the session cookie from our sign-in provider — it’s what keeps you signed in, and the app doesn’t work without it.

Your browser also keeps a couple of small things locally, on your device, that we never receive: which steps you’ve ticked off while cooking, and your light/dark theme choice.

Installed as an app, Mise registers a service worker. It caches only the offline page and static files like icons and fonts — never your pages, your plan or any response containing your data.

We keep your data for as long as your account exists, because it is the account — your plan history is what makes next week’s suggestions any good. Support threads stay until they’re deleted with the account.

Deleting your sign-in account with Clerk does not, today, automatically erase the data in Mise. Ask us and we’ll delete it — see the next section.

• See it. Almost everything we hold is already on screen — your household, plan, shopping list, settings and support thread. Ask us for anything that isn’t.
• Correct it. Edit household members, plans and settings in the app whenever you like. Your email and name are edited through your sign-in account.
• Delete it. We have a real deletion path, not a promise: one action removes your account record, household members, planned meals, the sides you added to each week, shortlists, shopping ticks and manual items, meal overrides, ratings, favourites, recipe edits, recipes you wrote yourself, settings, household invitations, and your support thread. Ask us and we’ll run it. It cannot be undone.
• Take it with you. Ask and we’ll export your household, plans and recipes.
• Object or complain. Write to us first — we’d rather fix it. You can also complain to your local data protection authority.

Recipes from the shared Mise library aren’t yours to delete, since they belong to everyone using the app. Everything you created or entered is.

The app is served over HTTPS and talks to its database over an encrypted connection. Sign-in and passwords are handled by Clerk, not by us. Every query is scoped to your household, and payment webhooks are signature-verified before they’re believed. No small team can promise perfect security, but we can promise we won’t hold data we don’t need.

Your data is stored in a managed Postgres database in the United States (AWS us-east-1, Northern Virginia).

Where the app itself runs, and the terms that cover transfers for people outside the US, are still to be confirmed.

If we change what we collect or who we share it with, we’ll update this page and change the date at the top. For anything significant we’ll tell you in the app rather than leaving you to notice.

Questions, corrections, exports and deletions all go to the same place: our contact page. If you’re signed in, the support screen reaches us directly.