Purpose of This Page
This page explains, in practical terms, how ChefAI uses the data involved in core app features. For broader privacy rights and legal disclosures, see the Privacy Policy.
Recipe Import Inputs
When you import a recipe, ChefAI may process the information you provide through the iOS share sheet, pasted text, manual entry, uploaded screenshots, photos, website URLs, social media URLs, captions, comments you paste, public metadata, YouTube links, and other recipe-related context. This can include links from Instagram, TikTok, Facebook, YouTube, Pinterest, Safari, recipe blogs, and other sources you choose to share.
How Import Data Is Used
- To identify the recipe title, source, creator or publisher, ingredients, quantities, directions, timing, servings, tags, and notes.
- To convert screenshots, pasted text, captions, and links into editable recipe cards.
- To suggest grocery list items and categories.
- To estimate calories, protein, carbohydrates, fat, and other nutrition details when available.
- To detect failed imports, troubleshoot errors, and improve reliability.
Saved Recipe Library
ChefAI stores saved recipes, edits, recipe photos, source links, cookbook assignments, favorites, privacy settings, grocery lists, checked items, and related account data so your recipe library works across sessions. If public recipe functionality is enabled, public/private settings determine how recipe content may be displayed or shared.
Supabase and Backend Storage
ChefAI uses Supabase-backed authentication, database, and storage infrastructure to keep account and recipe data available to the app. Backend records may include user identifiers, recipe records, cookbook records, favorite relationships, grocery list items, imported image references, subscription entitlement flags, timestamps, and settings needed to operate the service.
AI Processing
ChefAI may send relevant recipe import material to AI services through ChefAI backend infrastructure. This can include source text, links, screenshots, images, extracted text, user edits, and context needed to complete the requested feature. AI processing is used to parse, summarize, structure, categorize, estimate, or transform recipe information into app-friendly fields.
Analytics and Diagnostics
ChefAI may record app events such as onboarding completion, selected goals, recipe source selections, import start and completion, import errors, save actions, grocery list actions, cookbook actions, paywall or subscription events, and crash or diagnostic information. These events are used to improve reliability, user experience, and support.
Subscriptions and Apple Entitlements
If subscriptions are offered, purchases and payment details are handled by Apple. ChefAI may store or receive entitlement status, plan identifiers, renewal status, trial status, transaction identifiers, and related metadata needed to unlock paid features and provide support.
Data Not Intended for Advertising
ChefAI is designed around recipe organization, not advertising profiles. If ad networks, cross-app tracking, or materially different marketing tools are added later, this page and the Privacy Policy should be updated before those tools are used.
Retention and Deletion
Saved account and recipe data is retained while your account is active or as needed for app functionality, security, compliance, support, and backups. You can request deletion of account data by contacting ChefAI. Some logs, backups, transaction records, or abuse-prevention records may be retained for a limited period where necessary.
Where to Edit Later
Before launch, update this page with final analytics providers, AI providers, retention periods, subscription vendor details, and any public recipe indexing or sharing behavior.