Crumb Privacy Policy
Last updated 1 November 2026
The short version: Crumb stores the recipes, plans, lists and kitchen notes you and your household create so they stay in sync across your devices. We don't sell your data, we don't show ads, and we don't build profiles of you. You can export your own data or delete your account at any time.
1 · Who this covers
This policy covers anyone who uses the Crumb app or website. Because Crumb is shared within a household, it also explains what happens to information about other people you add: household members who don't use the app, and guests.
2 · What we collect
| Information | What it is | Why |
|---|---|---|
| Account | Name and email from Sign in with Apple (if you use Apple's "Hide My Email", we receive a relay address only), an account ID, and the date you joined. If you tick "Send me occasional Crumb news and offers by email", we record that you agreed and when. If you sign in with Apple, we keep a token Apple issues so that, when you delete your account, we can ask Apple to revoke Crumb's access. | To sign you in and keep your household's data attached to you. We email news only if you opted in, and you can opt out at any time. |
| Household | Household name; names and diet preferences of members (including members who don't use Crumb) and guests; invite links you generate. | To plan meals for the right people and scale recipes correctly. |
| Your content | Recipes you save or import (including the source web address), photos you add, meal plans, shopping lists, pantry and made-ahead items, ratings, "make again" answers, cook logs and notes. | This is the product. It's stored so it syncs across your household's devices. |
| Dietary information | Diet preferences you set per person (e.g. vegetarian, vegan, gluten-free, dairy-free, nut-free, custom needs). | To filter and convert recipes. See section 4; this can be health information. |
| Usage stats | Events like "recipe added", "meal cooked", "guest night", used to build your monthly stats and yearly Crumb Trail. | Shown only to your household. Not used for advertising. |
| Subscription | Whether your household is on the free tier, a trial, a paid plan or a complimentary plan, and your Apple transaction ID. We never see your card details. Apple handles payment. | To unlock the right features. |
| Feedback | If you send feedback from the app: your message, your account ID if you're signed in, and, if you give one, a reply email address, which we keep only to answer you. | To answer you and fix problems. |
| Device & diagnostics | Only when you send feedback with "Include diagnostics" left on: app version, device model, OS version, your household ID and a short sync log with personal content removed. | To fix bugs you report. |
What we don't collect: your location, contacts, health-app data, browsing history, or anything from other apps. We don't use advertising identifiers or tracking SDKs.
3 · How recipe import works
When you save a recipe from a web address, Crumb fetches the page on your device and extracts the recipe from the structured data most recipe sites publish. When you photograph a recipe, the text is read on your device using Apple's built-in text recognition. In both cases the recipe content stays on your device and in your household's synced library; nothing is sent to a third-party service. If a page can't be read this way and you've connected an AI app (section 8), Crumb can open that app with the page's address so it can save the recipe for you. The address goes to that AI app's company when you send the message.
Scanning a shelf or label reads the text on your device using Apple's built-in text recognition. The photo isn't uploaded.
4 · Dietary information (sensitive information)
Under Australian privacy law, information about a person's diet can be health information, which is "sensitive information". We only collect it when you choose to enter it, and only use it to filter, tag and convert recipes for your household. By entering a diet preference for yourself or someone in your household, you consent to us storing it for that purpose, and to the sharing described here. You can remove it at any time in Settings → Diets. We never share or analyse it beyond your household, except with an AI app someone in your household connects: only after they connect it, only while that connection is in place, and only for people whose Share with connected AI switch is on. The switch is on unless the person turns it off (section 8).
5 · People you add who don't use Crumb
You can add household members and guests by first name so meals can be planned for them. When you do, you're responsible for having a reasonable basis to add them. For family and regular guests that's simply that you cook for them. We store only what you enter: a first name, and optionally their diets, foods they won't eat and a note, plus which meals they joined. On its own that isn't enough for us to identify who the person is, so we can't act on removal requests from them directly. If someone asks you to remove their details, you should delete them in Settings → Household.
6 · Sharing within your household
Crumb is shared by design. Everyone in your household sees the same recipe library, meal plan, shopping lists and kitchen. Each recipe shows who added it. Household owners can remove members; members can leave. When you leave, you can take a copy of the recipes you added, all the household's recipes, or none, and the household keeps its copy.
A recipe file you send contains the recipe, its photo and the name you use in your household. It goes wherever you send it.
When you send a recipe as a link, we keep a copy of the recipe, its photo and the name you use in your household on our server for 30 days, so the person you send it to can open it. Anyone with the link can open it in Crumb during that time. Links are deleted after 30 days, or when you delete your account.
7 · Who else sees your data
- Apple: sign-in and payments, under Apple's own privacy policy.
- Hosting: your data is stored with Supabase in Sydney, Australia, encrypted in transit and at rest.
- Cloudflare: hosts this website and passes connected AI apps' requests to our server (section 8).
- Feedback email: feedback you send is stored with Supabase and forwarded to us by email through Resend.
- Crash reporting: none. Crumb has no crash-reporting SDK. Apple shares anonymised crash logs with us only if you have opted in to share analytics with developers in iOS Settings.
- Open Food Facts: When you scan a barcode, Crumb sends only the barcode number from your device to Open Food Facts (openfoodfacts.org) to look up the product. Nothing that identifies you is sent with it, though, like any website, they can see your device's IP address. Their privacy policy applies.
We don't sell personal information, and we don't share it for advertising. Apart from the services above and any AI app someone in your household connects (section 8), we'd only disclose it if the law required us to.
8 · Connected AI
On the Household plan, anyone in your household can connect their own AI app, such as Claude or ChatGPT, to Crumb. Once connected, it can read your household's Kitchen, recipes and their photos, meal plan, shopping lists, all notes, and who's eating, with the diets and foods they won't eat for each person who shares them. It can also add to your shopping lists, meal plan, recipes and Kitchen, add a photo to a recipe that doesn't have one, swap list items nobody has changed, update Kitchen amounts, dismiss freezer reminders on the meal plan, and remove items from your meal plan, Kitchen and shopping lists after checking with you in the chat. It never deletes a recipe, and you can undo what it adds from Crumb.
What the AI app reads is sent to the company that runs it (Anthropic for Claude, OpenAI for ChatGPT). It's sent under the connecting person's own account with that company, and that company's privacy policy and terms apply. That company may store and use it outside Australia, including in the United States. Whether it keeps your chats or uses them to improve its models depends on your settings with that company. Because the connecting person chooses to send it under their own account, Crumb isn't responsible for how that company handles it once it's sent. Once it's sent, Crumb can't recall it.
When the AI app gives Crumb a link to a photo for a recipe, Crumb asks you first. If you choose Add photo, our server downloads it from that link, resizes it, removes details stored in the file such as where it was taken, and saves it as the recipe's photo. The site the link points to sees a request from our server, not from you or your device.
Everyone in the household can see which AI apps are connected in Settings → Household → Connected AI. Each person chooses whether their diets and foods they won't eat are shared, with the Share with connected AI switch on their profile. For people without an account, the household owner sets it on their row in Settings → Your household. When it's off, a connected AI isn't sent anything about them, not even their name: it only learns how many other people are eating. Crumb still checks what it adds against their diets.
We never send profile photos, your Apple ID or email address, or your shopping history.
To stop sharing, disconnect in Settings → Household → Connected AI or in the AI app's own settings. Access stops straight away.
If an AI app Crumb doesn't support yet tries to connect, we note which app it was, so we know what to add next. We keep that note for 12 months.
What each AI tool sends and receives
A connected AI app works through the tools below. "Sends" is what the AI app gives Crumb when it uses a tool; "receives" is what Crumb gives back to it. Every tool only reaches the connecting person's own household, and never a private shopping list they aren't on. People whose Share with connected AI switch is off are never named in what it receives.
| Tool | The AI app sends | The AI app receives |
|---|---|---|
| get_household_context | How many days of the plan to read. | The people and saved guests who share, with their diets and foods they won't eat, and how many others don't share; the enabled meals; the meal plan with who's eating, day notes and freezer reminders; the Kitchen with amounts, levels and use-by dates; and the open shopping lists. |
| search_recipes | Search words, and optionally time, rating, when last made, a date and meal, and how many results. | Recipe summaries: title, cuisine, time, rating, when last made, and whether it suits everyone eating. |
| get_recipe | Recipe IDs, and optionally a date and meal. | Each recipe in full: ingredients, steps, the household's notes on it, its photo, and whether it suits everyone eating. |
| save_recipe | A new recipe: title, ingredients, steps, and optionally servings, time, cuisine, description, the web address it came from and a link to a photo. | Whether it was saved, or already saved under that title. |
| save_recipe_version | A recipe ID, a diet, ingredient swaps, and optionally a link to a photo. | Whether the version was saved. |
| add_to_plan | Dates, meals and recipe IDs, and optionally servings, who's eating and new guests' first names. | Which meals were filled and which were already taken. |
| remove_from_plan | The dishes to take off the plan. | Which dishes were removed. |
| add_to_shopping_list | Item names, amounts and units, and optionally a list. | Which items were added or merged, and on which list. |
| remove_from_shopping_list | The list lines to remove. | Which lines were removed. |
| replace_list_item | A list line, and the item, amount and unit to put in its place. | Whether the line was swapped. |
| create_event_list | A name for the new list. | The new list. |
| add_to_kitchen | Item names, amounts and units, and whether each is unsure. | Which items were added, and which were already there. |
| update_kitchen | Kitchen items with a new amount, or marked low, out or bought. | Which items changed. |
| remove_from_kitchen | The Kitchen items to remove. | Which items were removed. |
| dismiss_freezer_reminders | The planned dishes whose freezer reminder to dismiss. | Which reminders were dismissed. |
Any tool that changes something can first be run as a preview, which changes nothing and says what would change.
Why we use it
Only to answer the connecting person's requests: to read the household's data for the AI app and to make the changes it asks for. We don't use it for advertising, we don't sell it, and we don't use it to train AI models.
Who handles it
- Anthropic or OpenAI: receives what the tools return, as described above, under the connecting person's own account.
- Cloudflare: passes the AI app's requests to crumb-app.com/mcp on to our server. It also hosts this website.
- Supabase: runs our server and stores your household's data in Sydney, Australia. The server that answers an AI app's request may run outside Australia.
What we keep, and for how long
- What the AI app adds or changes becomes part of your household's data, kept as section 9 describes, and you can undo it in Crumb.
- The connection: which AI app, who connected it, and when it was connected, last used and disconnected. We keep this until the person's account or the household is deleted.
- Sign-in for the AI app: disconnecting ends it and removes its sign-in sessions.
- A faster copy for reading: a prepared copy of the household's people, plan, Kitchen and lists, so the AI app's reads are quick. It's deleted after 30 days without use, or when the household is deleted.
- Usage counts: how many requests each connection makes, with no content, used to apply limits. Deleted after 2 days.
- A photo link waiting for you: kept until you add the photo, the recipe gets a photo or is deleted, the connection ends, or the person who connected leaves the household.
- Logs: we don't write what an AI app sends or receives to our logs. Our hosting providers keep standard request logs, such as the time and the result of each request, for a short period under their own policies.
Your controls: disconnect an AI app at any time (above), turn Share with connected AI off for anyone, undo in Crumb what an AI app adds, export your data, or delete your account (section 10), which ends your connections straight away.
9 · Storage, offline use and retention
Crumb works offline. Your household's data is kept on each member's device and synced to our servers when you're online, so changes made by different people merge without losing anyone's work. We keep your data while you have an account. If your subscription lapses, nothing is deleted. You keep access to your 50 most recently added or cooked recipes and the rest unlock when you resubscribe.
10 · Your rights and controls
- See and correct: everything you've entered is visible and editable in the app.
- Export: Settings → You → Export my data generates a file of your own data that you can save or share: profile, diets, won't-eat, preferences, favourites, cook history and stats, for every household you belong to. (Recipes are referenced by title; we don't provide bulk recipe export.)
- Delete: Settings → Delete account (at the foot). Your account is deleted straight away and can't be restored by signing back in. Your personal information is removed from our live systems within minutes and from our backups within 30 days. Recipes you added remain with your household (attributed to a removed member) unless you delete them first.
- Notifications: turn each kind off in Settings → Notifications, or in iOS Settings.
- Complain: email privacy@crumb-app.com. We'll respond within 30 days. If you're not satisfied you can contact the Office of the Australian Information Commissioner (oaic.gov.au). If you're in the UK or EU you also have rights under GDPR, including access, erasure and portability, which the controls above provide.
11 · Children
Crumb accounts are for people 13 and over. Adults may add children to a household by name so meals can be planned for them; we hold only what the adult enters. We don't knowingly collect information directly from children under 13.
12 · Changes
If we change this policy in a way that matters, we'll tell you in the app before it takes effect. The current version always lives at crumb-app.com/privacy.
13 · Contact
Kitty Parke (ABN 16 541 656 304) · privacy@crumb-app.com