Privacy Policy

Overview

Chef Chop is an AI cooking assistant at chefchop.app, operated by Intentional Products LLC ("Chef Chop," "we," "us"). This policy explains what we collect, what we do with it, which companies handle it for us, and what you can control. It describes how Chef Chop works today. Where something is about to change, we say so and mark it Coming soon.

The short version:

• We do not sell your personal information.
• Your conversations, memories, pantry and plans are sent to OpenAI to write Chef Chop's replies. OpenAI, which processes your chats and food data, does not train on it under our API terms. We also review conversations with other AI tools, including Anthropic's Claude, to improve Chef Chop. Anthropic may use what we share to train its models.
• We use PostHog for product analytics, including recordings of what appears on screen. Anything you type into a text box is hidden while you type, but a message you send shows up in those recordings like any other text on the page.
• An OpenAI Ads tag on our pages tells OpenAI when someone signs up or subscribes, so we can measure our ads.
• Recipes you save are public by default.
• Reviews are always public, with your name and picture.
• There is no delete-account button yet. Email us and we will delete your account for you.

Information we collect

Your account

• Email sign-up: your email address and a password. Our sign-in provider, Supabase, stores the password only in scrambled (hashed) form.
• Sign in with Google: your name, email address, profile picture, language setting and Google account ID. Details are in Google user data.
• Sign in with Apple: your email address (which may be an Apple relay address) and your name, if Apple shares it.
• Guests: if you chat without signing up, we create a guest account with no email address. What you do as a guest is stored with that guest account and moves to your new account if you sign up.
• Your answer to "How did you hear about us?", if you give one.
• Subscriptions: your plan, its status and your Stripe customer ID. You enter card details on Stripe's checkout page; they never reach us.

What you create in Chef Chop

• Conversations: your messages, Chef Chop's replies, the title we generate for each chat, and any thumbs up/down and comments you leave.
• Memories, pantry, plans and recipes, described in their own sections below.
• Cooks and reviews: when you tap Made, the date you cooked a recipe, plus any stars, words and photo you add (see Recipes).
• Imports: text you paste from another AI assistant to import memories.
• Feedback and reports: product feedback and recipe reports you send us, along with your account ID, the page you were on and your browser type.

What we collect automatically

• Usage: pages you visit, buttons you tap, features you use, your device and browser, the site that referred you and any campaign (UTM) tags in the link you followed. Sign-in events also record your IP address.
• Session recordings of how you use our pages (see Analytics).
• Error reports when something breaks.
• Request logs kept by our hosting providers (IP address, web address, time).
• Cookies and local storage (see Cookies).

How we use it

• To run Chef Chop: answer your questions, remember what you tell it, keep your pantry and plans, save recipes, and send the emails described below.
• To personalize it: use your memories, pantry and plans so suggestions fit you, including checking replies against allergies you have told us about.
• To improve it: we look at analytics and session recordings, and we read conversations, ourselves and with the help of AI tools, to find bugs, see where Chef Chop gave a bad answer, and decide what to build next.
• To keep it working and safe: debug problems, prevent abuse, and secure accounts.
• To understand our marketing: learn which links, sites and ads bring people to Chef Chop.
• To meet legal obligations, such as keeping payment records.

AI processing

Chef Chop's replies are written by OpenAI models. To answer you, we send OpenAI your conversation together with the context Chef Chop uses: your memories, household details, summaries of past conversations, pantry, plans, the recipe you are looking at, and your local date and time zone. We do not add your name or email address to these requests. They are included only if you type them into the chat.

OpenAI also processes your data in the background. It pulls memories, pantry items and plans out of your conversations, summarizes past conversations, titles your chats, writes your "About you" summary, suggests meals and writes recipes for your plan, checks replies against your allergies, and spots duplicate memories.

Message classification. We send the text of short chat messages (400 characters or fewer) to TypeSafe, an AI model that answers yes-or-no questions about them, such as whether a question needs current information from the web. It gets the message only, without your name, email address, account ID or earlier messages.

Training. OpenAI, which processes your chats and food data, does not train on it under our API terms. OpenAI may keep what we send for up to 30 days to monitor for abuse. We do not train AI models of our own on your data.

Tracing. We record each AI request and response, including the context above, in LangSmith, a tool for debugging and evaluating AI. Records are linked to your account ID, not your email address. Thumbs up/down ratings and comments are recorded there too.

Conversation review. We also analyze conversations with other AI tools, including Anthropic's Claude, to find problems and ideas for improving Chef Chop. We do not include your name or email address in these reviews, unless you typed them into a conversation. Anthropic may use what we share to train its models.

Memory

Chef Chop keeps a set of memories about your cooking so you do not have to repeat yourself. These are short facts, such as "allergic to peanuts," "owns a Dutch oven" or "dislikes cilantro," saved as you chat (as a guest or signed in) or imported by you from another AI assistant. They cover food allergies and dietary restrictions, dietary identity (such as vegetarian, vegan or kosher), ingredients you like and dislike, your kitchen equipment, nutrition goals, who you cook for, your schedule, and how you want Chef Chop to help. Some of these are sensitive: a dietary identity can reflect a religious, medical or ethical commitment. Chef Chop also writes a short "About you" summary from them.

Your memories are stored with your account and are not shown to other users. They are part of what we send to OpenAI to write a reply. When a memory is first saved, its text is also recorded in our analytics (PostHog) and AI traces (LangSmith).

Settings → Memory lists the memories Chef Chop is confident about and lets you edit or delete any of them. Deleting a memory there deletes it. If you correct Chef Chop in chat (for example, "I'm not allergic to that anymore"), the old memory is marked as no longer true and kept, so Chef Chop does not learn it again. "Delete all memories" deletes all of your memories, including any not shown on that page and any marked as no longer true, along with the "About you" summary. Deleting a memory does not delete the conversation it came from, or the copies already recorded in analytics and AI traces.

There is no way to turn memory off. If you would like one, email us at hello@chefchop.app. We keep memories until you delete them; they do not expire.

Pantry and plans

Chef Chop can keep track of the food in your kitchen (your pantry) and the meals you plan, built from what you mention while you chat. For example, "we picked up eggplant" or "let's make salmon bowls Thursday." Your memories, pantry and plans are three separate stores: clearing one does not clear the others. They are stored with your account, not shown to other users, and sent to OpenAI to write replies and suggestions.

You can remove any pantry item from the Pantry page, and Settings → "Clear pantry" removes all of them. A removed item no longer appears in your pantry or in what Chef Chop uses. We keep it marked as removed, with a record of the removal (the item's name, type, where it was kept and how it was added), so Chef Chop learns not to add it back. You can undo a removal.

You cannot delete individual plan entries yet. Dismissing a suggestion or cancelling a planned meal marks it that way and keeps it.

Recipes

Recipes you save are public by default. Anyone with a recipe's web address can view it, recipes are listed in our sitemap so search engines can find them, and the recipe page shows your display name and profile picture. There is no setting yet to make a recipe private. You can delete any of your recipes at any time, but copies other people saved stay (see below).

Reviews

Reviews are public. When you tap Made, we record that you cooked the recipe. We don't show that to other users. If you add a review, its stars, your words, any photo, your profile picture and your name show on the recipe page to anyone who can see the recipe, signed in or not. Your name is your first name and last initial when we have them; otherwise your first name, or "A cook". Stars you tap count as a review, even if you then tap Skip. The page also shows the average rating and how many people reviewed and saved the recipe, as numbers, not names.

To delete a review, open the ⋯ menu on it and choose Delete. That removes the review and its photo from the recipe page; a cached photo can take about an hour to clear. The record of your cook stays. To remove the cook too, choose Remove this cook in the recipe's History, which also removes any review on it.

Copies of a deleted review stay in AI traces and recordings, and anything Chef Chop learned from it, such as a memory or recipe change, stays until you remove it. Search engines or other people may also keep copies.

Saved copies

A saved copy belongs to the person who saved it. It includes your recipe's title, text, notes and photo, and stays public if you delete your recipe or account. While your recipe is public, the copy's page credits it, with your name and picture. The copy also keeps a private record of the recipes it came from, including their titles, which doesn't say who owned them. If a copy contains your personal details, email us and we'll remove them.

Calendar feed

If you turn on the calendar feed (in Settings or on your Plans page), Chef Chop creates a private web address (URL) that calendar apps such as Google Calendar or Apple Calendar can subscribe to. The feed lists the meals and cooking steps on your plan from the past week through the next four weeks, with each one's ingredients, estimated time, and a link back to Chef Chop. It is off until you turn it on. Chef Chop does not read anything from your calendar.

The feed URL works like a password: anyone who has it can see your plans, without signing in. Keep it private. We store only a scrambled (hashed) version of it, so we can show you the link only once, when you create it. Because the secret is part of the web address, it appears in our hosting provider's request logs, and your calendar provider keeps its own copy of the feed.

You can regenerate the link or turn the feed off in Settings at any time. Either one stops the old link from working right away, but your calendar app may keep showing the plans it already downloaded for up to a day.

Email

We send email through Resend. Today we send:

• password reset emails, when you ask for one;
• subscription emails: a welcome when you start a trial and a reminder before it ends;
• occasional product updates, only to registered users who have not opted out. Each one has a one-click unsubscribe link.

When you start a trial we also email ourselves a notice with your name and email address.

Weekly plan email (Coming soon)

We are about to start a weekly email, "Your week at Chef Chop." It will be on by default for registered users (guests get nothing) and arrive on Sunday morning in your time zone. It will greet you by first name and include what you cooked last week, pantry items close to running out, the meals on your plan, and up to three suggestions based on your pantry and memories.

• Every weekly email will have a one-click "Turn off the weekly email" link that works without signing in. A spam complaint turns it off too.
• Links in the email carry single-purpose codes. The turn-off code can only turn off the weekly email. An "add to plan" code works once, expires after 14 days, and only works when you are signed in as the person it was sent to. We store only scrambled (hashed) versions of these codes.
• We will record whether each email was delivered, opened or clicked, in our database and in PostHog. We stop sending if you have not opened, clicked or chatted for eight weeks in a row.

Analytics, recordings and the ads tag

Product analytics (PostHog)

PostHog receives the usage events described above. When you have an account, it also receives your account ID, email address, name, plan, and how you found Chef Chop. If you signed in with Google, your name and email come from your Google account. A few events carry content: when Chef Chop saves a memory, the event includes the memory's text, and some events include up to 200 characters of a message you sent.

Session recordings

On chefchop.app, PostHog records how you use our pages: clicks, scrolling, navigation and what is shown on screen, including your conversations, recipes, memories and the email address shown in Settings. It also records browser console messages. Text you type into a text box is masked while you type, but once you send a message it appears on screen and is visible in the recording.

Error reports (Sentry)

When something breaks, Sentry receives an error report linked to your account ID. We remove email addresses and sign-in tokens from these reports before they are sent. For a share of sessions that hit an error, Sentry also keeps a short replay in which all text, inputs and images are masked.

OpenAI Ads tag

We advertise in ChatGPT and use OpenAI's measurement tag, which loads on every page of chefchop.app. It tells OpenAI when someone signs up, starts a trial or subscribes (with the plan and amount), so we can count which ads led to signups. It sets its own cookies to remember an ad click. The tag's "automatic matching" setting is on: it can detect an email address, phone number or name typed into a form on our site and send OpenAI a scrambled (hashed) version to match a signup to an ad. We do not give the tag your name, email address, account ID or anything from your Google account.

Turning these off

We do not have an in-app switch to turn off analytics, recordings or the ads tag. Browser content blockers usually block them, and Chef Chop still works when they are blocked. You can email us to delete your analytics profile and recordings.

Google user data

Signing in with Google

If you sign in with Google, we ask Google only for basic sign-in access (your name, email address and profile). Google shares with us your name, email address and whether it is verified, your profile picture, your language setting, and your Google account ID. To get your language we may ask Google's profile service once when you sign in; if Google has none, we use your browser's language. We never see your Google password, and we do not access your Gmail, Drive, contacts or calendar.

We use this information to create and secure your account, show your name and picture in the app, on recipes you save and reviews you post (both public, see Recipes), greet you by first name in emails, and set your language. It is stored in our database (Supabase). Like every account's name and email, yours is also part of your analytics profile in PostHog. Your email goes to Stripe if you subscribe and to Resend when we email you. We do not sell Google user data, use it for advertising, or give it to the OpenAI Ads tag or any other advertising service.

Connecting Google Calendar (Coming soon)

Nothing is read from your calendar today. We plan to let you connect Google Calendar from your Plans page so Chef Chop can fit cooking around your week. It will be optional, and off unless you choose to connect. If you do, Chef Chop will ask Google for one calendar permission: to see when you are free or busy. With it we can see only the start and end times of busy periods on your primary Google Calendar. We cannot see event titles, descriptions, locations, guests or your other calendars, and we cannot create, change or delete anything in your calendar.

• How we will use it. When we prepare your weekly plan, and when you ask Chef Chop about your week, we will look up your busy times for the next seven days and turn each evening into a simple availability note, such as "free 6–8pm" or "busy until 7:30pm." We will use these notes only to suggest when to cook, how quick a meal should be, and when a prep session fits. Your calendar will never move or change your plans.
• What we will store. An encrypted token that lets us ask Google for your free/busy times, and the per-evening availability notes. We will not store your busy times themselves, and we will delete each evening's note within seven days after that evening.
• Who can see it. Availability notes will be sent to OpenAI to write your suggestions, like your conversations, and will not be used to train AI models. Calendar data will not be sold, used for advertising, or shared with analytics or advertising providers, and session recordings will not capture calendar availability shown in the app. We will not use Google user data to develop, improve or train generalized AI or machine-learning models. No one at Chef Chop will read your calendar data unless you ask us to for support, it is needed for security, or the law requires it.
• Disconnecting. You will be able to disconnect Google Calendar in Settings at any time. Disconnecting deletes our token, asks Google to revoke it, and deletes your availability notes. You can also remove Chef Chop's access at myaccount.google.com/permissions.

Limited Use

Chef Chop's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Who processes your data

These companies handle personal data for us. Except where noted, they use it only to provide their service to Chef Chop:

• Supabase: Our database and sign-in provider (hosted on AWS). Stores your account and everything you create in Chef Chop.
• Vercel: Hosts the chefchop.app website. Keeps request logs (IP address, web address, time).
• Railway: Runs the service that talks to our AI models and does background work such as saving memories.
• OpenAI: The AI models behind Chef Chop’s replies and background processing. Separately, the OpenAI Ads tag measures signups from ChatGPT ads.
• TypeSafe: An AI model that classifies short chat messages (for example, whether a question needs current information from the web). It sees the message text only, not your name, email or account ID.
• Brave Search: Looks up current information on the web. It gets the search query, not your name, email or account ID.
• LangSmith (by LangChain): Records AI requests and responses so we can debug and evaluate Chef Chop.
• Anthropic: Its Claude models help us review conversations to find problems and product improvements. Anthropic may use what we share to train its models.
• PostHog: Product analytics, session recordings and feature flags (US data region).
• Sentry: Error reports, so we can find and fix crashes.
• Resend: Sends our emails and tells us whether they were delivered, opened or clicked.
• Stripe: Payments and subscriptions. Your card details go to Stripe, never to us.
• Notion: Where we keep product feedback and recipe reports you send us.
• Slack: Internal alerts when something breaks. These contain error messages, not your conversations.

Google and Apple handle sign-in when you choose them. We may also disclose information if the law requires it, or to a buyer if Chef Chop is sold or merged.

What we don't do

• We do not sell your personal information.
• We do not use your conversations, memories, pantry or plans for advertising.
• We do not show your conversations, memories, pantry or plans to other users. Two exceptions: recipes, public by default, and reviews, public even though you write them in chat.
• We do not train AI models of our own on your data. OpenAI, which processes your chats and food data, does not train on it under our API terms.
• We do not give your Google account data to advertising services.

Keeping and deleting data

We keep your data until you delete it or ask us to delete your account. Nothing in your account expires on its own, including conversations, and guest accounts that never sign up.

What deleting does

• Memories: deleting one in Settings deletes it; "Delete all memories" deletes all of them and your "About you" summary (see Memory).
• Pantry: removing items marks them removed and keeps a removal record (see Pantry and plans).
• Plans: entries cannot be deleted yet, only dismissed or cancelled.
• Recipes: deleting a recipe deletes it and its reviews. Copies other people saved stay, with the record of where they came from (see Recipes).
• Reviews and cooks: deleting a review removes it and its photo from the recipe page. Removing a cook deletes the cook and any review on it. Some copies stay (see Recipes).
• Ratings: you can take back a thumbs up or down, which deletes it.
• Conversations: you cannot delete them yourself yet. Email us and we will.

Deleting your account

There is no delete-account button yet. Email hello@chefchop.app from the address on your account and we will delete your account and everything stored with it (conversations, memories, pantry, plans, recipes, reviews and your profile) within 30 days. We will also delete your PostHog analytics profile and recordings. Copies in AI traces, error reports and email logs are kept until those services' retention periods end, and Stripe keeps payment records as the law requires. Feedback and reports in Notion are kept. Copies other people saved stay (see Recipes). Backups kept by our database provider expire on their own schedule.

Your choices

In Chef Chop you can:

• review, edit or delete your memories at Settings → Memory;
• remove pantry items, or clear your pantry in Settings;
• delete recipes;
• turn the calendar feed on or off, or regenerate its link;
• manage or cancel your subscription at Settings → Subscription;
• unsubscribe from product updates (and, when it launches, the weekly plan email) using the link in the email.

By emailing us, you can ask us to:

• send you a copy of your data;
• correct your name or email address (you cannot change them in the app yet);
• delete your conversations, analytics data or account;
• stop any non-essential email.

Email hello@chefchop.app from the address on your account. We will reply within 30 days. You can remove Chef Chop's access to your Google account at any time at myaccount.google.com/permissions.

Cookies and local storage

We and the services above store small pieces of data in your browser:

• Sign-in cookies from Supabase that keep you signed in.
• Attribution: the campaign (UTM) tags from the link you followed, kept for up to 30 minutes so they survive the sign-in redirect.
• Preferences, such as light or dark mode.
• PostHog cookies and local storage that tie your visits together for analytics.
• OpenAI Ads tag cookies that remember an ad click.

We do not show a cookie banner. We do not use Google, Meta or TikTok advertising pixels.

Children's privacy

Chef Chop is not directed at children under 13. We do not knowingly collect information from children under 13. If you believe a child has given us information, email us and we will delete it.

Changes to this policy

We will update this policy as Chef Chop changes and change the date at the top. For material changes we will also post a notice on our website or email you.

November 1, 2026: added cooks and public reviews, how to delete them and what stays afterwards, and what a saved copy keeps. Added Brave Search, which we had left out. Corrected our statement that every company listed uses data only to provide its service: Anthropic may use what we share to train its models. Corrected what deleting a recipe or account leaves behind. Previous version: October 18, 2026.

October 18, 2026: added TypeSafe, which classifies the text of short chat messages. Previous version: October 9, 2026.

October 9, 2026: rewritten to match how Chef Chop works today. Named the companies that process your data; added the OpenAI Ads tag, session recordings, Google sign-in data, public recipes, conversation review and the coming weekly plan email and Google Calendar connection. Removed promises the product does not yet keep: a delete-account button, conversation downloads, and an analytics opt-out. Previous version: October 8, 2026.

Contact

Questions about this policy or your data? Email us at hello@chefchop.app or write to: