Recipes in, shopping lists out. Open the app
You paste a recipe link. MarketMeal reads the ingredients and method off the page, and turns any number of recipes into one shopping list, merged and grouped by aisle. Two phones can share a list and see each other's changes as they happen.
Your recipes and lists never reach our servers. There is no account, no email address and no password. Everything lives in your phone's own storage. If you turn on sharing, it also lives in a private household database that only the phones holding your join code can read — not us.
When you paste a link, our server fetches that page, reads the recipe out of it, and sends it back. It keeps no copy of either the page or the recipe.
The one thing we do count is page views, through Vercel Web Analytics. It is served from this domain rather than a third party, sets no cookie, and builds no profile — it tells us how many visits there were, not who made them. It exists so we can tell whether anyone is still using this, which is otherwise unknowable. That is the entire extent of it.
MarketMeal fetches pages one at a time, only when a person pastes that specific link, and only the structured recipe data sites already publish for search engines. It identifies itself:
MarketMealBot/1.0 (+https://marketmeal.app/about)
It reads and obeys robots.txt before every fetch. If you would rather it left your
site alone, this is all it takes:
User-agent: MarketMealBot Disallow: /
MarketMeal will stop on its next fetch, and tell the person to paste the text instead. You do not need to contact anyone, wait for a reply, or be believed — it is immediate and it is yours to decide. Every recipe MarketMeal shows also credits and links back to where it came from.
MarketMeal is a personal project and there is no monitored address yet. Rather than print one that goes nowhere, here is what works today:
robots.txt lines above.
Immediate, self-service, and it needs nothing from us.