Privacy Policy
Last updated September 29, 2026
ClipKitchen is a meal-planning app. This policy describes the information we collect, why we collect it, and how you can delete it. It matches what the app actually does today — not a generic template.
Information we collect
- Account. If you sign in with Google, Apple, or email and password, we store your account email and name through Better Auth on our own origin. We do not get your Google or Apple password.
- Kitchen data. Pantry items, meal plans, saved recipes (which ones you make often, and your changes to them), and food preferences (foods you prefer or ban) are stored in Supabase and scoped to your signed-in account id. Signed-out use stays on this device only.
- ZIP and stores. The ZIP you enter and the grocery stores you pick are used to load weekly circulars and meal suggestions.
- Recipes you add. When you add a recipe from a link, photos of a recipe card, or pasted text, it’s sent through our server to xAI’s API, which reads the ingredients and steps back to us; we don’t keep the page, photos or text on our server. A photo of the dish you add to your recipe is stored on our server (Supabase) so it shows on your recipe card on your devices. Its web address is long and random, not listed anywhere. Deleting your account deletes your dish photos. When a recipe you add has no photo, our server looks for an openly licensed photo of the dish by the recipe’s name alone, from TheMealDB, Wikipedia, Wikimedia Commons and Openverse; nothing about you goes with it, and the photo’s author and license show under it.
- Recipes you share. If you choose to share one of your own recipes with every family, its name, time, servings, ingredients, steps and dish photo are stored on our server (Supabase) for a reviewer to check. Once approved, every ClipKitchen family can see and cook it, credited only as “Shared by a ClipKitchen family” — never your name or email. Reviewers see the recipe, not who sent it. Deleting your account removes it from everyone’s meals and deletes the copy we kept.
- Receipt photos. When you scan a receipt, the photo is read on this device and also sent through our server to xAI’s API, which reads the line items back to us. We don’t keep the photo on our server. It is sent to Open Prices only if you turn on “Share confirmed receipts with Open Prices” in Settings.
- Pantry photos. When you’re signed in and use ClipIQ on a photo of your fridge or shelves, the photo is first redrawn on your device (which drops its location and camera details), then sent through our server to xAI’s API, which lists the foods it can see. We don’t keep the photo on our server, and nothing is added to your pantry until you tick it. When you fix what ClipIQ read, the fix is remembered on this device only, and signing out removes it. As a guest, shelf photos aren’t read.
- Receipt prices. When you save a receipt, the price of each food we recognize goes to our own database so families near you see real prices at each store: only the store, the food, its price, the receipt date and the first three digits of your ZIP. Nothing identifies you, your account or your device. A price you correct at checkout (“Different price at the store?”) goes the same way, as the store, the food, that price and the day. Turn it off in Settings → Receipts.
- Your receipts and shops. When you’re signed in, the receipts you save (the store, the day, the items and prices read from it, its total and the savings it prints) and the shops you confirm with “Yes, I got it” (the store, the day, how many items, the total and the app’s estimate of the sale savings) are kept with your account on our server (Supabase), so your savings total and receipts follow you to a new phone. As a guest they stay on this device only. Deleting your account deletes them.
- Savings pilot. Only if you join the savings pilot (from the app tour or Settings), for two weeks each receipt you save sends our own database the store, the receipt date, what you paid, how many items, and the savings the receipt prints, plus the weekly grocery spend you told us is usual if you gave one. A shop you confirm with “Yes, I got it” instead of a receipt sends the store, the day, the total you confirmed, how many items, the app’s estimate of what they cost, and its estimate of the sale savings, marked as confirmed rather than from a receipt. They’re tied together by a random pilot ID made on your device — never what you bought, your name, your account or your ZIP. Leave in Settings → Savings pilot and we delete all of it; deleting your account does too.
- Receipts by email. Only if you turn it on in Settings, your device makes its own receipt address, and any email you forward to it is received by Resend, an email service, and read once by our server. We keep only the store, the day, the total, the item count and the savings it prints (or, for Gmail’s forwarding confirmation, its code), under that address’s random ID until your app collects it; the email itself — its sender, subject and body — is not stored. If an email isn’t a receipt we can read, we keep only the sender’s domain (like walmart.com) so the app can tell you. Collected rows are deleted from our server, and anything not collected is deleted after 30 days. Turn it off in Settings → Receipts by email.
- Barcodes. When you scan a package’s barcode, the camera image is read on your device (in the apps, by Google’s ML Kit scanner, on the phone) and only the barcode number goes to our server. Our server asks Kroger, Open Food Facts and USDA FoodData Central what product that number is, and keeps the answer so the next scan is faster. The barcode number is never linked to your name or account.
- Voice. When you add pantry items by voice, the recording is sent through our server to xAI’s speech-to-text API to turn it into text. We don’t keep the recording.
- Taste. The dinners you plan, save, make often, cook and rate, the suggestions you pass on, and how long you spend reading a recipe shape which dinners and groceries we suggest. As a guest this stays on your device. When you’re signed in, your ratings and the dinners you’ve hidden are kept with your account on our server (Supabase) so they follow you to a new phone; they’re never shared with anyone else, and deleting your account deletes them. Signing out takes your kitchen, ratings and receipts off this device; signing back in brings them back. Removing a dinner from History clears it from your account too; we keep only the recipe’s id and when it was marked cooked, so your other devices remove it as well.
- Usage. Vercel Web Analytics counts page views and a few app events (a dinner planned or taken off the week and whether it was the week’s “Something new” dinner, how many dinners were added at once, an item added to the list, which store’s checkout was opened, a “one grocery away” suggestion shown, added, bought or cooked — never which item or dinner). We also keep those same events, plus one “opened the app today”, the app tour started, skipped or finished and at which step, joining or leaving the savings pilot, that a shop was confirmed (at the end of checkout or from the Meal Board), that a receipt was kept, that a planned dinner was marked cooked, that your savings total was shown, that pantry items were added from a photo (never which ones), that one of the day’s pantry questions was answered (never which item or the answer), that a question on the cart about what’s still home was answered (never which item or the answer), that the cart was opened (never what’s on it), whether a store’s shop was started for pickup or in store (never what’s on the list), whether the week the Meal Board picked had a “Something new” dinner and how many dinners it had, and whether a dinner planned or marked cooked was that one (never which dinner), that the iPhone app asked about notifications and whether they were turned on, that you added dinners you make often or skipped that step and how many you added (never which dinners), and, for the first minutes of use, whether you started with Apple, Google, email or as a guest, whether setup was finished, whether the Meal Board showed dinners or couldn’t, and whether the app tour was offered or put off, in our own database (Supabase) with a random ID made on your device — not linked to your account, and never what you cook, buy or have in your pantry — so we can see whether people keep using the app. A failed Meal Board sends whether it timed out and how long it took, in milliseconds. None of this uses cookies or advertising identifiers, and we don’t use it to track you across other apps or sites.
- Feedback. When you use Send feedback in Settings, we keep your note, the screen you were on, whether you use the iPhone app, the Android app or the website, and, if you’re signed in, your account ID, in our own database (Supabase) so we can read it and follow up. The same details are emailed to our support inbox through Resend, an email service, so we see them quickly. Nothing is sent until you tap Send, and deleting your account deletes the notes you sent while signed in from our database.
How we use it
- To sign you in and keep your kitchen in sync across devices.
- To rank dinners, sides and desserts from what’s on sale near your ZIP and what’s already in your pantry.
- To generate AI meal suggestions and price estimates, read receipts and pantry photos, and understand voice input. Those requests go to xAI’s API from our server — not from your phone directly — and can include your pantry items, food preferences, the stores you picked, and your ZIP’s city.
- To see which parts of the app get used, so we know what to fix and improve.
- To find crashes and errors with Sentry on both the client and the server, so we can fix the app.
Who else sees data
- Google or Apple, only for the sign-in you choose.
- Supabase, for account-scoped kitchen rows, the dish photos on your own recipes, and recipes you share.
- xAI, for meal suggestions, price estimates, receipt and pantry photos, recipes you add, and voice recordings our server sends.
- Vercel, which hosts the app and counts usage.
- Flipp, which our server asks for the weekly circulars near your ZIP.
- Walmart, which our server asks for product prices and stock by grocery name (like “whole milk”) for your cart, with your ZIP code so it can check your nearest Walmart — never your name or account.
- Raley’s, whose public product pages our server reads for prices of the groceries in your cart — never your name, account, or ZIP.
- Kroger (Fred Meyer and Kroger stores), which our server asks for product prices and stock by grocery name for your cart, with your ZIP code so it can find your nearest store — never your name or account. It’s also asked what a scanned barcode is, by the barcode number alone.
- Open Food Facts and USDA FoodData Central, which our server asks what product a scanned barcode is, by the barcode number alone — never your name, account, or ZIP.
- Kroger again, only if you tap “Connect Fred Meyer” (or Kroger): you sign in on Kroger’s own page, and Kroger gives our server a key that can only add products to your Kroger cart. We keep that key on our server, never on your phone and never shown to anyone, and use it only when you tap “Fill my cart”. Kroger doesn’t learn who you are in ClipKitchen. The key is deleted when you delete your account.
- Sentry, for crash and error reports.
- Open Prices, only with the Settings opt-in above.
- Anyone you send a shared list link to — the link shows that list to whoever opens it.
- Grocery stores you check out with. ClipKitchen opens that store’s own app or website. We do not place the order, and we do not receive a copy of your store account password from them. In the iPhone app, the store’s site opens in an in-app browser; so you stay signed in to the store between visits, the app keeps that site’s sign-in cookies in this phone’s Keychain (this device only, never synced or sent anywhere, dropped after 30 days unused). We never see or keep your store password. Signing out of ClipKitchen or deleting your account removes them.
Account deletion
You can delete your account in the app: Settings → Account → Delete account. That flow is immediate (there is no email undo). It removes your Better Auth account and every associated kitchen row we store for you (device state with your synced receipts and shops, pantry, food preferences, saved recipes with which ones you make often, week plan, your Kroger connection, and lists you've shared), then clears ClipKitchen data on this device, including any store sign-in the iPhone app kept. If you signed in with Apple, the app first asks Apple to confirm and then revokes ClipKitchen’s access to your Apple ID. Terms of Service describe the product itself.
What we don’t do
We don’t sell your data, show ads, or use your data to track you across other companies’ apps and websites.
Children
ClipKitchen is not directed at children under 13, and we do not knowingly collect their data.
Contact
Questions about your data or this policy: hello@clipkitchen.app.
Changes
If this policy changes, we will update the date at the top of this page. Continued use after an update means you accept the revised policy.