Privacy policy
Updated 10 November 2026
Who we are
Mealwise is an app for logging what you eat and seeing its calories and nutrients. It is run by an individual developer in India under the name Mealwise, who decides how your data is used.
This policy covers the Mealwise Android app, trymealwise.app and the service behind them. Questions and requests: contact@trymealwise.app.
What we collect and why
- Your email address, to sign you in with a one-time code.
- Your profile: your name if you give one, birth year, height, weight, body fat if you add it, sex, pregnancy or breastfeeding, activity, goal, eating preferences, foods you avoid, meal times, language and time zone. We use it to set your targets and fit estimates to you.
- What you add: meals, meal photos, notes, water, weights, recipes, plans, reminders and your chats with Mealwise, plus the food facts Mealwise remembers, which you can see and edit.
- Photos of nutrition labels, barcodes, diet charts and recipes, when you add them.
- Weight from Health Connect, if you turn it on.
- Crash and error reports: app and Android version, phone model, the screen and the error. They never include your meals, messages or health numbers.
- Problem reports, when you send one from Profile → Report a problem: what you write, and any screenshot, video or PDF you choose. Sending also attaches the app and Android version, the phone model, a session id, and the recent trail of screens, actions and requests. The trail is names, status codes and timings, not a meal, a message or a health number. We use a report to look into the problem you reported, and the developer can read it.
- App usage, when this build can send it. During the beta it is always on. From launch, Profile → Privacy & data → Share app usage is on until you turn it off. While it is on, PostHog receives a hash of your account id, the name of each screen you open, and named actions such as a meal being logged or a purchase finishing. An action says what kind of thing happened, never the meal, the message, the photo or a health number. PostHog does not record the screen or collect taps on its own. Turning the switch off stops new events.
- Purchases, when they are turned on. Opening Plans sends your account id to RevenueCat, which handles the purchase through Google Play. RevenueCat receives the account id and the purchase: which product, and whether it is active. Google Play records the purchase against a hash of that account id. We use this to give you what you bought.
- A waitlist sign-up on our website: your email, when you joined, the invite tag and the site that sent you.
- Website analytics: PostHog counts page views, chapters you reach, Play-link clicks and waitlist sign-ups without cookies. Each page load gets a new anonymous label. We keep the page name with any campaign link details, the website that referred you (not its page), your browser, operating system and device type, and where on the page a click or sign-up happened. We drop your internet address, exact screen size and the full page address, and we don’t record what you type or your screen.
We use this to run Mealwise for you and understand visits to our website: to estimate, save and show your meals, keep your targets, answer in chat and fix problems. During the beta, and after it if you turn on Chat insights, we also use it to improve Mealwise as described below. We don’t sell it, show ads or build profiles for anyone else. Mealwise doesn’t ask for your contacts or location.
When you speak a meal, your phone turns it into text, and only the text reaches Mealwise. If your phone has no on-device speech, the app tells you that Android’s speech service may send the audio over the network.
AI and your photos
Mealwise uses AI to estimate meals, read labels and answer in chat. The AI runs on OpenAI’s GPT models, which also power ChatGPT. Your phone sends the data below to our servers in Mumbai, and those servers send it on to OpenAI. Each request asks OpenAI not to store it. If a request fails, our servers can try again through another OpenAI connection.
We send OpenAI:
- the meal photos you add, and photos of labels, diet charts and recipes;
- the meals you type or speak, as text, and your chat messages;
- what an answer needs from your account: your name if you gave one, age range, goal, targets, eating preferences, meal times, today’s and recent meals, today’s plan, your last few weights, saved foods and what Mealwise remembers.
Your email and account id are not sent. Before a photo leaves your phone, Mealwise makes it smaller and removes its location and camera details. Anything OpenAI keeps anyway follows its own terms and privacy policy (openai.com/policies).
If we change the AI provider, we update this policy and tell you in the app before the change applies.
Chat insights: each day our AI reads recent chat messages alongside your app activity, profile and earlier insights to find patterns, struggles, requests, confusion and missing features. The Mealwise team sees the AI’s notes and activity summaries, not your chats. During the beta it is on for everyone, as the next section says. From launch it is off unless you turn it on in Profile → Privacy & data. We keep the insights until you turn it off or delete your account; turning it off stops the analysis and deletes them. Your choice is saved with your account and included in your export.
During the beta
The beta is for testing. By joining it, you agree that our AI reads your chats each day for Chat insights and that the team receives app usage, so we can fix what is confusing or missing. Both stay on for everyone during the beta; to stop them, delete your account. Health Connect data is never used for either.
When Mealwise launches, Chat insights is off unless you turn it on, and insights from the beta are deleted unless you do. App usage then follows your Share app usage switch. Chats are kept for 30 days and app usage for up to 12 months. Your agreement, with its date and version, stays with your account until you delete it.
Where your data is
- Clerk (United States) handles sign-in and holds your email.
- MongoDB Atlas (India) is our database. It holds your records. Meal photos, and the screenshots, videos and PDFs attached to a problem report, are kept in a folder on our server in Mumbai. A photo saved in the database before that folder stays there until it is moved.
- When we keep meal photos in Cloudinary, they are kept there instead of that folder. Cloudinary receives the photo, filed under a hash of your account id, and only our servers can read it. Problem-report files stay in the folder either way.
- Oracle Cloud (Mumbai, India) runs our servers.
- AI requests are sent from our servers in Mumbai to OpenAI, and ask that service not to store them.
- Open Food Facts receives the barcodes and product names we look up, with nothing that identifies you.
- Google ML Kit reads barcodes on your phone, so the camera picture stays there. ML Kit sends Google its own usage details: the phone’s maker, model and Android version, the picture’s size and format, how long reading took and an id for this install of the app. Google uses them to check and improve ML Kit.
- Vercel hosts trymealwise.app.
- PostHog (European Union) is our analytics service. It counts visits to our website, and receives app-usage events when Share app usage is on.
- RevenueCat receives your account id and purchase information when purchases are turned on and you open Plans. Google Play takes the payment.
They process data only to provide their part of Mealwise. Some of them are outside India.
On your phone, Mealwise keeps your profile, today’s meals, unfinished drafts and changes waiting to upload, so it works offline. None of it goes into Android backups, and removing the app removes it.
Who can see your data
Only you, through your signed-in account. The server checks every request against the account that sent it, so no one else can read your records through the app.
The developer can reach the servers and database only to keep Mealwise running, fix a problem you report or meet a legal duty, and doesn’t look at your meals, photos or chats for any other reason. A problem report is part of that work: the words, the files you attached, the device and version, the session and the trail. We share data with authorities only when Indian law requires it.
How long we keep it
- Your account and records: until you delete them or your account.
- Chats: each day has its own chat, deleted after 30 days. Meals you saved from a chat stay.
- Chat insights: until you turn it off or delete your account.
- Photos: a photo you add but never use is deleted within a day, and one only in a chat goes with that chat. A photo used for an estimate, shown in a meal, or added as a label or barcode stays until you delete your account.
- Crash and error reports: 30 days. Request records with no content: 14 days.
- Problem reports and the files attached to them: until you delete your account. A file you upload and never attach is deleted within a day.
- Waitlist sign-ups: until you ask us to remove them.
- After an account is deleted, a record that the deletion happened, with nothing about you in it: one year.
- Deleted data can stay in our encrypted backups for up to 8 weeks.
Export and delete
Export: Profile → Privacy & data → Export your data gives you a ZIP of your records and photos.
Delete: Profile → Privacy & data → Delete account, or on the web at trymealwise.app/delete-account. You’re signed out everywhere, and the deletion happens after 30 days; until then you can cancel. Then we delete your sign-in and every record and photo from our servers, including a photo kept in the folder on our server or in Cloudinary. We also ask PostHog to delete your app-usage events and RevenueCat to delete your account id and purchases. Google Play keeps its own record of a purchase, under its own rules. Copies leave our backups within 8 weeks. A phone that stays offline keeps its local copy, including today’s meals and unsent changes, until it reconnects or you remove the app. What was already sent to OpenAI for an answer stays under its own rules.
You can also ask for deletion by emailing contact@trymealwise.app from your account’s address.
Health Connect
If you connect Health Connect, Mealwise can:
- read your weight, which is saved to your Mealwise account and, like weights you enter, can be sent to the AI as context;
- read today’s steps, shown on Trends and never sent to us;
- write the energy and nutrients of your saved meals, and the weights you log.
Sharing runs while Mealwise is open, and saved meal changes can also be shared in the background. You choose each permission and can turn them off in Mealwise or in Health Connect.
Data from Health Connect is used only for these features. It is never sold, used for ads, or used for credit, insurance or lending decisions, and no one reads it except to keep the service running or when the law requires. Mealwise’s use of Health Connect data follows the Health Connect Permissions policy, including its Limited Use requirements.
Children
Mealwise is for people 18 and older. We don’t knowingly collect data from anyone younger. If you think someone under 18 has an account, write to contact@trymealwise.app and we will delete it.
Security
Data travels over HTTPS. On your phone, your sign-in is encrypted with a key kept in Android’s keystore. Server logs hold error codes and timings, never your meals, messages, health numbers, email or account id. Only the developer can reach the servers and database, with keys. If a breach affects your data, we will tell you and the Data Protection Board of India as the law requires.
Your rights and grievances
Under Indian law you can:
- get a copy of your data (Export your data);
- correct it, in the app or by writing to us;
- delete it, which also withdraws your consent (Delete account);
- name someone to act for you if you die or can’t act yourself;
- raise a grievance with us, and then complain to the Data Protection Board of India.
Grievance officer: Mealwise, contact@trymealwise.app. We reply within 30 days.
Changes
When this policy changes, we update the date at the top. If a change affects how your data is used, we tell you in the app before it applies.