NutriLog AI: Privacy Policy
NutriLog AI ("the app", "we", "us") is a health, fitness, and nutrition tracking application. This policy explains what data we collect, how we use it, who we share it with, and the choices you have. It covers both the Android app and this website, nutrilogai.com. By using either you agree to this policy.
This website sets no cookies and runs no analytics. Visiting nutrilogai.com (including the calculators) creates no account, stores nothing on our servers about you, and places no cookie, tag or tracking pixel in your browser. The calculators run entirely in your browser: the height, weight and age you type are never sent anywhere and are gone when you close the tab.
One thing does happen, and it is the whole list. Our host (Vercel) processes the standard request data any web server sees (your IP address, the page requested, your browser's user agent) to serve the page, including its typefaces, and to protect the service from abuse. It is not linked to an account, because on this website there is no account.
Who we are
The controller of your personal data (the one who decides why and how it is used) is Logakrishnan N, sole proprietor, trading as NutriLog AI, 40, Union Bank Colony, 5th Street, New Vilangudi, Madurai, Tamil Nadu 625018, India. Contact: support@nutrilogai.com. We are a one-person business and have no data protection officer; the same address reaches the person responsible for this policy, and it is also our grievance officer for India (section 10a).
We have not appointed a representative in the European Union. We have not appointed a representative in the United Kingdom. The app is not currently offered on Google Play in the European Economic Area, the United Kingdom or Switzerland; if you use it there, these rights still apply to you and you can reach us at the address above.
1. Information we collect
- Account & identity. There are two ways to sign in, and we never ask for
or store a password for either.
- Google Sign-In. We receive your name, email address, profile photo and your Google account identifier, to create and secure your account.
- Email code. You give us your email address and we send a one-time code to it. We store the address on your account, and a hashed copy of the code with a short expiry so it can be checked once and cannot be reused; the code record deletes itself automatically when it expires. No profile photo and no Google identifier are involved on this path.
- Terms acceptance. When you accept the Terms of Service in the app we store which version you accepted and when, so we can tell which terms applied to you. It is included in your data export and deleted with your account.
- Profile & goals. Details you provide during onboarding (such as height, weight, age, sex, activity level, dietary preference, and fitness goals) used to compute your personalized nutrition targets. Your account also holds your time zone, taken from your phone on each request so your day starts and ends at your own midnight; it stays on your account whatever the Usage & Diagnostics setting, and is deleted with the account.
- Health & fitness logs. Data you enter or log in the app: meals and their nutrition (calories, macros, micros), water intake, body weight, workouts, and fasting sessions. Streaks and badges are recalculated from these logs rather than stored.
- Camera & food photos (optional). If you use photo meal scanning or the
barcode scanner, the app uses your camera. You can also pick an existing photo from your
gallery instead: the system picker returns only the single image you select, and the app
never reads the rest of your library. Either way the image is sent for AI analysis (section
4) and is not saved on our servers.
When a scan becomes a logged meal, the app keeps a copy of that photo on your phone only, in the app's own private storage, so you can look at the meal again and correct the estimate against the picture. A photo you picked from your gallery is copied there too. These copies never leave the device: they are not uploaded, not included in your data export, and not part of any backup. They are deleted when you delete the meal, when you sign out or delete your account, automatically after 90 days, and when you uninstall the app. - Health Connect data (optional). If you grant permission, the app reads fitness and health data from Android Health Connect (steps, active energy, exercise sessions, heart rate, resting heart rate, and sleep) to give you a fuller energy-balance picture. This access is read-only, requires your explicit on-device consent, and can be revoked at any time in Health Connect settings.
- Product analytics (App interactions). Which screens you open and which features you use: see section 5. No meal names, photos, weights or free text are included, and you can turn this off.
- Support requests and messages. If you contact us from inside the app (Profile > Help & support), we store the subject and the message you write, every later message you send on that request, and our replies, so the conversation survives closing the app and so whoever answers can see what you already told us. The app attaches six device facts to each request (app version, build number, Android version, device model, manufacturer, platform), because "which version are you on" is the first question any support answer depends on. Please do not put anything in a support message you would not want us to read: our staff can see it (section 8), and unlike your logs it is written to be read by a person.
- Food corrections you send. If you report a wrong entry in the food catalog, we store which food it was, the reason you picked and any note you add, against your account, so the entry can be checked and fixed. They are included in your data export and deleted with your account.
- Food searches that find nothing. When a food search returns almost no results we store the search text with a counter, so we know which foods to add to the catalog. These rows carry no user id and are not linked to your account. Successful searches are not stored.
- Purchase data. If you subscribe to Pro, Google Play processes the payment and gives us only a purchase token and your subscription status (which plan, whether it is active, and when the current period ends). We store both against your account for as long as the account exists, and delete them with it. We never receive or store your card or payment details. The purchase token is a credential against Google's billing API rather than a record of anything you did, so it is deliberately left out of your data export (see Your rights and choices): exporting it would hand out a working key to your subscription.
- Device & install identifiers. When your account is registered on a device we store an install ID (a random string this app generates for itself, not a hardware, advertising or Google identifier) together with your notification token and basic device facts (model, manufacturer, Android version, app version, language, time zone), plus the Play Store install referrer, which of our links or campaigns you installed the app from. Any advertising click identifier in that referrer is removed before it is stored. The install ID lets us tell one installation from another, so repeated failures from a single phone are recognised as one problem; the notification token is what Google's messaging service needs to deliver a reminder or a support reply to that phone. Both are stored against your account and are removed when you delete it. If you turn off Usage & Diagnostics, the device facts, the referrer and the Health Connect status are removed straight away. On app version 1.0.15 and later we keep only what delivering a notification needs (the install ID, the notification token, whether notifications are allowed and whether the token still works, the platform, and when the phone was last seen and its token last changed). The token is used for nothing but delivering the notifications you allowed on your phone; to stop those, turn notifications off for the app in Android settings. On earlier versions turning it off deletes the whole device record, notification token included, and the app registers nothing further, so notifications sent from our servers (such as a support reply) no longer reach that phone. If you then update to 1.0.15 or later, the app registers that phone again for notifications only (no device facts), and the app tells you so once; choose which notifications you get in Profile > Notification settings.
- Technical data. Standard request metadata (e.g. timestamps, and the app version making the request, so we answer it in a way that version understands) needed to operate and secure the service.
We do not collect your precise location, contacts, SMS, call logs, or audio. The app requests no microphone permission: voice logging is disabled in this release.
2. How we use your information
- Provide the core tracking features and calculate personalized calorie and macro targets.
- Generate AI-powered insights (e.g. meal estimates, weekly reviews, plateau and coaching suggestions).
- Maintain your account, subscription entitlement, streaks, and history across sessions.
- Understand which parts of the app are used and where people get stuck, so we can improve them (section 5), and decide which foods to add to the catalog.
- Keep the service secure, prevent abuse, and fix problems.
We do not use your data for advertising, we do not sell it, and we do not profile you for anyone else's purposes.
2a. Why we are allowed to use it (legal bases)
If you are in the European Economic Area, the United Kingdom or Switzerland, data protection law requires a legal basis for each use. These are ours:
| What we do | Legal basis |
|---|---|
| Create and secure your account, sign you in, store your logs, compute your targets, deliver the reminders you turn on, and provide Pro if you buy it | Performing our contract with you (GDPR Art. 6(1)(b)): the Terms you accept |
| Process your health information (weight, height, age, sex, goals, food, fasts, and Health Connect data if you connect it) | Your explicit consent (Art. 9(2)(a)), given separately when you accept the Terms, and for Health Connect also on your device |
| Send the inputs in section 4 to Google Gemini for AI features | Your consent (Art. 6(1)(a) and 9(2)(a)), given by turning on AI Data Sharing |
| Product analytics (section 5) and crash diagnostics (section 5a) | Your consent (Art. 6(1)(a)), given by turning on Usage & Diagnostics |
| Security, abuse prevention, rate limits, fixing faults, and keeping the record of staff access in section 8 | Our legitimate interest in running a safe and working service (Art. 6(1)(f)) |
| Answering support requests | Contract, and our legitimate interest in helping you |
| Keeping purchase and subscription records | Contract, and our legal obligations on tax and consumer records (Art. 6(1)(c)) |
| The weekly summary email | Our legitimate interest in showing you your own progress; you can stop it from the link in every email |
Where we rely on consent you can withdraw it at any time, without affecting what was done before. Because the app cannot work without processing your health information, withdrawing that consent means deleting your account (section 7); the optional uses each have their own switch and can be turned off on their own.
Automated decisions. Your calorie and macro targets are calculated automatically from what you enter. They are suggestions you can change at any time and have no legal or similarly significant effect on you, so they are not the kind of automated decision Art. 22 GDPR restricts.
3. How Health Connect data is used and handled
Health Connect data is used to display and compute your in-app health and fitness metrics (such as net calories, workouts, and sleep). We do not use Health Connect data for advertising or marketing, we do not sell it, and we do not share it with any third party for that third party's own purposes. It is transmitted over encrypted connections and stored only to power the features you use.
One exception you should know about. If you use the AI coach chat or meal suggestions, your daily summary is sent to Google's Gemini API so it can answer in context (section 4), and that summary includes your step count, which comes from Health Connect if you have connected it. Gemini processes it on our behalf to generate your response; it is not used for advertising and not sold. No other Health Connect metric is sent: sleep, heart rate, resting heart rate, active energy and imported workouts are never part of an AI request. Turning off AI Data Sharing (section 4) stops this entirely.
4. AI processing
To produce nutrition estimates and coaching insights, the app sends the relevant input to Google's Gemini API for processing. No name, email or account id is ever part of it. Depending on the feature, that is:
- Setting and refining your targets (when they are first set, whenever something they are calculated from changes (a weigh-in, a weight import, your goal, pace, activity level or body details) and when you ask the app to refine them with AI): weight, height, age, sex, goal (including the pace you chose), target weight, activity level, diet and fasting preference.
- Food estimates (typed, restaurant or photo): the meal description you type or the food photo, your cuisine preference and, if you have told the app you are vegetarian or vegan, that diet.
- The AI coach chat: the message you type, your goal, activity level, diet, cuisine preference, age and sex, your current calorie and macro targets, and your daily summary (today's calorie and nutrient totals, recent meals, weight, water and step count).
- Meal suggestions: your goal, activity level, diet, cuisine preference, age and sex, your current calorie and macro targets, and your daily summary (as for the coach chat).
- Weekly review: your week's average calories and macros against your target, how many days you logged and stayed on budget, and your weight change.
- Recovery tip: your goal, activity level, and calorie and protein targets.
- Plateau insight: your weekly weight trend, your current and suggested calorie target, the direction of your goal (losing, gaining or building muscle) and, when you are on track, roughly how many weeks you are from your target weight.
Where a feature above uses your cuisine preference and you skipped that question, we send Indian or international instead, judged from your time zone: the time zone itself is never sent.
This input is used to generate a response and is not used by us to identify you beyond your account. Food photos are sent for analysis and are not stored on our servers: a copy of a scanned photo is kept on your own phone only, and only once the scan is logged as a meal (see section 1). Do not submit information you consider sensitive that is unnecessary for logging a meal.
Your choice. You can switch this off at Profile > Privacy > AI Data Sharing. The switch is enforced on our servers, not just in the app: with it off, our API refuses every AI request, so nothing reaches Gemini even from an older or modified copy of the app. Manual logging, food search, barcode scanning and all tracking keep working; the AI features stop until you turn it back on.
5. Product analytics (App interactions)
We collect a small amount of first-party usage data to see which parts of the app work and where people get stuck:
- What we collect. Screen views (the screen's name only, never anything you typed or opened on it); when a session starts, how long it lasted and how many screens it covered; and a fixed set of feature-usage events: seeing the sign-in screen and whether you continued without an account; completing an onboarding step, finishing onboarding, and logging or skipping the first meal; logging a meal (only how it was logged: search, photo, barcode, etc.); seeing a scan's ingredient breakdown and correcting a scan (how many items, and by roughly what percentage you changed the total); saving a dish; adjusting a portion size (which measure, and by how much); opening the Pro screen, which button you tapped there, how you left it, restoring a purchase, and whether a subscription purchase completed (which plan, never any payment detail); opening a notification (which kind, and whether you tapped it or its button); whether the app asked you for a Play Store rating and how that ended; and which AI feature you used.
- What it cannot contain. Event names come from a fixed allowlist and every property must be a number, a boolean, or a short enum token. Our server rejects anything else before it is stored, so meal names, food text, photos, weights, email addresses and free text cannot be recorded here, not even by a modified copy of the app.
- How long we keep it. 90 days. Each event is deleted automatically by the database once it is that old, and all of your events are deleted immediately if you delete your account.
- Who sees it. Only us. There is no third-party analytics SDK and no advertising SDK in the app; these usage events go to our own API and nowhere else. Crash diagnostics are the one exception, and are described in section 5a.
- Your choice. Turn it off at Profile > Privacy > Usage & Diagnostics. With it off the app records and sends nothing, and our server independently discards any event that still arrives for your account.
5a. Crash diagnostics
When the app fails we collect a diagnostic report so the fault can be found and fixed. This is the only place a third-party SDK is involved, and it exists for a specific reason: a crash that kills the app outright leaves nothing running that could report it, so it has to be written to the device and sent on the next launch.
- What we collect. The error and its technical stack trace, the screen it happened on, your app version, your Android version and your device model. For failures inside the app's own code we also record a random install identifier (generated by the app, not a device or advertising ID) purely so repeated failures from one installation can be recognised as one problem rather than many.
- What it cannot contain. The same rule as everything else here: no meal names, food text, photos, voice notes, weights, messages or free text. A report has no field for them.
- Where it goes. Reports from the app's JavaScript layer go to our own API and are deleted after 30 days. Reports of a crash that terminates the app are handled by Firebase Crashlytics (Google), acting as our service provider under their data-processing terms.
- Signed out. A crash during sign-in or onboarding is reported without any account attached, because at that point there is none: it carries only the technical details above.
- Your choice. The same switch: Profile > Privacy > Usage & Diagnostics. Turning it off stops crash collection as well. A report already written to the device by an earlier crash may still be sent once on the next launch, because it exists before the app can read your preference.
- Before you answer. From app version 1.0.12, nothing goes to Crashlytics until you have answered the Usage & Diagnostics question. A crash before then stays on your phone: it is sent if you say yes and deleted if you say no. Versions 1.0.11 and earlier could send a report of a crash that happened before you answered; updating the app from Google Play closes that gap.
6. How we share information
We do not sell your personal data. We share data only with service providers that operate the app and this website on our behalf:
- Google (Gemini API): AI processing of the inputs described above, only while AI Data Sharing is on.
- Google Play Billing: subscription payments and lifecycle notifications.
- Firebase Crashlytics (Google): crash diagnostics as described in section 5a, only while Usage & Diagnostics is on.
- Cloud database hosting (MongoDB Atlas): secure storage of your account and logs.
- Hosting (Vercel): runs the API that receives and returns your app data, in the Mumbai region.
- Resend (email delivery, United States): sends the one-time sign-in code to your email address, and the weekly summary email if you have not turned it off. Resend receives your email address and the contents of those messages in order to deliver them. You can stop the weekly summary from the link in its footer; the sign-in code is only sent when you ask to sign in.
- Open Food Facts: when you scan a barcode, our server (not your device) looks the barcode up in the Open Food Facts product database to fetch the product's name and nutrition. We send only the barcode digits: no account id, no name, no email, no device identifier and no other data about you.
- Social features (optional): currently switched off. Friends and challenges are disabled in the released app, so nothing is shared with anyone today. If they are turned back on: other participants can see only derived, non-sensitive metrics you choose to share (such as your display name, photo, streak, and on-budget day count), and never your raw meals, weight, or health readings.
We may also disclose data if required by law or to protect the rights, safety, and security of our users and the service.
6a. Where your data is processed
We are based in India. Your account and logs are stored in MongoDB Atlas in Mumbai, India, and our API runs on Vercel in Mumbai. Some of the service providers above are in the United States or process data there: Google (Gemini, Play Billing, Firebase Crashlytics), Vercel and Resend.
India and the United States do not have an EU or UK adequacy decision covering all of this processing. When personal data of someone in the EEA, the UK or Switzerland goes to one of these providers, the transfer relies on the European Commission's Standard Contractual Clauses (and the UK Addendum or Swiss equivalent) in that provider's data processing terms, or, for providers certified to it, on the EU-US Data Privacy Framework and its UK and Swiss extensions. Each provider processes the data to provide its service to us. Vercel hosts our API on a plan that does not include a separate data processing agreement, so its standard terms of service apply. You can ask us for a copy of the relevant safeguards at the address in section 12.
7. Data retention and deletion
We keep your data for as long as your account exists. You can delete your account from within the app at any time, at Profile > Privacy > Delete Account & Data. Deletion is immediate and cannot be undone: it erases your profile, every log (meals, water, weight, workouts, steps, sleep, resting heart rate, fasting), your target history, your custom foods and recipes, food corrections you sent, your Terms acceptance record, your product-analytics events, and it removes you from any challenges and friend connections. Streaks and badges are recalculated from your logs rather than stored, so they go with them. Meal photos are held on your device rather than on our servers, so they are removed by the app itself: when the meal is deleted, when you sign out or delete your account, and automatically after 90 days. Full instructions: How to delete your account.
If you sign in but never finish setting up the app, add no meals or weigh-ins, and then do not sign in or change anything for 30 days, we delete that account and everything attached to it automatically, in the same way. If you told us your age when you signed in, we email you at least 7 days before this happens, and signing in again stops it. An account with a subscription purchase is never deleted this way.
Two kinds of record are detached from your account rather than erased, and we would
rather say so than let you discover it. A support conversation and a
subscription event (what Google Play told us about a purchase and what we did about it)
are both records of an exchange between two parties, and the half that is ours does not stop
existing because you closed your account: a refund or a chargeback can arrive after it. So on
deletion we detach your identity from both: the account id is removed, the email on a support
thread is replaced with [deleted], and any note we wrote by hand on a subscription
event is cleared. A support thread is then no longer linked to you.
A subscription event still carries its Google Play order id, because that is how
a later refund or chargeback is matched; through Google Play that id can be tied back to the
purchase, but it is no longer attached to any NutriLog AI account. Nothing in either record is
used to build a profile or contact you. Everything else listed above is deleted outright.
Three categories have their own limits regardless of your account: product-analytics events are deleted automatically 90 days after they are recorded; the device and install record described in section 1 (install ID, notification token, model, Android version, language, time zone) is deleted 120 days after that device was last seen; and the anonymous failed-search rows described in section 1 (which carry no user id and are therefore not linked to you) are deleted 180 days after the last time anyone searched for that text. Turning off Usage & Diagnostics removes the device facts from that record immediately rather than waiting for that limit. On app version 1.0.15 and later the install ID and notification token stay, for delivering notifications only, until the record's own limit or your account deletion; on earlier versions the whole record is deleted.
7a. Your rights and choices
- Get a copy of your data. In the app, Profile > Privacy > Download my data gives you a file with everything on your account: your profile and goals, every log, your target history, custom foods and recipes, support conversations, food corrections, your subscription status and your Terms acceptance. It is free on every plan and you can download it as often as you like. Download as a spreadsheet gives your meals or your weight history as a CSV. The file lists what it leaves out on purpose, and why: credentials (the purchase token from section 1, the identifier Google gives your account for sign-in, and any sign-in code that has not expired yet); the notes our staff keep about your account and the record of who accessed it, which you can ask us for; measurements taken when a feature failed; your phone's install ID and notification token and our record of whether notifications to it are allowed and still reachable, plus two internal markers (one that signs your sessions out, one that keeps our own test accounts out of our counts); and meal photos, which are on your phone rather than on our servers.
- Correct it. Your profile, goals and every log can be edited or deleted in the app. If something you cannot edit is wrong, write to us (section 12).
- Delete it. Delete your account and its data at any time (section 7).
- Change what you allowed. AI Data Sharing and Usage & Diagnostics can be turned off at any time in Profile > Privacy, Health Connect access in Android's Health Connect settings, and notifications in Android settings. Turning one off stops that use from then on.
- Object, restrict, and take it with you. You can object to any use we base on legitimate interest (section 2a), ask us to restrict a use while a question about it is settled, and receive your data in a portable format (the export above is JSON, the spreadsheet download is CSV).
- Withdraw consent. Any consent in section 2a can be withdrawn at any time, as described there.
- Ask us. For anything else about your data, including a request the app does not cover, write to the address in section 12. We answer within one month (we may extend that by two months for a complex request and will tell you if we do), and we do not charge for it. We may ask you to confirm the request comes from the account holder.
- Complain. If you are unhappy with how we handle your data, tell us first at the address in section 12. We acknowledge every complaint within 48 hours and tell you the outcome within 30 days. You also have the right to complain to a data protection authority: in the EEA, the authority in the country where you live or work; in the UK, the Information Commissioner's Office (ico.org.uk); in Switzerland, the Federal Data Protection and Information Commissioner (edoeb.admin.ch); in India, the Data Protection Board of India once it accepts complaints.
Revoking Health Connect permission stops further reads immediately. NutriLog AI only reads from Health Connect and never writes records into it.
8. Who can access your data
Besides you, a small number of our own staff can access your account data through an internal administration tool, in order to provide support, investigate a problem you have reported, or keep the service running. We want to be specific about what that means rather than leave you to assume it.
- What staff can see. Your name, email, subscription status, and the data you have logged: meals and nutrition, weight, water, workouts, steps, sleep, resting heart rate, fasting sessions, recipes, and the product-analytics events described in section 5.
- What staff can do. Correct your daily targets, reset your logged data at your request, suspend an account that is being misused, and delete an account. Only the most privileged staff role can delete an account or change a paid entitlement by hand.
- Support sessions ("impersonation"). To reproduce a problem you have reported, a senior member of staff can open a temporary session that shows them the app as you see it. Such a session lasts a maximum of ten minutes, requires a written reason, cannot be used to delete your account or change your subscription, and is recorded on your own sign-in history as well as in our internal log, so it is visible to anyone reviewing your account, not only to us.
- Everything is logged. Every administrative action on your account is recorded with who performed it, when, and why. Those records are kept so that access to your data remains reviewable, and they are retained even after an account is deleted.
- Sign-in locations. Your sign-in history shows the approximate network your
request came from, stored only as a shortened prefix (for example
203.0.x.x), never your full IP address.
We do not sell your data, and we do not give staff access to it for any purpose other than the ones above.
9. Security
Access to the app requires an authenticated session, data is transmitted over encrypted (HTTPS) connections, and Pro entitlement is verified server-side. Access to the internal administration tool is separate from your account, requires its own credentials, is limited by role, times out after a period of inactivity, and is logged as described in section 8. No system is perfectly secure, but we take reasonable measures to protect your information.
10. Children's privacy
You must be 18 or older to create a NutriLog AI account, and the app refuses a new account for a younger age. Accounts created before 18 October 2026 by people aged 13 to 17 keep working with a parent or guardian involved, and the app protects them: it will not plan weight loss for them, and fasts stop at 12 hours. We do not knowingly collect data from children under 13. If you believe a child under 13, or anyone under 18 who signed up after that date, has an account, write to us and we will delete it. An older version of the app could create a sign-in record before asking your age. If it then refused you as under 18, that record is deleted automatically 30 days after its last sign-in (see section 7), or straight away if you write to us.
10a. If you are in India
Under the Digital Personal Data Protection Act, 2023 we are the Data Fiduciary for your data. This policy is our notice. Section 1 says what we collect and section 2 why. Section 7a explains how to access, correct or erase your data and how to complain, and section 2a how to withdraw consent. Our grievance officer is Logakrishnan N, at support@nutrilogai.com; we acknowledge a grievance within 48 hours and resolve it within 30 days, and never later than the 90 days the DPDP Rules allow. A copy of this notice in any language listed in the Eighth Schedule to the Constitution can be requested at the same address.
10b. If you are in the United States
Some US states give extra rights over health data that is not covered by HIPAA (NutriLog AI is not a healthcare provider and HIPAA does not apply to it). Our Consumer Health Data Privacy Policy explains, for residents of Washington, Nevada and similar states, what consumer health data we collect, why, who receives it, and how to exercise your rights.
11. Changes to this policy
We may update this policy from time to time. Material changes will be reflected by a new effective date at the top of this page.
12. Contact
Questions or requests about your data: support@nutrilogai.com, or by post to Logakrishnan N, 40, Union Bank Colony, 5th Street, New Vilangudi, Madurai, Tamil Nadu 625018, India. Post is accepted for formal requests and is read, but email is much faster.