Last updated: October 21, 2026
Welcome to MyChefAI. This Privacy Policy explains how we collect, use, and disclose information when you use our application.
Account data: name, email address, user ID, sign-in credentials and basic Google profile data when you use Google sign-in. A name is required for email signup; additional profile details are optional.
Content you provide: chef conversations and preference-question answers, uploaded photos, saved or imported recipes, saved meal plans and notes, shopping lists, favorites, ratings, comments, community photos and other published content. We also store support requests, app feedback and content reports.
You may voluntarily provide dietary preferences, allergies, restrictions and health information, such as diabetes, in conversations or your profile. These details can become part of your stored history and personalized suggestions; you do not need to share them to create an account.
The public name, biography, website, photo and location you choose to add are optional profile details and may appear publicly. Location is the information you enter, not a GPS reading. We do not request precise device location or access to your contacts.
Website subscriptions are processed through Stripe; purchases in the native Android app are billed through Google Play. We store account and purchase identifiers, verification data and subscription status to manage access and prevent purchase misuse. We do not see or store full card numbers. The billing provider processes your payment data under its own policy.
Operational data: session identifiers and timestamps, IP address and user agent associated with sign-in, usage activity, token consumption, recipe interactions and technical records needed to operate, protect and analyze the service.
We use this data to authenticate and manage your account, save conversations and content, personalize cooking suggestions, generate recipes and images, operate shopping-list and community features, verify purchases and provide support. Usage data and technical records help analyze performance, manage limits and costs and prevent abuse.
We send account and security emails. If you opt into cooking or product-update emails, we use your email address and delivery preferences for those communications; you can change your preferences or unsubscribe.
We do not sell your personal data. Providers receiving data for service functions include OpenAI (AI processing), Vercel (hosting, analytics and Blob image storage), Supabase (database), Resend (email delivery), Stripe (web payments) and Google (sign-in and Google Play billing; website analytics services when enabled). Better Auth is the authentication software we use, not a separate provider hosting your data.
Our team may access information needed for support, report review and administration. New Discord feedback notifications only alert staff to review feedback in the authenticated console: they do not include your message, rating, email, user ID or context. Feedback submitted before this update may have been forwarded to the staff channel; contact support@mychefai.com to ask about or request removal of those copies.
If you publish recipes, comments, photos or profile details, other people can view that content. When you share content with another application, the recipient receives it at your direction. Do not put private or health information in content you do not want to make public.
The website uses Vercel Analytics and, when configured, Google Tag Manager for analytics tags, including Google Analytics, and may use Google advertising services. These website services may process browsing activity, browser or device information and cookies or other identifiers according to the enabled tags. This website analytics and advertising disclosure does not mean the native app includes an advertising SDK or accesses the Android advertising ID.
To answer your questions, we send relevant messages, conversation context and attached photos to OpenAI. Dietary preferences, allergies and health information you include can form part of that context. For recipe-image generation, we send recipe descriptions and details to OpenAI. Conversations and image references are stored in our database; uploaded photos and generated images are stored in Vercel Blob.
We do not use your conversations to train our own models. Each external provider's processing is also subject to its terms and policies; this statement is not a guarantee about all of those providers' uses or retention periods.
MyChefAI provides cooking ideas and dietary guidance, including diabetes-related suggestions. It is not a medical device and does not diagnose, treat, cure, or prevent any medical condition. Consult a qualified healthcare professional about your health or dietary needs before relying on these suggestions. Check ingredients for allergens and verify AI-generated nutrition estimates.
If you use YouTube recipe conversion when it is available, we send the supported video's YouTube URL to Apify to retrieve its title, description and other video metadata. When the description does not contain enough recipe information, we use Apify to obtain subtitles or, as a fallback, a transcript of the video's audio.
We send the available title, description and transcript, along with a language hint when available, to OpenAI to extract structured recipes, including ingredients, quantities and cooking steps.
If you use the public converter when it is available, we store recipe previews and their source details in browser-bound drafts, together with a hash of the browser token. Draft access expires 24 hours after creation. If you choose a recipe or save it, the draft can also store your selection, save request time, signed-in account ID and a record of the saved recipe to continue saving and prevent duplicate saves. New recipes saved from a preview are private and are stored separately in your collection. Draft expiry does not delete saved recipes.
To enforce usage limits and prevent abuse, we store keyed hashes (HMAC) of a browser identifier and IP address, along with usage counts and time windows. These usage records are marked to expire one day after the relevant limit resets. Cleanup removes expired drafts and usage records in batches; expiry does not mean immediate deletion.
The ChatGPT video preview tool, when available, returns a preview without creating one of these browser-bound drafts. Saving a recipe is a separate action.
For structured recipe saves, we retain a record containing your account ID, save key, a hash of the original content and the original recipe ID to prevent duplicate saves and retries restoring deleted recipes. This record contains no recipe ingredients, instructions or text. It remains after you delete the recipe and is removed when you delete your account.
Retrying the same save returns the current recipe while it remains available. If you deleted it, the retry fails and does not recreate it. Saving it again requires a new save request.
If you choose to connect MyChefAI to ChatGPT and approve account access, ChatGPT can use the permissions you grant to work with your MyChefAI recipe collection. We issue app authorization tokens for this connection so ChatGPT can make permitted requests. For connection authentication, MyChefAI may return your account ID, email address and email verification status to ChatGPT/OpenAI. An account lookup may return your account ID, name and email address so you can identify the connected account.
We receive the recipe content and search criteria that ChatGPT sends for your requests. Depending on the request, we return recipe previews, search results, saved recipes and save or update results to ChatGPT/OpenAI. These can include recipes you saved or bookmarked, including your private recipes; recipe names, descriptions, ingredients, quantities, instructions, servings, yield, cooking times, tags, source URLs, credits and adaptation notes; and the original text of older recipes.
Returned recipe information can also include recipe IDs and links, chef information, image URLs, dates when recipes were saved or bookmarked, version numbers, and publication and editing status. We use these fields to find, display, save and update the correct recipes.
If you separately authorize meal-plan or shopping access, available tools can receive and return your saved plan dates, meal slots, servings, notes, linked recipe summaries, shopping items, checked status and ingredient quantities. These records can include private notes, recipe names and source identifiers. Read permissions allow retrieval and previews; write permissions allow the requested additions, edits and removals. Recipe permissions do not automatically grant plan or shopping access, and these permissions do not publish your plans or lists.
Grocery previews use the stored recipes or saved plan you select. We check current source access before compiling or adding groceries. A grocery item already saved to your shopping list retains its saved ingredient and source-name snapshot until you edit or remove it, even if that recipe later becomes private or is deleted. Saving this snapshot does not grant access to new private recipe content.
To prevent duplicate plan and shopping changes, we retain account-linked mutation receipts containing the operation, request key, a hash of the request, the plan or list identifier, applied version and creation time. Receipts contain no recipe ingredients or plan notes. A retry returns the current authorized record, or fails if its original record is no longer available; it does not restore deleted entries. Receipts remain until account deletion.
Review the connected account and permissions before approving access. New recipes saved through this connection are private. Connecting does not publish your private recipes. With write access, the connection can update recipes you own in response to your requests.
To measure how the connection works, we store daily counts linked to your account, including the tool used, outcome and number of requests. These counters contain no conversations, recipe content or IDs, search terms, source URLs or tokens. We retain them while you keep your account and remove them when you delete your account. Administrative reports show aggregate totals and the number of accounts with current access through the connection.
You can disconnect MyChefAI through ChatGPT's connection settings. Signing out of the MyChefAI session used to authorize the connection, or that session expiring, also ends its access. Disconnecting does not delete recipes, plans or shopping lists stored in MyChefAI or itself remove information already included in ChatGPT conversations. Manage your recipes in MyChefAI and those conversation copies through ChatGPT's controls. OpenAI handles information it receives under its own terms, privacy policy and your ChatGPT data settings.
You can access and update your account details and change email preferences. You can request access, correction or deletion of your data by contacting support@mychefai.com. Applicable rights depend on where you live.
We keep account data and content to provide the described features while you maintain your account, until you remove that content or request deletion. You can delete your account from your Profile, or email support@mychefai.com from your account address with subject "Account Deletion Request".
Account deletion removes account and profile details, sessions, conversations, private recipes, saved meal plans, shopping lists, mutation receipts, your submitted community comments and photos, preferences and app feedback from our database. It also removes your stored images that are not referenced by surviving public or shared content.
Removing images from origin storage does not immediately remove copies already held in delivery caches. Those copies may remain available until the cache expires.
Published recipes may remain without attribution to your account, along with images still used by public or shared content. Removing attribution does not automatically remove personal information you wrote into the text or included in a photo. Review your public content before deleting your account and contact support to request removal of personal information in that content.
We retain usage and cost records without a link to the deleted account. We also retain Google Play purchase verification records: a billing-account identifier unlinked from your account, purchase and linked-purchase tokens, product and plan identifiers, subscription status and expiry, test indicators, verification timestamps and notification-processing records. These records support billing verification and prevent an existing purchase from being reassigned to another account; they currently have no fixed automatic-deletion period. Account deletion does not cancel a Google Play subscription: manage or cancel it in Google Play.
Payment providers and other recipients may retain records under their own policies and legal obligations. MyChefAI deletion does not automatically erase provider transaction records or copies other people have received or shared. For questions about data sent to providers, support correspondence or backups, contact support@mychefai.com.
See detailed account deletion instructionsWe apply reasonable security measures, including session protection and data safeguards.
We may update this policy from time to time. When we do, we update the "Last updated" date.
If you have questions, contact support@mychefai.com.
