feedwisely.

feedwisely Privacy Policy

Effective date: October 20, 2026

This Privacy Policy explains what information the feedwisely app for Android and the feedwisely.com web pages (the "Service") collect, why, who we share it with, how long we keep it, and the choices you have.

Much of what you put into feedwisely is health information (your weight, body measurements and what you eat). Our Health Privacy Notice explains how we handle that "consumer health data" under US state laws such as Washington's My Health My Data Act. It is part of this policy. If you live in India, section 10 explains your rights under Indian law.

The short version

1. Who we are

feedwisely is provided by:

Mohd Aqib, an individual based in India

Email: support@feedwisely.com

We are the "controller" (or "regulated entity", or "Data Fiduciary" under Indian law) responsible for your information. feedwisely is offered only in the United States and India, and only to adults 18 and over.

2. Information we collect, why, and on what basis

2.1 Account information

WhatWhyBasis
Your email address, and the name your Google account shares if you sign in with GoogleTo create and secure your account, sign you in, and send account emails (verification and password reset)Needed to provide the Service you asked for
Your password (email accounts)To sign you in. It is handled by Google Firebase Authentication; we never see it in plain textNeeded to provide the Service
A user ID that Firebase assigns to your accountTo link your data, your subscription and your analytics to your accountNeeded to provide the Service

Before you create an account, the app makes an anonymous Firebase user so you can subscribe first. If you then create an account, the same user ID is kept.

2.2 Health and body information (consumer health data)

We receive it only after you accept the Health Disclaimer and the Health Privacy Notice on the "Your health data" screen, which comes after the setup questions. The answers you give before that stay only on your phone.

WhatWhyBasis
Birth dateTo check you are 18 or over and to estimate your energy expenditure (age is part of the formula)Your consent
HeightTo estimate expenditure, set a minimum fat target and check that a goal weight stays at a healthy BMIYour consent
Weight at sign-up, and every weigh-in you logTo estimate expenditure, show your trend weight and update your targetsYour consent
Body-fat range (for example 24–28%)To estimate expenditure and protein needsYour consent
Activity level and exercise sessions a weekTo estimate expenditureYour consent
Goal (lose, maintain or gain), goal weight and weekly rateTo set your targets and estimated finish dateYour consent
Diet style (for example Balanced or Keto) and training typeTo split your calories into protein, fat and carbsYour consent
Food log: foods, amounts, times, calories and nutrients, including AI dish results and their ingredientsTo show your intake against your targets and update your expenditureYour consent
Favorites you save: a copy of the food (its name, brand, serving, calories and nutrients, icon and, for an AI dish, its ingredients) and the nickname you give itTo let you log those foods again from the LibraryYour consent
Custom foods you create: the food's name, brand, barcode, serving, calories and nutrients, the icon you choose, and, for a copy made with To Custom, which food it was copied fromTo let you log those foods again, from the Library, from Search and by scanning their barcodeYour consent
Your programs (calorie and macro targets) and weekly check-in resultsTo show and adjust your targets over timeYour consent
Meal photos and typed meal descriptions you send to the AITo estimate the foods in your meal. Sent to Google's Gemini AI; not kept by feedwisely (see 2.3)Your consent
"Report a problem" reports on AI results: the dish result and your note (never the photo or the description)To improve AI resultsYour consent

We do not ask for your sex in this version of the app.

2.3 Meal photos and descriptions sent to the AI

When you use Snap (photo) or Describe (text), your photo or description is sent to Google's Gemini AI, through Google Firebase AI Logic, to read your meal.

Your photo goes to Google's Gemini AI to read your meal. feedwisely doesn't keep it, and Google doesn't use it for training.

In more detail:

2.4 Settings

Your units (lb or kg, feet and inches or cm), Food Log view settings, and the date you signed up, saved with your account so they follow you to a new phone.

When you accept the Health Disclaimer, the Health Privacy Notice, the Terms of Service and this Privacy Policy, we save which document and version you accepted and when. Why: to show that you gave consent. Basis: our legal obligations.

2.6 Purchase information

When you subscribe, Google Play handles the payment. We (through RevenueCat) receive your subscription status, plan, trial status, renewal and expiry dates, and purchase records, linked to your Firebase user ID. We never receive your card details. Why: to unlock the app and show your subscription. Basis: needed to provide the Service you paid for.

2.7 Usage analytics (PostHog)

Nothing is sent before you give the health consent on the "Your health data" screen. After that, the app sends product events such as "onboarding step viewed", "paywall viewed", "plan selected", "purchase succeeded", "food logged" (how, never what), "weigh-in logged" (never the weight), "check-in completed" and "account deleted". Events from the screens before it (the start of the app and the setup questions) are held in memory on your phone and sent only after you consent; if you don't consent, or the app is closed first, they are dropped.

Analytics never include health values: no weight, food, calories, birth date, height, body fat, or goal weight or rate. The only goal detail sent is the goal type (lose, maintain or gain) when you save a new goal. Session replay is off.

After you create an account or log in, events are linked to your Firebase user ID. PostHog's software also records technical details about your device and the app: device make and model, Android version, app version, language, screen size and connection type (Wi-Fi or mobile data). Our PostHog project doesn't store your IP address, doesn't work out your location from it, and drops your time zone and mobile carrier.

Why: to understand how people use the app and improve it. Basis: your consent, given on the health consent screen. Analytics start only after you give it.

Analytics stop when you log out or delete your account.

2.8 Crash reports (Firebase Crashlytics)

Crash reports are sent from the first time you open the app, before you create an account. They contain technical details about the error (such as the stack trace), the app version, and device information (such as model and Android version), with a Firebase installation identifier. They do not contain your account ID or any health information. Why: to find and fix crashes. Basis: keeping the app working, which is necessary to provide the Service. Because they are sent before you consent, they never include your account ID or any health information.

2.9 Device and security information

Why: security, abuse prevention and running the Service. Basis: our legitimate interest in protecting the Service.

2.10 Food lookups (Open Food Facts)

When you search for a brand-name food or scan a barcode, your search text or the barcode number is sent directly from your phone to Open Food Facts to find the product. Each request carries the app's name, version and our contact email. It does not carry your account ID or any health information. Open Food Facts, like any website, receives your phone's IP address. Searches of the built-in USDA food list and of the custom foods you created happen on your phone and are not sent anywhere. A scanned barcode is first matched on your phone against your custom foods; if one matches, nothing is sent. Scanning a barcode into the Create Food form only reads the number and doesn't look it up.

2.11 Support requests

If you email support@feedwisely.com, we receive your email address and what you write. Why: to answer you and handle requests about your data.

2.12 What we don't collect

3. What stays on your phone

Your unfinished onboarding answers, your account data, and sign-in data are excluded from Android backups, so they are not copied to a new phone through backup.

4. Who we share information with

We do not sell your personal information or health data, and we do not share it for targeted advertising. We share it only with these service providers, who process it for us under contract, and with Google Play for purchases:

ProviderWhat it does for usWhat it receives
Google Firebase (Google LLC): Authentication, Cloud Firestore, Crashlytics, App CheckAccounts and sign-in; stores your account data; crash reports; abuse protectionAccount information; all the data saved to your account (section 2.2, 2.4, 2.5); crash reports; device integrity information
Google Gemini, via Firebase AI Logic (Google LLC)Estimates meals from photos and descriptionsThe photo or description you send, at the moment of analysis
RevenueCat (RevenueCat, Inc.)Manages subscriptions with Google PlayYour Firebase user ID, purchase and subscription information, and device identifiers
PostHog (PostHog, Inc.)Product analyticsThe events in section 2.7, your Firebase user ID after sign-up, device and app information
Open Food Facts (Open Food Facts association)Brand-name food search and barcode lookupsYour search text or barcode number, the app's name and version, your IP address
Google Play (Google LLC)Sells and bills subscriptionsYour purchase, under Google's own privacy policy

Your data is stored on Google Firebase servers in the United States (Cloud Firestore multi-region location nam5). PostHog data is stored in the United States.

We may also disclose information if the law requires it (for example, a valid court order), or to protect the rights or safety of our users or others. If the business is sold or merged, information may move to the new owner, and this policy continues to apply to it. Health data is never sold. It is disclosed only when the law requires it, and in a sale or merger it moves to the new owner only with your consent where the law requires it (see the Health Privacy Notice).

5. How long we keep information

WhatHow long
Account data (profile, weigh-ins, food logs, custom foods, favorites, goals, programs, check-ins, settings, consent records, AI reports)Until you delete your account. We don't delete accounts automatically when they aren't used
Meal photosNot kept by feedwisely: deleted from the phone right after analysis, never stored on our servers
RevenueCat and PostHog recordsUntil you delete your account; then deleted within 30 days
Crash reports90 days
Support emailsUp to 2 years after the conversation ends
Google Play order recordsKept by Google under its own policies; we can't delete them

6. Deleting your account and data

You can delete your account at any time:

When you delete your account:

Deleting your account does not cancel your Google Play subscription. Cancel it in Google Play to stop being charged.

If you subscribed but never created an account, a purchase record still exists with Google Play and RevenueCat. Email support@feedwisely.com to ask about it.

7. Your rights and choices

Wherever you live in the US, you can ask us to:

We won't treat you differently for using these rights. We will verify your request, for example by asking you to write from your account's email address. We will reply within 45 days. If we need more time, we may extend this once by another 45 days, and we'll tell you why within the first 45 days. If we refuse a request, you can appeal by replying to our decision within 45 days. We will answer your appeal within 45 days and explain our decision. If we deny your appeal, you can contact your state Attorney General. You may use an authorized agent where the law allows.

Some states (for example California, Colorado, Connecticut, Virginia, Washington and others) give additional rights. You can use the same routes above for any of them.

If you live in India, section 10 lists your rights under Indian law.

California. We do not sell your personal information, and we do not share it for cross-context behavioral advertising. The information we collect, why, and who receives it are described in sections 2 and 4. California residents can make access, correction and deletion requests in the same ways as everyone else.

Other choices:

8. Children

feedwisely is for adults 18 and over. The app asks for your birth date and does not let anyone under 18 continue. We do not knowingly collect information from anyone under 18. If you think someone under 18 has given us information, email support@feedwisely.com and we will delete it.

9. Where feedwisely is offered and where your data is stored

feedwisely is offered only in the United States and India. The Service is not directed to people in other countries.

Your information is stored in the United States, on Google Firebase (Cloud Firestore location nam5) and PostHog's US servers. If you use feedwisely from India, your information is transferred to the United States and processed there. Our providers, listed in section 4, may also process it in other countries where they operate.

10. If you live in India

This section applies if you live in India. It adds to the rest of this policy.

The law. We process your personal data under India's Digital Personal Data Protection Act, 2023 and the rules made under it. Sections 2 to 6 describe the personal data we collect, why we use it, who receives it, how long we keep it and how to delete it. We receive your health information only after you give your consent on the "Your health data" screen; the setup answers you give before it stay only on your phone.

Your rights. You can:

To use any of these rights, email support@feedwisely.com from the email address on your account, so we can verify it is you.

Grievance Officer. Mohd Aqib, support@feedwisely.com. We acknowledge grievances within 48 hours and resolve them within 1 month of receiving them.

The Data Protection Board of India. If you are not satisfied with how we handled your grievance, you can complain to the Data Protection Board of India. The law asks you to use our grievance process first.

Transfer out of India. Your personal data is stored and processed in the United States, as described in section 9. Meal photos and descriptions go to Google's Gemini AI, which processes them on Google's servers, in the United States or other countries where Google operates.

Health data is never sold. We don't sell your personal data or health data, and we don't use it for advertising.

11. Security

No system is perfectly secure. If we learn of a breach that affects your information, we will notify you and the authorities as the law requires.

12. Changes to this policy

We may update this policy. We'll post the new version with a new effective date. If a change is material, we'll tell you in the app and by email at least 30 days before it takes effect. If a change would let us use your health data in a new way, we will ask for your consent first.

13. Contact

Mohd Aqib, an individual based in India

Email: support@feedwisely.com

Grievance Officer (India): Mohd Aqib, support@feedwisely.com