Sizzlo Privacy Policy

Last updated 29 October 2026

Sizzlo turns photos and questions about food into recipes. To do that it sends what you give it to an AI service. This page says exactly what is collected, who sees it, and how to remove it.

What Sizzlo stores

• Your account. An account is required to use Sizzlo, so signing in is the first thing the app asks for. We hold the email address and the name you give us with our database provider (Supabase). Having an account does not move everything to our servers: your saved-recipe photos, your theme and calorie target, and the log of what you have cooked (with its calories), stay on your device either way.
• What you cook. Recipes you save, your shopping list, anything you've liked, and what you've told Sizzlo is in your fridge, freezer and pantry — including anything you add by scanning a barcode, and the dates you type off a package. All of it is held with your account so it follows you between phones. The barcodes themselves are not: when you name a product Sizzlo didn't recognize, that name is remembered on your device only. Photos you attach to a saved recipe are stored on your device too, not on our servers — and, like the rest of your app data, they are included in your own device backup if you make one.
• Your preferences. Cooking skill, goals, the foods you like, would rather skip and must avoid (your allergies and diet), and any nutrition targets you set (such as low salt), held with your account. How long you usually have to cook, how many you cook for, what you cook with, and the swaps you always make (oat milk for milk, say) stay on your device, though the swaps go with each recipe and chef request so the recipe can use them (see Google below). Answers you give before you create an account also stay on your device until the account exists. Sizzlo does not ask for or store any medical condition: a target is an instruction about the food, not a fact about you. Your daily calorie target and theme stay on your device. Your preferred shop is kept on your device too, but it goes with each recipe request so the recipe can link to that shop (see Google below).
• Your calendar. Only if you connect it from Home's calendar. Sizzlo puts the meals you plan on your phone's default calendar and keeps them up to date as the plan changes. If you leave "Show my events" on, it also reads the titles and times of your events for the days on screen, so you can plan around them. Your events are read on your phone, are not stored by Sizzlo, and nothing from your calendar is sent to us.
• Bug reports you send. Only when you use Settings → Report a bug. We keep what you write (a short title, what you did, what you expected and what happened instead), how serious it is and how often it happens, the part of the app and kind of problem you pick, the Sizzlo and iOS version, your iPhone model, and any screenshots you choose to attach. If you tick “Include recent error lines”, we also keep the last few lines Sizzlo wrote about what went wrong since you opened it: which step failed and how long it took. Those lines never include what is in your kitchen, your photos, your messages or anything that identifies you. Reports are kept privately with our database provider (Supabase) and seen only by the people fixing Sizzlo. To work on a fix we may copy a report's text and details, never its screenshots and never your email or account, into a spreadsheet in our Google account (Google Sheets) and into the AI coding assistant we use to fix Sizzlo (Anthropic's Claude). Screenshots are the one kind of picture Sizzlo stores on our side, and only these: your phone re-saves each one as a plain image before sending, which drops its location and other hidden details, and our server checks it again. They are never sent to Google or any AI. A screenshot shows whatever was on your screen, so look before you attach it. A report and its screenshots are deleted automatically two days after you send it, unless we keep it to work on a fix; a kept report, and any copy we made of it, is deleted once we have fixed the problem or decided not to.
• Your Kroger connection. Only if you connect your Kroger account from Send to store. We keep the sign-in Kroger gives us, locked with a key only our server holds, and the Kroger store you picked, so Sizzlo can add the items you approve to your Kroger cart. We never see your Kroger password or payment details, and Sizzlo cannot place an order. A review you have not finished, and the products you picked before, stay on your device. Settings → Privacy and data → Kroger account disconnects it.
• How much AI you've used. A per-month count, so we can apply your plan's coin allowance. We do not keep the contents of those requests.
• Your IP address. Seen by our server on each request, as it is by every website you visit. Used to operate and protect the service, not to build a profile of you.

Where it goes

• Google (Gemini). Photos you take, what you type, what is in your kitchen, your food preferences (allergies, diet, nutrition targets such as low salt, cooking skill, the foods you like and would rather skip, cooking time, servings and equipment), your preferred shop, the swaps you always make, and how you like recipes written (tone, length and units) are sent to Google's Gemini API with each request so it can answer. The chef also receives the first name you gave it and the names of recipes you have hearted. In cook mode, when you ask Sizz to swap an ingredient or explain a step, the recipe you are cooking (its title, ingredients and steps) goes with the question. Your email address and account id are never sent to Google. This is the core of the app, and it cannot work without it. Google processes the request and returns a reply. Read their policy at policies.google.com/privacy.
• Supabase. Hosts the database and sign-in when you use an account. Rows are protected by row-level security, so an account can only ever read its own.
• Resend. Sends the emails that come from signing up and resetting your password, so it receives your email address and that email. Nothing else. Read their policy at resend.com/legal/privacy-policy.
• Apple (sign-in). Only if you choose "Sign in with Apple". Apple tells us your email address — or a private relay address, if you choose to hide yours — and, the first time only, your name. Nothing else. This is separate from anything the AI does.
• Google (sign-in). Only if you choose "Continue with Google". Google tells us your email and name, nothing else. This is separate from the AI processing above and happens whether or not you use the AI features.
• Recipe sites you paste. When you paste a link, our server fetches that public page to read the recipe. We send no information about you to that site, but our server does handle the address you pasted, which reveals which page you were reading. If the page carries a photo of the dish, your phone loads that photo from wherever the page hosts it — so that host sees the request and your device's IP address, in the same way Unsplash does below.
• TheMealDB. We look up a dish photo by name. Only the dish name is sent.
• Unsplash. The photographs on the built-in recipe cards are hosted by Unsplash, so your phone loads them from there. Nothing about you is sent — but, like loading any image on the web, Unsplash sees the request and your device's IP address. Read their policy at unsplash.com/privacy.
• Open Food Facts. When you scan a barcode Sizzlo has never seen, the number on the package is sent to Open Food Facts to ask what the product is, and only when the scan is not already answered from the food database on your phone. When you choose “Search Open Food Facts” while adding something to your kitchen, the words you typed are sent to them instead. Either way that is all that is sent: no account, no location, no photograph. Your phone asks them directly, so, like loading any web page, they see the request and your device's IP address. Read their policy at openfoodfacts.org.
• USDA FoodData Central. When you type the name of something to add to your kitchen, the words you type are passed by our server to the U.S. Department of Agriculture's FoodData Central to find matching foods. Only those words are sent, with no account, no location and nothing about your device. Read their policy at usda.gov/privacy-policy.
• Kroger. Only when you use Send to store with Kroger, or Compare prices with a ZIP code while live Kroger prices are on. Our server sends Kroger the words of each shopping-list line it looks for, the ZIP code you type to find a store, and the store you pick. When you tap “Add to my Kroger cart”, it sends the products and quantities you approved, under your Kroger sign-in. Nothing else about you is sent. Sizzlo never places an order or handles payment: you check out with Kroger, under their privacy policy at kroger.com.
• Instacart. Only if you choose Send to Instacart. Our server sends Instacart the names and amounts of the items you send, and nothing about you: no account, no location. Instacart returns a page of its own, which opens in Instacart's app or website. What you do there, including choosing a store and paying, is under Instacart's privacy policy at instacart.com.
• RevenueCat. Handles subscriptions. When you sign in, RevenueCat receives your Sizzlo account id, so a plan you buy later follows your account rather than one phone, and our server asks it what that account holds. When you buy, restore or cancel a plan, it also receives which plan you hold and basic purchase and device information from Apple. Before a free-preview account is deleted for not being used, our server checks with RevenueCat that it bought nothing, then deletes its record there. It never sees your recipes, your photos or your messages. Read their policy at revenuecat.com/privacy.

What Sizzlo does not do

• No advertising, and no ad networks.
• No analytics or tracking SDKs. We do not track you across other apps or websites, and there is no App Tracking Transparency prompt because there is nothing to ask for. RevenueCat, above, handles payments only, and is not used for advertising or tracking.
• We do not sell your data, and we do not build a profile of you to share with anyone.
• We ask for no Apple Health permission at all, and neither read from nor write to it.
• Speaking your ingredients is transcribed by your iPhone itself. The recording never reaches Sizzlo and is not sent to Apple. If your device has no offline voice model for your language, Sizzlo tells you on the listening screen before it starts, and Apple transcribes that recording under their privacy policy. The words you end up with are then treated like anything else you type.

Keeping and deleting

• Your data stays until you remove it. Individual recipes and fridge items can be deleted as you go. There are two exceptions. Bug reports delete themselves, as described above. And an account that has never bought a plan (the free preview) is deleted, with everything in it, once it has not been used for 60 days; we tell it has been used from the sign-ins, purchase checks and requests the service already records, and keep no separate record of your visits. If you allow notifications, the app reminds you a week before. As with Delete account below, if it used any of its two free coins of AI, a one-way fingerprint of its email and how many it used is kept.
• Settings → Account → Download my data gives you a copy of everything held with your account, as a file you can keep. Your Kroger sign-in is not in it: it is a key to your Kroger cart, not something you gave us.
• Settings → Account → Delete account erases your account and everything attached to it (recipes, fridge, shopping list, likes, preferences, usage counts, your Kroger connection, and any bug reports and their screenshots) from our servers and from this device, along with your purchase record at RevenueCat. It is immediate and cannot be undone. It does not cancel an App Store subscription: Apple bills that, so cancel it in your Apple Account settings first. One thing is kept: if the account had used any of its two free coins of AI, we keep a one-way fingerprint of its email (never the address itself) and how many it used, so a new account with the same email does not get them again.
• Deleting the app takes everything that only ever lived on this device with it: your saved-recipe photos, and your theme and calorie target. Your account is separate, and stays until you delete it.

Children

Sizzlo is not directed at children under 13 and we do not knowingly collect their data. Creating an account asks for your birthday so the app can check you are 13 or older. That check happens on your phone: the date is never stored and never sent to us. If you believe a child under 13 has made an account, write to the address below and we will delete it.

Questions

Write to sizzlobusiness@gmail.com and we'll answer.