Consumer health data we collect, and how we use it
| Category | Purpose and how we use it |
|---|---|
| Body and health profile: birth year, sex, height, weight and weight history, activity level | To calculate safe calorie and nutrient targets and show your progress |
| Health goals: goal, target weight and pace | To set your targets and plan meals |
| Pregnancy or breastfeeding status, and an eating-disorder concern | To apply safety limits and switch to a supportive mode without calorie numbers |
| Allergies and dietary patterns (such as halal or kosher, which may reveal religious beliefs) | To filter foods and meal plans and warn you about allergens |
| Food and nutrition logs, meal and nutrition-label photos, recipes, meal plans and grocery lists | To keep your food diary, estimate nutrition, show summaries and plan meals |
| Check-ins and habits: mood, energy, hunger, sleep, optional tags and notes, water and other habits | To show trends and your weekly review; notes go to the coach only if you turn on note sharing |
| Coach conversations, memories and safety events (category and severity only) | To give you personal coaching when AI features are on, and to respond carefully to sensitive topics |
| Information we calculate from the above, such as targets, trends and weekly-review insights | To show them to you in the app |
We use consumer health data only to provide the BiteMilo features you ask for. We do not use it for advertising and we do not sell it.
Where we get it
- From you: what you enter, the photos you take, your messages to the coach, and the text your phone creates from your voice.
- From your device: settings such as language and time zone.
- From Apple or Google sign-in: your account ID, email address and, if you share it, your name.
BiteMilo also calculates some information, such as your targets and trends, from the data above.
Consumer health data we share
We do not share consumer health data with third parties. We disclose it only to processors that act on our behalf, and each receives only what it needs:
| Processor | Consumer health data it handles |
|---|---|
| Supabase (database, sign-in and photo storage) | All the categories above, stored for you |
| DigitalOcean (API servers) | All the categories above, while our servers process them |
| Anthropic (AI models, only when AI features are on) | Your messages, photos or voice text, and the relevant parts of your profile, goals and logs |
| RevenueCat (purchases) | No health data; only your subscription and purchase status |
| Google Firebase Cloud Messaging (push notifications) | The notifications sent to your device, such as meal and check-in reminders |
Third parties and affiliates we share it with
We do not sell consumer health data, and we do not share it with third parties other than the processors listed above: Supabase, DigitalOcean, Anthropic (only when AI features are on), RevenueCat and Google Firebase Cloud Messaging. Each acts on our instructions under its data processing terms. We have no affiliates.
Your rights and how to use them
- Access: you can ask whether we collect, share or sell your consumer health data, get a copy of it, and get the list of all processors we have disclosed it to. In the app, Me → Account → Export my data gives you a copy straight away.
- Delete: delete your account in the app (Me → Account → Delete account), or ask us by email. We also tell our processors to delete it.
- Withdraw consent: turn off Me → AI features to stop sending data to Anthropic, or delete your account to withdraw your consent to health-data processing.
To make a request, email privacy@bitemilo.com from the email address of your BiteMilo account, or use the in-app options above. We respond within 45 days. If we need more time, which the law allows once for another 45 days, we will tell you why.
Appeal: if we decline your request, you can appeal by replying “appeal” to our decision. We will decide within 45 days and explain our decision in writing. If we deny your appeal, you can contact the Washington State Attorney General at atg.wa.gov/file-complaint.
