Privacy
eeatly is your family's food memory, and you should know exactly how it's kept. This page is in plain English, not legal boilerplate. If something here is unclear, let us know through Help and we'll fix the wording.
What we collect
Only the things you put in:
- Your account info: email and the name you sign up with
- Meals you log: name, date, effort, notes
- Photos you upload (optional)
- Audio you record or upload for voice notes (see “AI processing” below)
- Which kitchen you belong to and who else is in it
- Recipes you save and any shareable links you create
Beyond what you log, we keep lightweight product analytics (which pages get visited and when people sign up) to understand how eeatly is used (see “Analytics & error tracking” below). We don't sell your data or track you across other sites.
Where your data lives
Your account, meals, recipes, and household info live in a managed Postgres database (Neon). Photos you upload live in object storage (Cloudflare R2). Payment info (only if you upgrade to a paid plan) is handled entirely by Stripe; we never see your card details.
Analytics & error tracking
We use two third-party services to understand usage and keep the app healthy:
- PostHog: product analytics for page visits and sign-ups, so we can see what's working. Anonymous visits are counted without a profile; a profile is only created once you sign in. We don't sell this data or use it to track you on other sites.
- Sentry: error monitoring. When something breaks, a diagnostic report (the error and a stack trace) is sent so we can fix it. We don't attach your personal data to these reports.
AI processing
When you use the AI suggest feature (to fill a meal from a photo, pasted text, or a voice note) your input is sent to an AI provider (OpenAI primary, Anthropic as a fallback) to extract the recipe. Two specifics worth being explicit about:
- Audio is not persisted on our servers. Voice notes are sent directly to the transcription provider, transcribed in-memory, and discarded. We never write the audio bytes to disk.
- Transcripts and AI outputs aren't persisted beyond what shows up in your meal record. The intermediate data the AI generates while extracting your recipe isn't stored separately.
- The AI providers process your input under their own terms. Anthropic and OpenAI don't train their public models on API-submitted data by default.
If you'd rather not send your data to a third-party AI provider, you can ignore the AI suggest feature entirely. Everything in eeatly works without it.
Shared kitchens
When you join a kitchen with family, members see each other's meals, recipes, and plans. Each cook's attribution is preserved (“Sara cooked this”) so you can tell whose recipe is whose.
If a member leaves the kitchen or deletes their account, the meals they logged stay with the household but their attribution becomes “Former member”: their name and email come off. The history doesn't disappear; the personal identifier does.
Recipe shares
When you create a public share link for a recipe, anyone with that link can view the recipe (no sign-in required). Share links are unlisted (they aren't indexed or made findable) but they're not secret either. You can revoke a share link at any time from the recipe's settings.
Deleting your account
You can delete your account from Settings. When you do:
- Your account info (name, email, profile) is removed.
- If you're the only member of your kitchen, the kitchen and all meals/recipes in it are removed too.
- If you're part of a shared kitchen, your meals stay with the household as described above; your name comes off, but the cooking history doesn't.
- Aggregated, deidentified analytics events stay so our totals don't suddenly look wrong, but they no longer reference you.
Deletion is immediate. We send a confirmation email so you have a record of the request.
Cookies
The session cookie that keeps you signed in after you click a magic link, plus a PostHog analytics cookie that counts visits. No ad cookies and no tracking pixels; we don't follow you around the web.
Feedback we receive
If you send feedback through the app, a small team reads it. We use it to fix things and improve the product, never publicly, and never attached to your name without asking.
Questions
For data requests, account questions, or anything else, send a message through the Feedback button in the app. If you're not signed in, get in touch from the Help page.