Privacy Policy
Effective 25 September 2026 · support@trymorsel.app
Morsel is a food diary. This page says exactly what it stores about you, what leaves the service and where to, and how to take it all back. There are no advertisements in Morsel, no tracking across other apps or websites, and your data is never sold or shared for marketing. The one analytics tool we use is listed below, with exactly what it receives.
What we store
- Your account — email address, a hash of your password (never the password itself; accounts created with Google or Apple have none), and an optional display name.
- Your profile — the onboarding answers used to compute your nutrition targets: sex, date of birth, height, weight, activity level, goal, and (for a gain or loss goal) target weight and rate.
- Your food data — the meals you log, your recipes and boards, custom foods you create, corrections you make to catalogue foods, day completions, and per-food logging history that keeps your recents useful.
- Your photos — recipe and board images you upload, stored in our database. If you offer a custom food for the shared catalogue, its label and front-of-pack photos are stored with it and looked at by us before the food is accepted; an accepted food's name, nutrition and barcode become part of the catalogue every user searches, without your name or account attached.
- Your weight history — the weigh-ins you record, so progress can be shown over time.
- Your invite code — the referral code shown on your account and which accounts joined with it, so referral rewards can be counted.
- Sign-in records — active sessions with the device's browser string, so sign-out works and stale sessions expire.
Morsel uses a single essential cookie to keep you signed in. There are no advertising or analytics cookies.
What leaves the service, and to whom
| Recipient | What they receive |
|---|---|
| OpenAI | The link, caption text, or photos you submit when you import a recipe, sent so the recipe can be read and transcribed. When the words of a post are not enough, we fetch its public video and send OpenAI a handful of still frames and the soundtrack so a spoken or on-screen recipe can be read; the video itself is processed on our server and deleted straight after, never stored. Also the ingredient lines you ask Morsel to price when writing a recipe, and a photo of a nutrition label when you ask Morsel to read one. Nothing else from your account is included. Under OpenAI's API terms this content is not used to train their models. |
| USDA FoodData Central / Open Food Facts | The search terms and barcodes you look up — never your identity or account details. |
| Only if you sign in with Google: Google tells us your email, name and that the email is verified. We send Google nothing about your diary. | |
| Apple | Only if you sign in with Apple: Apple tells us your email (or a private relay address) and, once, your name. We send Apple nothing about your diary. |
| PostHog | Product analytics, hosted in the EU. Receives a numeric account id and the fact that a step happened — a wizard screen was reached, a meal was logged, a day was completed, a recipe was imported — plus your answer to "Where did you find Morsel?" and, if you subscribe, which plan, its price, currency and store country. It never receives your email address, your weight, your targets, or the name of any food or recipe. Off entirely unless the deployment configures a key. |
| RevenueCat | Only if you subscribe to Morsel Plus through the App Store: RevenueCat processes the purchase on our behalf and tells us whether your subscription is active. It receives a numeric account id and your App Store receipt, never your email address or your diary. |
| Resend | Delivers the emails we send you — the address verification and password reset links. Receives your email address and the message, and nothing else. |
| Hosting | The service runs on Railway with data in Neon (Postgres) behind Cloudflare, the weekly backup described below is held privately on GitHub, and pages load fonts from Google Fonts — infrastructure providers that process traffic and storage on our behalf. |
We require any service receiving your data to protect it at least as well as this policy does.
Nutrition numbers are estimates
Calorie and nutrient figures come from public food databases and, for imported recipes, from AI-assisted reading of the source you provide — imported recipes are labelled, including when they are an estimate. None of it is medical advice. Talk to a healthcare professional before making decisions about your health.
How long we keep it
Everything is kept until you delete it. Deleting a meal, recipe, food, or photo removes it; deleting your account removes everything at once from the live database. Our host keeps short-term operational snapshots, and we keep an encrypted weekly backup of the whole database for up to 90 days so the service can be restored after a failure; a deleted account can remain in those backups until they age out, and is never restored to the live service on its own.
Deleting your account
More → Account → Account data → Delete account removes your account and all of its data immediately. If you signed in with Apple, we also ask Apple to revoke the sign-in tokens. Deleting your account does not cancel an App Store subscription; cancel that in your App Store settings. You can also email support@trymorsel.app and we will do it for you.
Your rights
Wherever you live — and specifically under UK and EU data-protection law — you can ask for a copy of your data, ask us to correct it, or ask us to erase it. Email support@trymorsel.app; deletion you can also do yourself in the app.
Age
Morsel is for people aged 13 and over, and the sign-up flow enforces this.
Changes
If this policy changes in a way that matters, the effective date above changes with it and the app will say so.
Morsel · Terms of Service · Support