It’s Dinnertime privacy policy
Effective September 30, 2026 · Updated November 17, 2026 · Made by Smart Home Life LLC.
The short version
Unless you plan with Claude through Pro or connect an AI assistant (Pro), or connected an oven for alerts earlier, we keep no record of who you are or what you do. (For Claude, we ask your permission first, on your phone, before anything is sent, and all we keep is a monthly count for each feature, described under AI planning.) The app has no accounts, no tracking, no analytics and no third-party SDKs. This website is separate from the app, and it counts page views, and clicks on Join beta, with Cloudflare Web Analytics and Umami. Neither uses cookies, and neither tracks individual visitors or collects personal data. Your recipes, plans, lists, photos, ratings, notes and past grocery orders live on your device and, if you use iCloud, in your own private iCloud storage that only you can read. The one exception is a week you share with your household: it is kept in the iCloud of whoever set the household up, and only the people in it can read it. We cannot. The one small thing that is not kept there is the notice that lets a member's phone be alerted when someone asks them to cook or to choose a different dinner: it carries no names, and the paragraph on asks below says exactly what it holds. Our own service remembers which stores are near a zip code, for a day, so the store finder stays fast: a fact about a place, never about you. To stay within Kroger's daily limit, our service briefly keeps Kroger's answers to product searches, keyed by store and search words and never by who searched, for at most 6 hours, along with one daily count of searches. If you connected a Samsung oven earlier so the app could alert you while it was closed, our service keeps that connection until it is deleted. "Oven Alerts" below lists every piece of it. If you connect ChatGPT, Claude or Gemini so it can read and change your recipes, week and grocery list, a separate server keeps an encrypted copy of just that until you disconnect; "Connected assistants" below lists every piece of it. A recipe or a dish drawing you share with other cooks is public and anonymous, as described under "Shared recipes and the sketch library".
What stays on your device or in your iCloud
Recipes you save, weeks you plan, your grocery list, dish photos you take, the pictures drawn for recipes without a photo, your ratings and notes, your settings, the original PDF of a recipe you brought in from a file, kept on this phone so you can open it again, and your past grocery orders. If you connect a store, what the app reads from your order history (items, prices, totals) is stored on your device and in your own iCloud, and never reaches us. If iCloud is on, Apple syncs these between your devices through your private iCloud database. We cannot read it: it belongs to your Apple Account, not to us.
Your grocery list is kept in Apple's Reminders, in a list you choose, so you can share it with your family the way you already share Reminders. That data is governed by your device and your Apple Account, not by us.
Sharing your week with your household (optional)
Add someone, in Settings, Your Household, Household, makes a one-time invitation link through Apple's iCloud. Each link lets exactly one person join. The household lives in the iCloud of the person who set it up, as a shared space Apple keeps for them. Nothing about it passes through our service, and we cannot read it.
Everyone in the household can see:
- The week that was planned. Each night's dish, its note, ingredients and steps, and how many servings; for a dinner from a recipe on the web, a link to that page and its photo; nutrition figures when there are any. A dinner planned from one of your saved recipes brings that recipe's ingredients and steps, never your photos of it.
- The name each person typed when they joined, if they typed one. The app never reads anyone's Apple Account name, email or phone number, and someone who typed nothing shows as "Someone". To tell people apart, the app uses an identifier Apple's iCloud gives it for each person's account, which cannot be turned into a name or an email.
- Who is cooking. If someone picks who is cooking a night, the household's shared copy of that night holds that person's household identifier, the same one described above, and the app shows it as their first name.
- A night's note and its side dishes. If someone adds a note to a night (up to 280 characters), the note text is kept with that night. For each side dish added to a night, the side's name, its ingredient lines, its steps and its source link, if it has one, are kept with that night too. Everyone in the household can read them, and the app shows them on that night's card. A side picked from your saved recipes is copied, so your saved recipe itself and its photo stay yours and are not shared.
- Asks to choose again. Ask to choose again saves a small request in the household's shared space for each other person in it: the identifier of the person asked, the weekday, who asked (a first name) and which version of that night it was asked about. It shows as a short line on that night until anyone changes the dinner.
- The nights someone said no to. Which night, who crossed it off and when, and which of those were settled with Keep it. A night is crossed off from Review the week.
- Invitation links nobody has used yet, and when each was made, so each can close after three days.
- Each person's colour, and their photo if they add one. A photo is small (under 64 KB), chosen with the system photo picker, which gives the app only the one photo you pick, so the app never asks for access to your photo library. It is saved on your phone and in your household's iCloud, and only the people in your household can see it. It is never sent to us. Remove your photo in Settings, Your Household, Household and it leaves the household's copy too. Someone who has left, or was removed, may keep a photo their phone had already downloaded.
Not shared: your saved recipes and their photos (except one you send to someone, below), what you have cooked, your ratings and notes, your settings, a week you have planned ahead, and your allergens and diet. Your grocery list is shared only if you share it in Reminders. The Recent Activity list in Settings, Your Household, Household is kept only on your phone: it is never sent to iCloud or to us, and your other devices keep their own.
Everything the household shares counts against the iCloud storage of the person who set it up, including what other people add to it. If you join someone else's household, the name you type, your photo and colour, the nights you cross off, who you pick to cook, and any note or side dish you add are stored in their iCloud, not yours.
If you are in a household, It’s Dinnertime can tell you when its week changes, or when someone crosses off a night, takes one back or keeps one, when someone asks you to cook a night, when someone asks to choose a night's dinner again, and, if you set the household up, when someone joins. These notes are sent by Apple's iCloud, from a request saved in your own iCloud account, through Apple's push notification service. Nothing about them passes through our service. Some of them name who did it, for example "Sam crossed off a dinner", using the first name that person typed when they joined. They name a weekday when it helps, but they never include a dish, a note, a side or a recipe. If you made an invitation link, It’s Dinnertime can also remind you, on your own phone, about 48 hours after you made it, that the link has not been used and closes tomorrow. That reminder is scheduled on your phone and never leaves it. Each kind of note has its own switch in Settings, Notifications and News, and the switches apply to every device signed in to your Apple Account.
Asks to a household member. When someone asks a household member to cook a night, or to choose a different dinner, and that member is not the person who set the household up, the app writes a small notice to the app's public iCloud database so that member's phone can be alerted. The notice holds two things: a scrambled code that stands for that member (a one-way hash, not their Apple Account, and it cannot be turned back into it) and the weekday. Its record name is scrambled too, and ends in a second scrambled code that stands for the person who asked, so the member’s own phone can show who it was. Neither code is a name or can be turned back into one. It holds no names, no recipes and no household details. Because it is a public database, anyone who has the app's iCloud container ID could read what is in it, which is why the notice carries nothing that identifies anyone. The phone that created the notice deletes it after seven days, the next time it syncs the household. If that phone has been erased or reset first, the notice can stay behind, still holding only a code and a weekday. The name of the person who asked is never stored in the public database: the alert on the member's phone is filled in on that phone, from household information it already has. The household's own iCloud holds a fuller copy, which only the people in the household can read: a request to cook is saved there only when the person asked is the one who set the household up, with the first name of whoever asked, and the phone that made it deletes it after seven days; a request to choose again is saved there for everyone asked, as described above, and stays until the household stops sharing. Neither the public notice nor the household copy passes through our service, and we do not receive either.
You can send one of your saved recipes to someone in your household, from its menu in Recipes. It goes into the household's shared space with its picture, addressed to them, and waits there until their phone copies it into their own recipes, which takes it out of the shared space again. While it waits, it counts against the storage of whoever set the household up, and like everything the household shares it can be read by the phones of the people in it. Your rating and notes on it are not sent. Once it is copied it is theirs: your later changes do not reach it, and they can change or delete their copy. Their copy is marked with the name you typed for the household.
Anyone can leave a household in Settings, Your Household, Household. The person who set it up can also remove someone, close a link nobody has used, or stop sharing, which ends the household for everyone. Removing someone deletes their name and the nights they crossed off from the household, and so does leaving, the next time the phone of whoever set it up syncs the household. Stopping sharing deletes everything the household shared from their iCloud, including every night's cook, note and side dishes and any open requests, and their own week stays on their phone. A night's cook, note and side dishes also go when that night is taken off the shared week, the next time the phone of whoever set it up shares the week. What a phone had already received may stay on that phone: one person's tap cannot reach into someone else's device.
Apple Health
Two optional connections, each off until you turn it on.
Sending your dinners. If you turn on "Send cooked dinners to Apple Health" in Settings, the app writes the nutrition figures for each dinner you finish to Apple Health on your device. Figures the app estimated are marked as estimates in Health. Nothing it writes is read back.
Seeing the rest of your day. If you tap "Connect Apple Health" on the week's totals, the app reads today's calories, protein, carbohydrates and fat that other apps have logged in Apple Health, and shows them beside your dinner. What it reads is displayed on your device and then forgotten: never stored, never synced to iCloud, never sent anywhere. It leaves out what this app itself wrote, so a dinner is never counted twice. You can turn sending off in the app's Settings, turn either connection off in iOS Settings (Privacy & Security, Health) or in the Health app, and manage or delete what was written in the Health app itself.
What leaves your device, and what it carries
- Fetching a recipe you asked for. When you paste or share a recipe link, the app fetches that page directly from that website, the same way a browser would. The website sees an ordinary page request from your device. Browsing the starter-recipe catalog goes through our own service instead, which passes the request along and keeps nothing; the starter recipes' photographs load from TheMealDB directly, like any picture on a web page.
- Shared recipes from a website. When you open a shared recipe that credits a website, your phone asks that website for its picture, the same way a browser would. The website sees an ordinary request from your device; we are not involved and keep nothing.
- Store prices (Pro). When you look up prices, the app asks our price service for a product search at your chosen store. The request carries the search words and the store, and for the store picker your zip code. It never carries your name, an account, or anything that identifies you. Our service keeps no record of who asked or what anybody searched; it keeps two things, neither about a person: a shared day-long note of which stores are near a zip code, so the store finder does not have to ask the catalog twice, and, to stay within Kroger's daily limit, Kroger's answers to product searches, keyed by store and search words and never by who searched, for at most 6 hours, along with one daily count of searches. Supabase, the company that runs our service, keeps short request logs of its own; because the search words and the zip code travel in the request's address, those logs can hold them, with the internet address the request came from, until they expire about a day later. Price data comes from the store's own public catalog service. A price lookup also carries your Pro purchase's signed receipt, which our service checks and does not keep. The store finder instead carries a proof that the request comes from a real copy of this app (Apple's App Attest), which says nothing about you and is not kept either.
- Walmart prices and cart (Pro). For a Walmart list, the app asks our price service for Walmart product data. The request carries the search words (for a barcode scan, the barcode digits; for products you already picked, their Walmart item numbers) and your chosen Walmart store, and for the Walmart store picker your zip code. It never carries your name, an account, or anything that identifies you, and you do not sign in to Walmart for it. Our service keeps no record of who asked or what anybody searched; it holds recent answers in memory for about fifteen minutes so a repeat search is not sent to Walmart twice, and they are not tied to anyone. Walmart's product service supplies the data, and a price lookup carries your Pro purchase's signed receipt, which our service checks and does not keep. Add all to cart builds a link on your phone and opens walmart.com, which then sees the products and store in that link along with what any visit to walmart.com shows. It’s Dinnertime cannot see your Walmart cart or what you buy there.
- Signing into a store's website (optional). If you connect a store (Kroger, Walmart, Whole Foods, Publix, Costco, or an Albertsons-family store), you sign into that store's own website in a secure web view on your device. Your sign-in belongs to that store; we never see or store your credentials, and their privacy policy governs what they do. With a store connected, the app can read prices and your own order history from the store's pages, on your device; what it reads stays on your devices and never reaches us. For Costco, the app reads only a receipt you open on Costco's own page, then fills in item names and pictures from Costco's product pages while the app is open; only the food lines are kept, on your devices and in your own iCloud. To keep you signed in, the app keeps the store's sign-in cookies in your device's Keychain for up to 30 days, on that device only, never in a backup, and removed when you disconnect the store.
- Scanning a barcode. When you scan a product, the app asks Open Food Facts, a nonprofit open food database, what that barcode is. The barcode digits are all that go; no account, no device, nothing about you, and nothing about anything else you have scanned. It comes back with a product name, which is what lets the app search your stores for the right thing. If the database does not know the barcode, the app says it could not confirm it rather than guessing.
- Sending items to your Kroger cart (Pro, optional). If you connect your Kroger account for the cart, Kroger's sign-in hands the app a connection code, and our service exchanges it with Kroger for the app. That is the one moment it passes through us; it is not logged or kept, and the resulting connection lives only in your device's Keychain.
- Connecting a Samsung oven (Pro, optional, paused for now). You sign in on Samsung's own page; we never see your Samsung password. Samsung asks you to let Dinnertime read the devices and locations (homes) you have in SmartThings. That access is read-only: the app can never turn anything on, change a temperature or start a cycle. Samsung's page hands the app a sign-in code, and our service swaps it with SmartThings for the connection's keys, because that swap needs a secret the app must not carry. The swap itself keeps nothing, and the app stores the keys in your device's Keychain. Your phone then looks through your SmartThings devices for ovens, on the phone. While you are looking at your oven in the app, your phone reads it straight from SmartThings about every 20 seconds, not through us.
- Oven Alerts (Pro, optional, paused for now). To reach you when the app is closed, our service keeps a small record of your oven connection and your phone, SmartThings sends it your oven's changes, and each alert travels to your phone through Apple's push notification service. This is the one feature where our service keeps something tied to you. "Oven Alerts" below lists all of it.
- Sharing a recipe with other cooks (optional). If you share a recipe with other cooks, the recipe itself (its name, ingredient lines, steps, yield, time, category, and your own photo of the dish if you added one) is posted to the app's public iCloud database, where anyone using the app can read it and save it. Nothing about you goes with it: no name, no email, no location, no notes, no ratings, and no link. Apple's iCloud notes which iCloud account posted it as an opaque identifier that we cannot turn into a person; we see that identifier only in Apple's developer console, and use it for nothing but removing a post. Reading shared recipes sends nothing. You can remove your own post at any time from its page, and we remove anything reported that is not a recipe. If you report a recipe, the report (which post, your reason, and any note you type) is written to the same public iCloud database so we can read it in Apple's developer console; write nothing personal in the note. Hiding a cook's recipes sends a report the same way.
- Show on HomeView. When you use Show on HomeView, for an Apple HomeView™ smart display, the recipe travels inside the link, after the # mark. The link, and the recipe inside it, goes wherever you send it: to the people you share it with and, when you open it in Safari, to your other Apple devices through iCloud Tabs. Browsers never include the part after the # mark in a page request, so when the link is opened our website receives an ordinary page request with no recipe in it, which our web host handles like any other visit. Unlike the rest of this website, that page counts nothing: it carries no Cloudflare Web Analytics and no Umami. The picture loads from where it lives: our own website for one of our drawings, whose address names the kind of dish (for example "italian") or, for a dish we have drawn, the dish itself (for example "fettuccine alfredo"), or TheMealDB for a recipe from TheMealDB, whose picture names that dish. Our drawings are made with Apple Image Playground. HomeView is a trademark of Apple Inc.
- Asking a household member to cook or to choose again. The app writes a small notice to the app's public iCloud database, holding a scrambled code for the member asked, a weekday, and a scrambled code for the person who asked in its record name, and nothing else. "Asks to a household member" above says what it is for and when it is deleted.
- AI planning. By default, meal planning and substitutions run on Apple Intelligence, on your device or in Apple's private cloud (Private Cloud Compute), which is designed so that nobody, including Apple and including us, can read your requests.
Claude, included with Pro (no key needed). Claude is an AI made by Anthropic. The first time you use a Claude feature on a phone, the app asks your permission, in a screen that names Anthropic and lists what can be sent, with two equal buttons, Allow Claude and Don't allow. Nothing is sent to Anthropic before you allow it, on that phone. Your answer is kept on that phone only. It is not synced through iCloud, so each of your devices asks once, and each adult in a household answers for their own phone. You can change your answer any time in Settings, under Privacy and AI, Claude Included. Turning it off stops new requests; it cannot take back what Anthropic has already received. If you do not allow it, nothing is sent and the rest of the app works: Apple's planner, saving and importing recipes, your grocery list, and cooking along.
Once you allow it, what can be sent is only what the feature you use needs, from these six groups:
Your week: how many adults and children, your busy evenings (never what is on them), the names of some saved recipes, the dishes you liked or skipped, and dinners you planned or cooked lately.
Diets and avoids: the diets and allergies set for your household, and the avoid note you wrote. In a household these go along without anyone's name.
Recipes and posts: the words of a link or post the app could not read itself, and the text of a recipe when Claude writes, fills in or changes it. If you ask for a recipe that uses what is on sale, the names of sale items too.
Questions and ideas: what you type or say after "ask" while cooking, with the recipe and step you are on; the dish ideas you type; and the ingredients you type when you ask what you can make tonight.
Photos of recipe pages: pictures of a cookbook page, recipe card or screenshot, sent when you take or choose them so Claude can read them.
Grocery list lines: the open items on one list, when you tap Tidy this list.
Never sent: the names of people in your household, your calendar, prices, store names, your notes on a recipe, or photos of your dishes.
Four things send on their own once you allow Claude, with no tap on that moment: reading a failed import (when the app could not read a link's recipe itself, Claude reads the same words the app had already fetched, up to 12,000 characters, and answers only from them; you can turn this one off in Settings, Recipes, Rescue failed imports with Claude), fixing the words of a picture PDF (the words the phone read, never the picture or the file), filling in a dinner that has only a name when Claude is your planner, and a question you say aloud while cooking (speech is recognized on the phone; only the words go). Until you allow Claude, none of these send: a failed import shows a Try with Claude button instead, a picture PDF is read on the phone, a name-only dinner is filled in on your phone, and a spoken question waits in the Ask box for you to tap Ask.
Anthropic does not train on data sent through its API. As a rule Anthropic deletes API inputs and outputs within 30 days, with exceptions its own page lists. Our server passes the request along and keeps no copy of the request or the answer. It keeps only how many plans, rescues, questions, dinner ideas, one-night dinner suggestions, photos, adaptations and tidies you have used this month, under a one-way code made from your purchase, and deletes those counts after two months. For a plan of both weeks it also keeps a time stamp ten minutes ahead, so the two halves count as one plan, and one number for the whole month, shared by everyone, estimating what Claude has cost us, which is about nobody. During the public beta, every TestFlight tester can use Claude this way, and the same permission screen is shown to them first.
More Claude features (Pro). Each of the features below is one of the six groups above, and each is also gated by your permission. Claude with Pro answers a question while you cook (your question, the recipe's text and the step you are on), reads a photo of a cookbook page or a handwritten recipe card (the photo), suggests dinners from what you type (the foods you list and your household's diet and allergens), suggests or swaps a single dinner for one night (the day, the other dinners that week, some saved recipe names, and your household's diet and allergens), writes a recipe from a dish name or idea you type (and your household's diet and allergens), fills in a dinner that has only a name (the dinner's name, any ingredient and step lines it has, and your household's diet and allergens), adapts a recipe (the recipe's text, the change you pick, your household's diet, allergens and avoid note, and, for "use what's on sale", the names of sale items), reads a failed import (the post or page words, as above), fixes letters the phone misread when you bring in a recipe PDF that is a picture (the words the phone read, never the picture or the file), and tidies a grocery list (the text of the list's open lines). Each goes through our server to Anthropic, which does not train on data sent through its API. Our server keeps no copy of any of it. It keeps only the monthly counts described above.
Your own key (free). If you paste your own Claude, ChatGPT or Gemini key and switch it on, the request goes to that provider instead, under its API terms, and never through our server. Switching the key on is your permission, and the note beside the switch lists what it sends: the same six groups above (the photo group for a Claude key only), straight from your phone to that company, with no extra question. Two things go on their own once a key is on, because they are the same two as above: a failed import is read by your key, and the words of a picture PDF are cleaned by it. You can turn the key off, or remove it, in Settings, Privacy and AI, Your Own AI. We never see your key. On Google's unpaid Gemini tier, Google's terms allow it to use what you send to improve its products and to have people read it; a key billed to a paid Google account is covered by different terms. The app says this beside the key field. - Purchases. Pro is bought through Apple. We receive no payment details. The app verifies your purchase with a signed receipt; our service checks the signature and keeps nothing, with one exception: for Claude planning it keeps a one-way code made from your purchase, so it can count what you use each month.
- If an ad brought you here. The app tells Apple, on the phone, how far it has got: opened, Pro started, or Pro bought. If you installed it after an ad on a network such as Meta, Reddit or TikTok, Apple later tells that network the furthest step, in an anonymous report, through Apple's SKAdNetwork and AdAttributionKit, so an ad can be judged by who stays rather than who downloads. The report carries no identifier and nothing about you or your recipes. Apple sends it, not us, and it never reaches us. Apple does not count it as tracking. Without an ad, there is no report.
Oven Alerts (Pro, Optional)
Paused. Samsung oven alerts are paused for now, so new oven connections cannot be made; what follows describes what is kept for a connection made earlier. If you connected an oven earlier, email hello@itsdinnertimeapp.com and we delete it.
If you connected a Samsung oven, range or cooktop earlier through SmartThings, the app showed what it was doing and alerted you when it turned on, reached temperature, finished its own timer, had a burner turned on, was left on, or had its door left open. This is the one part of the app where our service keeps something tied to you, and it exists only so an alert can reach your phone while the app is closed. If you never connect an oven, none of this exists for you.
While your oven is connected, our service keeps exactly this:
- Which connection is yours. The SmartThings ids for this connection, for your SmartThings location, and for the one oven you chose. SmartThings sends us that oven's changes by these ids, and we ignore changes from anything else.
- The connection's keys. Your SmartThings access and refresh tokens, encrypted, so the connection keeps working.
- Where to send alerts. Your phone's push token, and whether it belongs to Apple's test push service or its normal one, so each alert reaches your phone. While a cook is running, also a second token for the Live Activity on your lock screen, which is cleared when the cook ends.
- Which alerts you want. The switches you set for the six alerts.
- The oven's last reading, and only the last one. Whether it is on, its temperature and set temperature, mode, door, timer and burners, the probe's temperature and target, whether the cooktop surface is still hot, and when that reading arrived. An alert like "Your oven is at 400° F." comes from noticing a change, which takes one earlier reading to compare against. Each new reading replaces the one before.
- A few times, only while the oven is on. When it turned on, when its door opened, and when its own timer finished, plus two notes that the "left on" and "door open" alerts were already sent, so each is sent once. All of them are cleared the moment the oven turns off.
- Two dates for the connection itself. When the app last renewed it, which the 30-day rule below counts from, and when anything in it last changed.
We never keep a history of your oven's readings, a log of what it did, your name, your email, your Samsung password, what you cooked, or anything else from the app. Each alert's words are put together at the moment it is sent and are not stored.
When it is deleted. All of it goes:
- when you email us at hello@itsdinnertimeapp.com and ask us to delete it. Oven alerts are paused, so this is how anyone who connected an oven earlier removes it;
- when SmartThings tells us the connection has been removed on its side;
- in every case, 30 days after the app last renewed the connection. The app renews it each time it starts while you have Pro, so if you delete the app, or Pro ends, the connection goes on its own.
Your phone's push token alone is cleared sooner if Apple tells us it no longer works.
Samsung's own privacy terms cover what SmartThings does with your account.
Connected assistants (Pro, optional)
In Settings you can connect ChatGPT (OpenAI), Claude (Anthropic) or Gemini (Google) so you can ask that assistant about your dinners and have it add or change things. You start the connection from the app and approve it on your phone. During the public beta, TestFlight testers can connect without Pro.
If you share your week with a household, the people in it see which assistant changed a dinner, and that you asked for it. That note stays in your household's iCloud, not on our servers.
A separate server. This runs on its own server, apart from our price service, so the price service stays free of any of it. Its data lives in three tables, and nothing else is stored:
- An encrypted copy of your plan. Your saved recipes, this week and next week, and the open items of your one grocery list, uploaded by your phone. With it, an encrypted push token for your phone and whether it uses Apple's test push service or its normal one, the date your Pro ends (or that it is a lifetime purchase), whether you connected as a beta tester, when your phone last uploaded, a version number for each of the three parts, whether you have switched on alerts for changes an assistant makes (a single on or off setting, which lets the server send a notice that names only the assistant and describes no change), a marker on the one demo copy App Review uses, and a one-way hash of a secret your phone keeps so the server can tell later uploads come from the same phone.
- The connection for each assistant. The sign-in grant you approved, with its tokens stored only as one-way hashes, and two numbers per assistant counting today’s calls and today’s changes, overwritten each day. Alongside the grant: which assistant it is (ChatGPT, Claude or Gemini), the connection details that assistant gave when you approved it (its client id and the address it returns to), a one-way hash of the pairing code you approved with, and when it was last used.
- The assistant’s requests. The adds, changes and removals an assistant asks for, waiting for your phone to apply them. What a request says is encrypted. The kind of request (for example plan a night, save a recipe or add grocery items), whether your phone applied it, and the reason if it did not, are kept in plain form so the server can queue and clear it.
What it never holds. Your calendar, photos, sketches, ratings, cook’s notes, cooked history, allergens or diets, the names or ids of household members, prices or stores, or any analytics. Nothing an assistant sends or receives is logged. Your phone, iCloud and Reminders stay the source of truth; the server is a copy and a queue.
Encryption. Each person’s data is sealed under its own key, and that key is itself sealed under a secret held only on the server. Deleting your row destroys your key. This is encryption at rest, not end-to-end: the server can open your copy at the moment it answers your assistant, and not otherwise.
When it is deleted.
- At once when you disconnect in Settings.
- If Pro ends, the connection keeps working for 3 days to cover a renewal that has not been reported yet, then it pauses, and the copy is deleted 30 days after Pro ends.
- After 60 days with no upload from your phone.
- Within 72 hours after a request has been applied. A request your phone has not applied within 14 days expires, and is then deleted within 72 hours.
- An assistant you approved but have not used for 30 days is disconnected and its connection deleted. A copy of your plan that no assistant has connected to within 30 days of being made is deleted.
- A connection you never approve is deleted after 10 minutes.
The assistant companies. OpenAI (ChatGPT), Anthropic (Claude) and Google (Gemini) run the assistants, not us. What you say to an assistant, what it reads from your copy, and what it keeps are covered by that company’s own terms and privacy policy, and you should read them before you connect. We cannot see your conversations and we cannot delete anything from their systems. The App Store label declares this as user content.
Our web host. When you connect ChatGPT, Claude or Gemini, the connection runs through our web host, Hostinger, which passes your assistant's requests on to our server. Our relay there is written to keep no copy of a request or an answer. Like any web host, Hostinger may keep ordinary server logs of the address and time of a request, which we do not control.
Kroger Data
Prices, products and store locations for Kroger-family stores (Kroger, Ralphs, Fred Meyer, King Soopers, Smith's, Fry's, QFC, Dillons, Pick 'n Save, Metro Market, JayC, Owen's, Pay Less and Gerbes) come from Kroger's public developer APIs, through our price service. This policy is the privacy policy for that use.
What we send Kroger is the search words, the store, and for the store finder a zip code. We send no name, account, email or device identifier, and we collect no personal information from Kroger's APIs. What we keep from them is listed under "Store prices (Pro)" above: a note of which stores are near a zip code, for as long as Kroger's own cache header allows and never more than 24 hours; Kroger's answers to product searches, keyed by store and search words and never by who searched, for at most 6 hours; and one count of searches a day. If you connect your own Kroger account for the cart, you sign in on Kroger's website, Kroger's policy governs it, and the resulting connection stays in your device's Keychain. Nothing from Kroger is used for advertising, and we send Kroger nothing beyond what this section lists.
The Waitlist and Creator Applications
If you join the waitlist or apply as a creator, on our website or in the app, you are choosing to send us a message. We use your email only to reply to you: to send the beta link or to say when the app is in the App Store, or to talk about working together. No marketing beyond that, no spam, and we never sell or share it. A waitlist sign-up is kept on our email list (Hostinger Reach) and also emailed to us; a creator application is emailed to us and not stored anywhere else. Ask at hello@itsdinnertimeapp.com and we will delete either.
What we collect
Almost nothing, and unless you connected an oven for alerts earlier, nothing about you. The App Store label declares a coarse location (the zip code you give the store finder, remembered by place for a day), search history (the product words that pass through our price service, which keeps none of them; its host's request logs can hold them for about a day), user content (a recipe you choose to share with other cooks), photos (a picture of a recipe page that Claude reads, which we never store, and a dish picture you choose to share), and health (your household's diets and allergies, sent with a Claude request so the answer respects them, and never stored by us), none of it linked to you. It also declares your name and email address, linked to you, but only if you type them into the creator partnership form. If you connect an AI assistant, the App Store label also declares user content, linked to the phone that uploads it: the encrypted copy of your recipes, week and grocery list listed under "Connected assistants", which is used to answer your assistant and nothing else. Connecting an oven adds the identifiers listed under "Oven Alerts", which are linked to you because an alert cannot reach your phone without knowing which phone, and which are used for that and nothing else. Sharing your week with your household adds nothing to this list: it lives in your household's iCloud and never reaches us. Nothing is used for tracking, and none of it is sold or used for advertising. The app contains no analytics and no crash-reporting SDKs. (This website, not the app, counts page views, as the short version above says.) The one measurement is the anonymous ad report under "If an ad brought you here" above, which Apple sends to the ad network and never to us. If you choose to share diagnostics with Apple, Apple may show us standard crash reports under Apple's own privacy terms; these contain no recipes, plans, or identities.
Data retention and deletion
Unless you connected an oven for alerts earlier, plan with Claude through Pro or connect an AI assistant, we hold no data about you, so there is nothing for us to retain or delete. If you plan with Claude, we hold monthly counts of how many plans, rescues, questions, dinner ideas, one-night dinner suggestions, photos, adaptations and tidies you have used, under a one-way code made from your purchase, and they are deleted after two months. Because deleting that one row (a one-way code, a month and a few counts) would reset your monthly limit, we cannot delete it when you ask; it is deleted two months after its month. Your permission answer for Claude is kept on your phone only and is deleted with the app; turning Claude Included off in Settings stops new requests but cannot take back what Anthropic has already received. If you connected an oven earlier, "Oven Alerts" above says exactly what is held and when each part goes, and emailing hello@itsdinnertimeapp.com deletes all of it, with or without Pro. (The store finder's zip-to-stores note expires on its own within a day, and the Kroger product answers within 6 hours.) If you connect an AI assistant, "Connected assistants" above says what is held and when each part goes, and Disconnect in Settings deletes all of it at once. A recipe or drawing you share with other cooks stays visible until you remove it or we do. A week you share with your household stays in the iCloud of whoever set the household up until they stop sharing; "Sharing your week with your household" above says what each way out deletes. If you turn on the shared recipes digest in Settings, the app checks for new shared recipes in the background the way it does when you open it, and posts a note on this phone; nothing about you leaves it. Everything the app stores is yours to delete: remove recipes and photos in the app, remove the app to delete its local data, and manage or delete its iCloud data in Settings > iCloud > Manage Storage on your device.
Consent
Dinnertime asks before it first sends anything to Claude (included with Pro), on each device, and shows what can be sent; if you say no, everything else still works, and you can change your answer any time in Settings, Privacy and AI, Claude Included. The app asks permission before using the camera (cookbook pages, dish photos and barcodes), Reminders (your grocery list), location (finding stores near you, only if you use "Use current location"), the microphone and speech recognition (cooking hands-free, including saying Ask to put a question to Claude; speech is recognized on the phone, and a question you say is sent to Claude as text only if you have allowed Claude), Apple Health (only if you turn it on), and notifications (when you first start a cook timer, start Pro, turn on the shared recipes digest, turn on a planning-day, takeout or prep-day reminder, switch on alerts for changes an AI assistant makes, or join or set up a household, for notes from your household). Every feature has a path that works if you say no, and you can change any of these later in Settings.
Children
The It’s Dinnertime app is made for adults who plan and cook meals. It is not directed at children. What we declare above is the same for every user, and we knowingly collect nothing further from anyone, children included.
Changes
If this policy changes, the new version will be posted at this address with a new effective date. Our terms of service are part of the same promise.
Contact
Smart Home Life LLC · hello@itsdinnertimeapp.com