Privacy Policy

Summarize with: ChatGPT Claude AI Mode Perplexity

Effective date: 16 September 2026

This policy explains what NutriScan collects, why, what we do with it, who else touches it, and what you can ask us to do about it. It covers the NutriScan mobile apps for iOS and Android and the website at nutriscan.app.

Privacy Policy in Other Languages

• 🇺🇸 English (Current): Privacy Policy | Terms of Use
• 🇮🇳 हिन्दी (Hindi): गोपनीयता नीति | उपयोग की शर्तें
• 🇪🇸 Español (Spanish): Política de Privacidad | Términos de Uso
• 🇫🇷 Français (French): Politique de Confidentialité | Conditions d'Utilisation
• 🇩🇪 Deutsch (German): Datenschutzerklärung | Nutzungsbedingungen
• 🇻🇳 Tiếng Việt (Vietnamese): Chính sách quyền riêng tư | Điều khoản sử dụng
• 🇮🇹 Italiano (Italian): Informativa sulla privacy | Termini di utilizzo
• 🇷🇺 Русский (Russian): Политика конфиденциальности | Условия использования
• 🇸🇪 Svenska (Swedish): Integritetspolicy | Användarvillkor
• 🇵🇱 Polski (Polish): Polityka prywatności | Warunki korzystania
• 🇧🇷 Português (Brasil) (Brazilian Portuguese): Política de Privacidade | Termos de Uso
• 🇯🇵 日本語 (Japanese): プライバシーポリシー | 利用規約

Who we are

NutriScan is a product of Fizday Tech (OPC) Private Limited, a One Person Company registered in India.

• Corporate Identity Number: U62091KA2024OPC186351
• GSTIN: 29AAFCF8616H1ZC
• Registered office: #14, 1st Cross Road, 1st Main, 7th Block, Koramangala, Bengaluru, Karnataka 560095, India
• Email: [email protected]
• In the app: Profile, then Contact Us

Fizday Tech (OPC) Private Limited is the controller of the personal data described here. For India's Digital Personal Data Protection Act 2023 we are the Data Fiduciary.

Scope and languages

This policy applies to the NutriScan iOS app, the NutriScan Android app, the website at nutriscan.app, the emails we send you and the push notifications we send you.

The policy is published in English, Hindi, Spanish, French, German, Vietnamese, Italian, Russian, Swedish, Polish, Brazilian Portuguese and Japanese. All versions describe the same processing. Where a translation and the English text disagree, the English text governs, except where your local consumer or data protection law requires otherwise.

Summary

This table is a short version of the sections below. The sections are the full statement.

Category	Examples	Why we use it	Legal basis (EEA and UK)	How long	Who else sees it
Account	Email, phone number, Google or Apple sign-in identity, user id	Create and secure your account	Contract	Until you delete it or your account, and then from backups on rotation	Supabase, Firebase, Google, Apple, Authkey.io
Profile and goals	Name, age, gender, height, weight, activity level, health goal, food preferences, allergies	Personalise targets, plans and suggestions	Contract, and explicit consent for health details	Until you delete it or your account, and then from backups on rotation	Supabase, RevenueCat, AI vendors
Meals and photos	Meal photos, food descriptions, portions, nutrition results, timestamps	Analyse meals and keep your diary	Contract	Until you delete it or your account, and then from backups on rotation	Cloudflare R2, Supabase, AI vendors
Medical reports	Lab report PDFs and images you upload	Generate a diet plan you asked for	Explicit consent	Until you delete it or your account, and then from backups on rotation	Cloudflare R2, Supabase, AI vendors
Voice	Microphone audio while you talk to the assistant, and the transcript	Run the voice assistant	Explicit consent	Kept no longer than needed to run the feature and for the provider's service terms	ElevenLabs, our backend on Google Cloud
AI chat	Your questions, the conversation, your profile context, attached documents	Answer your questions	Contract, and explicit consent where health data is included	Until you delete it or your account, and then from backups on rotation	Google Cloud, the model vendor in use
Health platform data	Apple Health and Health Connect readings, glucose readings, daily vitals summaries	Show your numbers next to your food	Explicit consent	Until you delete it or your account, and then from backups on rotation	Supabase, Firebase Storage
Location	Latitude and longitude, resolved city	Meal location insights, regional suggestions	Consent	Stored on your profile until you delete it or your account, and then from backups on rotation	Supabase, PostHog, platform geocoder, Google Maps
Device and usage	Device model, operating system, app version, a stable device identifier, push token, in-app events	Run the app, prevent referral fraud, fix faults, understand use	Legitimate interests	Until you delete it or your account, and then from backups on rotation	PostHog, Firebase, Supabase, Shorebird
Community	Posts, shared meal photos, comments, reactions, reports	Run the community features you opt into	Contract	Until you delete the post or your account, and then from backups on rotation	Supabase, other users by design
Subscription and payment	Purchase receipts, plan state, name, contact, age, city held as subscriber attributes	Give you what you paid for, prevent fraud, meet tax rules	Contract, legal obligation	Until you delete your account, and tax records for as long as Indian tax law requires	RevenueCat, Apple, Google, Stripe, Meta
Referral	Referral code, referred accounts, stable device identifier	Pay out referral rewards and block abuse	Contract, legitimate interests	Until you delete your account, and then from backups on rotation	Supabase, Cloudflare
Website	Page views with consent, questionnaire answers in your browser, demo tool uploads, IP address at the edge	Run the site, answer the demo, measure the site	Consent for analytics, legitimate interests for security and delivery	Analytics per Google Analytics settings, function logs per Netlify's retention	Google, Netlify, Cloudflare
Email and notifications	Email address, send, open, click and bounce events, segment name, push token	Send what you asked for, and our own messages	Consent, or legitimate interests where the law allows	Email event rows on Cloudflare Analytics Engine for 90 days; suppression records kept so we do not mail you again	Cloudflare, AutoSend, Supabase, Firebase, Notion

Data we collect

Account

When you create an account we collect your email address, or your phone number if you sign in with a one-time password, or your Google or Apple sign-in identity. We create a user id for you. Sign-in runs on Firebase Authentication. One-time passwords for Indian mobile numbers are delivered by Authkey.io.

The app also asks Firebase App Check for a device attestation token, through Apple DeviceCheck on iOS and Play Integrity on Android, so our backend can tell a real app install from a scripted one.

Profile, goals and health details

You tell us your name, age, gender, height, weight, activity level, food preferences, allergies and a health goal. Health goals include options such as diabetes, PCOS, pregnancy and recovery. Those answers are health data. In the EEA and UK they are special category data under Article 9 of the GDPR, and we process them on your explicit consent, which you give by entering them and can withdraw by removing them or deleting your account.

Meals and photos

When you scan a meal, the photo is uploaded to Cloudflare R2 storage and our backend is given a pointer to it. If that upload fails, the photo is sent inline instead. Alongside the photo we send your user id, your city and coordinates, your food preferences, your health goal and your subscription state, so the result matches you. The nutrition result, the portion, the time and any notes are stored in your diary on Supabase. Profile photos take the same route.

Medical reports

If you attach a lab report, we upload the PDF or image to Cloudflare R2, record it against your account, and pass its contents into diet plan generation. This is health data, and we process it on your explicit consent. You do not have to upload anything to use NutriScan.

Voice

The voice assistant records microphone audio while you are speaking to it. Audio is streamed over a secure connection to our backend and to ElevenLabs, which runs the conversational model and the speech to text. The assistant has tools that can read and write your meals, weight, diet plan, fasting state and support messages on your instruction. On iOS the app also asks for speech recognition access, and uses a local network and Bonjour connection to carry the real-time voice session.

Audio and transcripts are processed by us and by ElevenLabs to run the feature and are kept no longer than needed for that purpose and for the provider's service terms.

AI chat

When you ask the assistant a question, we send the question, the recent conversation, your name, user id, city, food preferences, health goal, timezone, whether you have connected a health platform, any document you attached, and your stored health readings where they are relevant to the answer. This goes to our chat backend on Google Cloud Run and from there to a model vendor.

Health platforms: Apple Health and Health Connect

If you turn health features on, NutriScan asks for access to Apple Health on iOS or Health Connect on Android. We ask for consent in the app before the platform permission dialog appears, and you can change or revoke it at any time in your phone's Health settings.

Read today: steps, active energy burned, total energy burned, distance walked and run, exercise time, workouts, sleep stages, heart rate, resting heart rate, heart rate variability, weight, height, body fat, nutrition and hydration.

Written today: weight, water and meal nutrition, which on iOS covers energy, macronutrients, fats, minerals and vitamins as separate nutrient types, and on Android is written as nutrition records.

Coming with the health monitoring feature: blood glucose is read and written. Heart rate, resting heart rate, heart rate variability, blood oxygen, respiratory rate and body temperature are read only.

What we do with it:

• We use it to show your own data back to you and to put it next to what you ate. Nothing more.
• Blood glucose readings are stored as individual rows in your NutriScan account, so they follow you across devices.
• Wearable vitals are stored as a daily summary per metric. Raw samples stay on your phone and are not uploaded.
• Today, a summary of your steps, active energy and sleep for the last 90 days is also written to Firebase Storage under your user id, and platform readings are stored in our Supabase health tables. Our chat backend reads those readings when it answers a health question you asked.
• Health platform data is never used for advertising, never sold, and never shared with any third party except the providers that host it for us. It is not stored in iCloud.
• Analytics events about health features carry counts and flags only. They never carry a glucose value or a heart rate.

Nothing NutriScan shows you is a diagnosis. Target ranges are informational and follow published guidance from bodies such as the American Diabetes Association and the NHS. Talk to your doctor about your own targets.

Location

With your permission the app reads your latitude and longitude. We use it for meal location insights, for regional food suggestions, and in India as part of sign-in. The coordinates are resolved to a place name by the platform geocoder, which is Google on Android and Apple on iOS, stored on your profile, sent with each meal scan, and sent to our product analytics with a location event. The insights map is drawn with Google Maps.

We use your location only while the app is in use.

Device and usage

We collect your device model, operating system version and app version. We collect a stable device identifier that survives reinstalling the app. On Android this is the Android ID and on iOS a value we keep in the Keychain. We use it to stop one person claiming referral rewards over and over from the same phone.

We also collect in-app events through PostHog, which we run on our own server, and through PostHog's hosted service. Events carry your user id, your food preference and your meal count, and the location event described above carries coordinates. Crash reports go to Firebase Crashlytics. App configuration is fetched from Firebase Remote Config and from a Cloudflare Worker. App updates and patches are checked with Shorebird.

Android declares a foreground service so the fasting timer keeps running.

Community

If you post to the community, share a meal to the public gallery, react or comment, that content and the meal photo attached to it are visible to other users by design. Reports you file about other posts are stored with your user id.

Subscription and payment

Purchases made in the iOS or Android app run through Apple and Google. Purchases made on nutriscan.app are sold by us and paid through Stripe, which handles your card details, your name and billing address (required for a cross-border payment to an Indian company) and the payment itself. We do not see your card number.

Subscription state is managed by RevenueCat. RevenueCat holds your purchase receipts and also holds, as subscriber attributes, your full name, your phone number or email, your age and your city. RevenueCat sends purchase events onward to Meta for ad measurement, described under Ads measurement below.

Plans are Free and Premium.

Referral

Referral links run through refer.nutriscan.app, a redirect we operate on Cloudflare. We record which account referred which, and we check the stable device identifier and push token to stop the same device claiming a reward twice.

Website

• Analytics. Google Analytics 4 loads only after you accept cookies in the banner. Consent Mode is set to denied by default.
• Google Fonts. The site loads a font stylesheet from fonts.googleapis.com and font files from fonts.gstatic.com on every page, before the consent banner is answered. Your IP address and browser details reach Google in that request.
• Questionnaire. The onboarding questionnaire on the website asks for your goal, gender, height, weight, age, diet, sleep, exercise and how you feel after meals. Those answers are written to your browser's local storage on your own device. They are not sent to our servers. Only step events, with no health values in them, go to Google Analytics, and only after you accept cookies.
• Demo tool. The food demo tool sends the photo or text you submit to a function on Netlify, which forwards it to Google Gemini and returns the answer. The function reads your IP address from the request headers and resolves it to an approximate location, which is included in the prompt so the answer suits your region. The function writes the text you submitted and the suggestions it generated to Netlify's function logs. Function logs are retained under Netlify's standard retention.
• Other browser storage. The calculators, the demo tool's scan counter, the exit-intent message and scroll position are all kept in your browser's local or session storage on your device.
• Edge delivery, caching and media are served by Cloudflare and Netlify, which see your IP address as part of delivering the page.

The Cookies Policy lists every cookie and storage key.

Email and notifications

We collect your email address, whether a message was delivered, opened, clicked, bounced or reported as spam, the campaign, the audience segment the message was sent to, your language, your timezone and the class of mail app or browser you used. Our click and open tracker stores a short hash of your email rather than the address, along with up to 200 characters of your raw user agent string, in Cloudflare Workers Analytics Engine for 90 days. Delivery events from AutoSend are written to our Supabase email tables. Push tokens are held in Firebase Cloud Messaging and in our database, and a token we cannot reach for 30 days is dropped.

The welcome message you get on signup contains an open pixel and a tracked link. It is sent to every new account using your first name, your language and your health goal.

Why we use your data and our legal bases

For readers in the EEA and UK, these are our Article 6 bases, and Article 9 conditions where health data is involved.

Purpose	What it covers	Legal basis
Run the service	Accounts, meal analysis, diary, diet plans, targets, community, subscriptions	Contract, Article 6(1)(b)
Health personalisation	Health goals, medical reports, health platform readings, glucose and vitals	Explicit consent, Article 6(1)(a) and Article 9(2)(a)
Voice assistant	Recording and processing your speech	Explicit consent, Article 6(1)(a)
Location features	Meal location insights, regional suggestions, India sign-in	Consent, Article 6(1)(a)
Product analytics and improvement	Feature use, funnels, faults, crash reports, churn and subscription analysis on individual records	Legitimate interests, Article 6(1)(f)
Security and fraud prevention	Device attestation, referral abuse checks, abuse of the community	Legitimate interests, Article 6(1)(f)
Our own email and push messages	Tips, product news, streak and habit prompts, digests	Legitimate interests for existing customers, Article 6(1)(f), with the soft opt-in under PECR; consent where your local law requires it
Health-based email and push segmentation	Choosing who gets a message based on a health goal such as PCOS, pregnancy, diabetes or recovery	Explicit consent, Article 9(2)(a)
Ad measurement	Sending purchase events to Meta so we can tell which ads worked	Legitimate interests, Article 6(1)(f), and consent where required
Legal and tax	Invoices, tax records, answering lawful requests, enforcing our terms	Legal obligation, Article 6(1)(c), and legitimate interests

On health-based email segmentation. We sometimes choose who receives a message using the health goal on your profile. That is a use of health data for direct marketing, and it needs your explicit consent. You can withdraw it by unsubscribing from any message, by turning marketing messages off in Profile settings, or by writing to [email protected]. Withdrawing stops the segmentation and stops the messages.

We do not make decisions about you that produce legal effects or something similarly significant, by automated means alone.

Who we share your data with

We do not sell your personal data. The section on California below explains the separate CPRA meaning of "share".

Provider	What they do for us	What they receive	Where they process it
Supabase	Main database, authentication and storage for app data, including the health tables	Almost everything in your account	United States and other regions Supabase operates
Google (Firebase)	Sign-in, push messaging, crash reports, remote configuration, app attestation, and a health summary file in Firebase Storage	Identity, device, crash data, push token, health summary	United States
Google Cloud (Run and Functions)	Our meal scan backend, chat backend, notification scheduler and account management endpoint	Scan and chat payloads, user id, profile context	United States
Google (Gemini)	Answers for the website demo tool, and app AI where it is the selected vendor	Food photo or text, approximate location, prompt context	United States
OpenAI, including through Azure	App AI where it is the selected vendor	Prompt context described under AI disclosures	United States
ElevenLabs	Voice assistant conversation and speech to text	Live microphone audio, transcript, tool results	United States
Cloudflare	R2 storage for meal photos, profile photos and medical reports; Workers for configuration, media, referral redirects, email sending and email tracking	Photos, reports, request metadata, email hash and event data	Global edge network
Netlify	Website hosting and the demo tool function	Website requests, demo tool input, IP address	United States
RevenueCat	Subscription state and entitlements	Receipts, plus name, contact, age and city as subscriber attributes	United States
Stripe	Payment processing and billing portal for purchases made on nutriscan.app	Name, billing address, email, payment details, invoice history	United States, Ireland and India
Apple and Google Play	In-app purchases, subscriptions and refunds	Purchase and account data held by the store	Global
Meta	Ad measurement through the in-app SDK and the server-side Conversions API	App events, advertising identifier, IP address, hashed email, hashed user id, purchase value and currency	United States
PostHog	Product analytics, on our own server and on PostHog's hosted service	Events, user id, food preference, meal count, location event	Our own server, and PostHog's infrastructure
AutoSend	Email delivery events	Email address and event type	United States
Notion	Holds the audience segments we build for push notifications, and support feedback records	Segment definitions, feedback text with your name and contact	United States
Authkey.io	One-time password delivery for Indian mobile sign-in	Phone number	India
Typesense on rented servers	Food search index	Search queries	Germany and other data centre locations of our hosting providers
Shorebird	App update and patch delivery	Install and patch check-in	United States
Google Maps and the platform geocoder	Map tiles and turning coordinates into a place name	Coordinates, map requests	United States
Google Translate	Translating food names	Food names you typed or scanned	United States
Google Fonts	Website typography	IP address and browser details of website visitors	United States
Google Analytics	Website analytics after you consent	Page views, session data, consented identifiers	United States

We may also disclose data to comply with the law, to respond to a lawful request, to enforce our terms, or to protect people from harm. If the business is sold or merged, your data moves with it and we will tell you.

Anything you choose to post publicly in the community or the gallery is visible to other users by design.

International transfers

We are established in India. Most of the providers above process data in the United States, and some elsewhere. India is not the subject of a European Commission adequacy decision.

For transfers of personal data out of the EEA we rely on the European Commission's 2021 Standard Contractual Clauses, and for transfers out of the United Kingdom on the UK International Data Transfer Addendum, in our contracts with providers whose terms offer them. Where a provider does not offer them, we rely on your explicit consent to the transfer or on the transfer being necessary for our contract with you. Providers processing in the United States include Supabase, Google, Cloudflare, Netlify, RevenueCat, Stripe, Meta, PostHog, AutoSend, Notion, ElevenLabs, OpenAI and Shorebird.

You can ask us for a copy of the transfer terms we rely on for a particular provider by writing to [email protected].

How long we keep data

We keep what is in your account for as long as your account exists.

• Your account content, which is your profile, meals, photos, medical reports, health readings, chats and community posts: until you delete it or your account, and then from backups on rotation.
• Email open and click events: 90 days in Cloudflare Workers Analytics Engine, then removed automatically.
• Suppression records for bounces and complaints: kept indefinitely, because that is what stops us mailing an address that should not be mailed.
• Push tokens: dropped after 30 days without a successful delivery.
• Website function logs holding demo tool input: retained under Netlify's standard retention.
• Tax and transaction records: for as long as Indian tax law requires.
• Voice audio and transcripts: kept no longer than needed to run the feature and for the provider's service terms.

Security

What we actually do:

• All traffic between the app, the website and our services runs over TLS.
• Data is held with providers that encrypt it at rest, including Supabase, Firebase and Cloudflare R2.
• Database access is role-based, with row-level security policies so one account cannot read another's rows.
• Secrets and API keys are held in provider secret stores, not in the app.
• App requests are checked with Firebase App Check before our backend trusts them.
• If a breach happens, we investigate it, and where the GDPR applies we notify the supervisory authority within 72 hours of becoming aware, and tell affected users where the law requires it.

No service is perfectly secure.

Your rights by region

You can exercise any right below by emailing [email protected], or in the app through Profile, then Contact Us. We will not charge you and we will not treat you differently for asking. We ask for enough information to be sure the request is yours.

Everywhere, you can:

• Access and Portability: Request a copy of your data.
• Correction: Update profile details, preferences, and goals.
• Deletion: Delete meals or delete your full account. Backups delete on rotation.
• Consent Controls: Revoke optional permissions (voice, location); opt out of promotional emails.

EEA and United Kingdom

You have the right of access, rectification, erasure, restriction of processing, data portability, and objection to processing based on our legitimate interests, including objection to direct marketing at any time. Where we rely on consent, you may withdraw it at any time, and withdrawal does not affect what we did before you withdrew it.

You can complain to your national supervisory authority. In Ireland that is the Data Protection Commission, in Germany your state authority, in Spain the AEPD, in France the CNIL, and in the United Kingdom the Information Commissioner's Office.

California

We do not sell personal information for money.

Under the CPRA, "share" covers disclosing personal information for cross-context behavioural advertising. We send purchase events to Meta so we can measure our advertising, and those events include an advertising identifier, an IP address and a hashed email address. We treat that disclosure as "sharing" under the CPRA.

To opt out of that sharing: email [email protected] with the subject "Do Not Sell or Share" and we will stop the server-side forwarding for your account. On iOS, declining App Tracking Transparency stops the in-app SDK from using your advertising identifier. On Android, turning off ads personalisation limits the advertising identifier. Those device controls do not stop the server-side forwarding on their own, which is why the email route exists.

You also have the right to know what we collect and disclose, to delete, to correct, and to limit the use of sensitive personal information. We collect sensitive personal information in the form of health data and precise geolocation, and we use it only to provide the features you asked for, never to infer characteristics about you. You may use an authorised agent.

Brazil

Under the LGPD you may confirm whether we process your data, access it, correct it, ask for anonymisation, blocking or deletion of data that is unnecessary or excessive, ask about who we share it with, ask about the consequences of refusing consent, withdraw consent, and request portability. Write to [email protected]. You may also complain to the ANPD.

India

Under the Digital Personal Data Protection Act 2023 you may access a summary of your data and the processing, correct or complete it, ask for erasure, nominate another person to exercise your rights if you die or become incapacitated, and withdraw consent.

Grievance route: email [email protected] with "Grievance" in the subject. Grievances are handled by our designated grievance contact. If you are not satisfied with our answer, you may complain to the Data Protection Board of India.

Canada

Under PIPEDA you may request access to your personal information and challenge its accuracy, and you may complain to the Office of the Privacy Commissioner of Canada.

Australia

Under the Privacy Act 1988 and the Australian Privacy Principles you may request access and correction, and complain to the Office of the Australian Information Commissioner. Our email marketing follows the Spam Act, and every message carries an unsubscribe link.

Marketing email and push

We send transactional messages that you cannot opt out of while you have an account, such as sign-in codes, receipts and security notices.

We also send messages that are ours, not yours: tips, product news, digests of your own nutrition, habit prompts and offers.

• Email marketing runs on an opt-out basis today. If you have an account and you have not told us to stop, you are on the list. You can unsubscribe from every one of those emails with the link in the message, in Profile settings, or by writing to [email protected]. One click is enough.
• Push marketing is capped at four messages a week per person with a cooldown between them. You can turn push notifications off in your phone's settings or in the app.
• We choose who gets which message using your language, your timezone, when you signed up, how recently you logged a meal, how many meals you have logged, and your health goal. Choosing by health goal, such as PCOS, pregnancy, diabetes or recovery, is a use of health data for marketing and rests on your explicit consent, which you can withdraw at any time by unsubscribing.
• We record whether you opened or clicked a message, along with the audience segment it was sent to. For a health-based segment, that record shows that someone with a hashed email in that segment opened a message.
• Some website and app features, including the demo tool and the calculators, are free to use without an account, and we do not add you to any list for using them.

Ads measurement

We advertise NutriScan, mostly on Meta platforms, and we need to know which ads led to installs and purchases.

• The app includes the Meta SDK, which sends events such as install, registration, trial start and purchase. It sends your advertising identifier only where you have allowed tracking on iOS.
• Separately, our servers send purchase events to the Meta Conversions API. Those calls include an anonymous Meta identifier, your Google Advertising ID on Android, your IP address, your email address as a SHA-256 hash, your app user id as a SHA-256 hash, and the purchase amount and currency.
• We may upload hashed email addresses to Meta to build advertising audiences. Meta matches them and discards what does not match.
• Health data never goes to Meta or to any advertising system.

To opt out of the server-side forwarding, email [email protected] with the subject "Do Not Sell or Share". Device-level controls, App Tracking Transparency on iOS and ads personalisation on Android, limit the SDK and the advertising identifier but do not by themselves stop the server-side calls.

AI disclosures

You are talking to software, not a person. The meal scanner, the chat assistant, the voice assistant and the website demo tool are all AI systems. Nobody at NutriScan reviews an answer before you see it. We do not use AI to make any decision about you that has legal effects.

Vendors: Google Gemini, OpenAI including through Azure, and ElevenLabs for voice. Which vendor serves a given request is set on our servers and can change. The website demo tool uses Google Gemini.

What is sent: your meal photo or its storage key, your food description or question, the conversation so far, your name, user id, city and coordinates, food preferences, health goal, timezone, subscription state, whether a health platform is connected, documents you attach, and your stored health readings where they are relevant to your question. For the website demo tool, the photo or text you submit and an approximate location derived from your IP address.

Training: we do not permit vendors to train on your data where the vendor offers that control.

Accuracy: nutrition estimates made from a photo can be materially wrong. Portion size in particular is estimated, not measured. Ingredients that are not visible are not detected. Do not rely on these numbers for a medical decision, including insulin dosing or avoiding an allergen.

Health and safety limits

NutriScan is a food and habit tracking app. It is not a medical device, and it is not a substitute for a doctor, a dietitian or a pharmacist.

• We do not diagnose anything. A number outside a range is coloured and labelled, and that is all it means.
• We do not give dosing advice, and we never tell you to change a medication.
• Health targets we show are informational and follow published general guidance. Your own targets come from your clinician.
• Nobody at NutriScan is acting as your licensed healthcare professional.
• If you are unwell, call a doctor or your local emergency number. The app has no emergency function and no crisis detection.

Children

NutriScan is not for children.

• In India you must be 18 or older.
• In the EEA and the United Kingdom you must be 16 or older.
• Everywhere else you must be 13 or older, and where your local law requires it, between 13 and 17 you need a parent or guardian's consent.

You tell us your age yourself. We do not run age verification. If we learn that an account belongs to someone under 13, we delete it. A parent or guardian can write to [email protected] to ask us to delete a child's account and data.

Changes to this policy

We update this policy when features or laws change. The updated version is posted here with a new effective date. When a change is material, we tell you in the app or by email before it takes effect.

Contact

• Email: [email protected]
• In the app: Profile, then Contact Us
• Post: Fizday Tech (OPC) Private Limited, #14, 1st Cross Road, 1st Main, 7th Block, Koramangala, Bengaluru, Karnataka 560095, India
• This page: https://nutriscan.app/privacy-policy

For a privacy request, use the subject "Privacy Request". For an India DPDP grievance, use "Grievance". For a California opt-out, use "Do Not Sell or Share". We answer within the deadline your law gives us.

What changed on 1 October 2026

• Added Vietnamese, Italian, Russian, Swedish, Polish, Brazilian Portuguese and Japanese versions of this page. The English text still governs.

What changed on 20 September 2026

• Web purchases are now paid through Stripe as our payment processor, with Fizday Tech (OPC) Private Limited as the seller. Stripe replaces the previous payment provider in the subscription row and the provider list.

What changed on 16 September 2026

• Added our legal entity, registration number and registered office.
• Added a health platforms section for Apple Health and Health Connect, covering what we read, what we write, where it is stored, and the rule that health data is never used for advertising and never sold.
• Added ElevenLabs as our voice provider, and medical report uploads as a data category.
• Added a full processor table naming every provider, what it does, what it receives and where it processes it.
• Added the website sections: the onboarding questionnaire, the food demo tool, Google Fonts and browser storage.
• Added the ads measurement section covering the Meta SDK and the server-side Conversions API, with a California opt-out route.
• Clarified the subscriber attributes RevenueCat holds, the device identifier used for referral checks, and the data our analytics receives.
• Clarified the legal bases for email and push, including health-goal segmentation, and how to opt out.
• Updated the security, retention and international transfer sections to describe our current measures.
• Updated the rights section with routes for the EEA and UK, California, Brazil, India, Canada and Australia.