Last updated: July 23, 2026
The short version: your recipes are private by default, we collect only what the app needs to work, and we never sell your data or show ads.
Your account info (email, and the name/photo from Google if you sign in with it), the content you add (recipes, photos, plans, pantry items, notes, comments), a count of your AI uses (to enforce the daily allowance), and — if you subscribe to Pro — billing status. Card numbers go directly to Stripe; we never see or store them.
To run the app: store your library, build shopping lists, enforce AI quotas, show your public dishcoveries to others when you opt in, and manage your subscription. That's it. No ads, no selling your data, no tracking cookies — the only cookies are the ones that keep you signed in.
Nothing, until you say so. Recipes are private by default. If you mark a recipe or collection public and opt into public dishcovery, that recipe plus your display name, handle, bio, and avatar appear on public pages. Comments you post on public dishcoveries are visible to others. Your email is never shown publicly.
A few services make DishCovered work, each receiving only what it needs: Supabase (database, sign-in, and photo storage), Vercel (hosting), Anthropic (the AI that reads recipe text and photos during import — API data is not used to train their models), and Stripe (payments, if you subscribe).
Export your entire recipe library anytime from Profile. Want something corrected or your account and data deleted entirely? Message Ralph and it's done — no dark patterns, no retention tricks. We keep data only as long as you have an account.
If this policy changes in a meaningful way, we'll note it in the app. Questions: message Ralph, who built and runs DishCovered. See also the Terms of Service.
