Privacy policy
The short version. We collect what we need to estimate your meals and set your targets. Your body stats, health conditions and meals are never shared with advertisers and never sold. Ads are shown to keep the app free, and where the law requires it you choose whether those ads are personalised.
Who we are
MacroLime (“we”, “us”) is an app run by Aditya Pratap Singh Bisht, an individual developer based in India, who is the data controller for the personal data described here. Contact us at hello@macrolime.com about anything in this policy.
This policy covers the MacroLime apps for Android and iOS and this website.
What we collect
| Data | Examples | Why |
|---|---|---|
| Account | Email address, sign-in provider (Apple, Google or email), a user ID | To create and secure your account |
| Body and goal profile | Sex, age, height, weight, body type, goal, gym days per week, diet preference, units | To calculate your calorie and macro targets |
| Health conditions (optional) | Diabetes, PCOS, high blood pressure, thyroid, high cholesterol, lactose intolerance | To adjust targets and food suggestions. Only collected after a separate consent, and you can skip it |
| Meal logs | What you typed or said, meal photos, the estimated foods, calories and macros | To estimate your meals, show your day and suggest what to eat next |
| Usage counters | How many meals you logged today and how many were unlocked | To run the free log, daily limits and ad unlocks |
| Advertising data | Device advertising ID (if you allow it), IP address, approximate location, ad views and taps | Collected by Google AdMob to show and measure ads (see “Ads” below) |
| Technical data | Error logs, app version, device type | To keep the service running and fix problems |
Voice logging uses your phone's built-in speech recognition (Apple or Google). Where your phone supports it, this happens on the device. We receive only the resulting text, never the audio.
How meal estimates work
When you log a meal, our server sends the meal text or photo to an AI model, currently Google's Gemini, along with a region code (for example “IN”) so it understands local food. We do not send your name, email, body stats or health conditions to the AI. The AI returns the estimate and we store it in your account.
Meal photos are stored only to produce the estimate and are deleted after about 30 days. They are not used for anything else.
Ads
MacroLime is free because of ads served by Google AdMob. AdMob may collect device identifiers, IP address and ad interaction data as described in how Google uses information from sites or apps that use its services.
- Health data is never shared with AdMob or any other ad network. Ads are never targeted based on your meals, body or health.
- In the EEA, UK and Switzerland, we ask for your consent through Google's consent form before personalised ads are shown. If you decline, you still see ads, but they are not personalised.
- In US states with privacy laws, you can opt out of the “sale” or “sharing” of personal information for targeted advertising in the app's privacy settings.
- On iPhone, we only use your advertising identifier if you allow tracking when Apple asks.
When you watch a rewarded ad to unlock a meal, Google tells our server that the ad was completed. That message contains a random ID and no personal details.
Who we share data with
We don't sell your personal data. We share it only with service providers that help run MacroLime:
- Google Firebase (authentication, database, file storage, servers), with data stored in the United States.
- Google Gemini API (meal estimates, as described above).
- Google AdMob (ads, as described above).
- Apple and Google when you choose to sign in with them.
We may also disclose data if the law requires it, or to protect the rights and safety of our users.
Consumer health data
Some of what you give us is health data under laws such as Washington's My Health My Data Act, Nevada SB 370, the GDPR and India's Digital Personal Data Protection Act. That includes body stats, weight, health conditions and meal logs.
- What we collect and why: listed in the table above. We use it only to provide the app's features: targets, meal estimates and food suggestions.
- Sources: you, directly in the app.
- Who receives it: Google Firebase stores it for us. Meal text and photos go to the AI model, with no profile or condition data attached. Nobody else.
- We never sell health data and never share it with advertisers.
- Your rights: you can access, delete and withdraw consent for your health data at any time by emailing us or using the app's settings. Washington residents can appeal a refusal by replying to our decision, and can contact the Washington Attorney General if the appeal is denied.
How long we keep data
- Account, profile and meal logs: until you delete your account.
- Meal photos: about 30 days.
- Daily usage counters and ad-reward records: up to 90 days.
- After you delete your account, we delete your data within 30 days, except where the law requires us to keep it.
Your rights
Depending on where you live, you can ask us to access, correct, export or delete your data, restrict or object to its use, and withdraw consent at any time. You can change your ad consent choice in the app's privacy settings. To make any other request, email hello@macrolime.com from the address on your account. We answer within 30 days.
If you are in the EEA or UK, you can also complain to your local data protection authority. In India, you can raise a grievance with us first, and then with the Data Protection Board of India.
To delete your account, see how to delete your account.
Security
Data is encrypted in transit and at rest by Google Cloud. Access rules stop one user's data being read by another, and the AI key never leaves our servers. No system is perfectly secure, but we will tell you and the relevant authorities promptly if a breach affects your data.
Age
MacroLime is for people aged 18 and over. We don't knowingly collect data from anyone younger. If you believe a minor has created an account, email us and we will delete it.
International transfers
Our service providers store and process data in the United States and other countries. Where data leaves the EEA or UK, Google provides safeguards such as the EU Standard Contractual Clauses.
Changes
If we change this policy, we will update the date at the top. For significant changes we will also tell you in the app.