Mise
Privacy
Last updated 21 September 2026
A starting point, not legal advice
This page was drafted from what the app actually stores and who it actually talks to. It hasn’t been reviewed by a lawyer yet and isn’t legal advice, and anything we haven’t settled is marked as still to be confirmed.
Mise is a meal planner for households. To do that it has to hold some personal things — who eats at your table, what they can’t eat, what you cooked last week. This page says exactly what we keep, why, and who else ever sees it. We don’t sell it, and there are no advertising or analytics trackers in the app.
Who is responsible
Mise is built and run by Claudia and Simon through Leah & Felix LLC, 601 Harrison Street, Apt 422W, Hoboken, NJ 07030. In data-protection terms, Leah & Felix LLC is the “controller”: we decide what the app holds and why, so we’re the ones to ask about it.
We’re based in the United States. Where a data-protection law such as the EU or UK GDPR applies to how we handle your data, you have the rights it gives you, and we’ll honour them. Reach us through the contact page.
What we store
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. We can also set switches on your account by hand, to give you something your plan wouldn’t normally include. Only we see them, and they’re ours rather than yours, so they aren’t in your download — ask and we’ll tell you what yours say.
- Your household. For each person you add: their name, age band, sex if you give it, portion size, diet, dislikes, allergies, ingredients they never eat, which meals they eat on weekdays and weekends, and an optional nutrition mode such as lactation or weight loss. Also optional: the nutrients you’ve asked us to watch for them, and the ones they take a supplement for — the nutrient only, never a dose, brand or product.
- Your planning. Planned meals and weekly sides, your shortlist for the week, per-meal headcount changes, who’s out or fending for themselves at a meal and any note you add to it, shopping ticks and any items you add by hand, meal ratings for each person, favourites, your household’s versions of 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 — and, if you sign in with Google, your name and the Google account you use — live with Clerk, our sign-in provider, not in our database. There’s no password: you sign in with a code we email you, or with Google. We read your verified email, and your first name if there is one, 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 they leave the household or the invite is 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.
Children, allergies and health
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 leave the allergies you’ve listed out of the dishes Mise plans for that person, 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.
Supplement use is health data too. Recording it is optional, and nothing in the app asks for it. If you do, we store which nutrient someone takes a supplement for (say, vitamin B12) and nothing else: no dose, brand, product, how often, or test result. Nutrients you ask us to watch for someone are stored the same way. We use them only to pin those nutrients on that person’s nutrition rows and to stop flagging a nutrient they take a supplement for. Everyone in your household can see and change them. When our support staff open your account in the operator console to help you, the console loads your household’s records, these among them. Removing that person, or deleting your account, deletes them.
Mise is for the adult running a household. You need to be 18 or over to open an account or to accept an invitation into someone’s household, and Mise isn’t directed at children. If we learn that someone under 18 has opened an account, we’ll close it and delete its data.
The details about children in Mise are entered by their parent or carer, about their own family, and are handled exactly as this page describes. If you’d rather not record a child’s name, use an initial or a nickname — nothing in the app needs their real one.
Why we store it
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.
Who else sees it
- Clerk — sign-in and account management. Holds your email address, the cookies that keep you signed in and, if you sign in with Google, your name and the Google account you use. When you sign up, Clerk runs a bot check in your browser, provided by Cloudflare.
- Stripe — subscriptions and payment. Receives your email address and your Mise user ID 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, which may include your first name.
- Neon and Vercel — Neon runs our Postgres database and Vercel runs the app. They store and process the data above on our behalf; the connection to the database is encrypted.
- Open Food Facts — when you search for a shop-bought product, or add one, our server asks the Open Food Facts database for it: the words you typed, or the product’s barcode. Nothing else goes with them — no name, email or account ID.
- 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.
Clerk, Stripe, Resend, Neon and Vercel are our sub-processors: they handle personal data on our behalf, only to provide their service, under a data processing agreement with us.
- Clerk — [REGION] — data processing agreement — [DPA LINK]
- Stripe — [REGION] — data processing agreement — [DPA LINK]
- Resend — [REGION] — data processing agreement — [DPA LINK]
- Neon — United States (AWS us-east-1) — data processing agreement — [DPA LINK]
- Vercel — [VERCEL FUNCTION REGION] — data processing agreement — [DPA LINK]
Signing in with Google is your choice, and Google handles that sign-in under its own privacy policy.
Sharing a household
When you invite someone into your household and they accept, they work inside your data — the same plan, shopping list, household members, favourites, ratings, your versions of library recipes 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.
Grocery partners
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.
Cookies and local storage
We don’t use tracking or advertising cookies. The only cookies Mise sets are the ones our sign-in provider uses to keep you signed in — the app doesn’t work without them.
Your browser also keeps a few small things locally, on your device, that we never receive: which steps you’ve ticked off while cooking, any cooking timers you’ve started (so a reload doesn’t lose them), the undo for a week you’ve just copied (for an hour, in that tab), 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.
How long we keep it
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.
When you remove an invitation, or a collaborator, the email address in it is erased straight away. If someone declines your invitation, it’s deleted.
Deleting your data removes it from our live database at once. Our database host keeps [NEON RESTORE WINDOW], so a deleted record can stay in a backup until that backup expires. Backups are used only to recover from a failure. If we ever restore one, we’ll delete again anything you’d already asked us to remove.
Some records live with our providers rather than with us. Stripe keeps your customer record and its record of your payments under its own rules. Deleting your data in Mise doesn’t close your sign-in account with Clerk — tell us if you want that closed too and we’ll do it. Sent emails stay in Resend’s logs for [RESEND LOG RETENTION].
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.
Your rights
- 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. To change your email address or name, ask us and we’ll do it.
- 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. Download everything in your household — who’s eating, every week you’ve planned, shopping lists and ticks, meal notes, ratings, favourites, settings, the recipes you wrote and your own versions of ours, and your conversation with us — as one file, any time, from your data. It works even if your subscription has lapsed. Recipes from the shared library are linked rather than copied, and the file itself says what isn’t in it and where that lives.
- 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.
Keeping it safe
The app is served over HTTPS and talks to its database over an encrypted connection. Sign-in is handled by Clerk, not by us, and there are no passwords to leak: you sign in with an emailed code or with Google. 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.
Where your data is handled
Your data is stored in a managed Postgres database in the United States (AWS us-east-1, Northern Virginia).
The app itself runs on Vercel in [VERCEL FUNCTION REGION]. If you use Mise from outside the United States, your data is transferred to and handled in the US.
Where the law asks for a safeguard for that transfer, we rely on the Standard Contractual Clauses in our providers’ data processing agreements (with the UK’s equivalent), and on the EU–US Data Privacy Framework where a provider is certified under it.
Changes
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 email you rather than leaving you to notice.
Getting in touch
Exports are a download — take your data with you. Questions, corrections and deletions all go to the same place: our contact page. If you’re signed in, the support screen reaches us directly.