feedwisely Privacy Policy
Effective date: October 3, 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.
The short version
- We use your information to run feedwisely for you. We never sell it.
- Your health answers are collected only after you agree to the Health Disclaimer and the Health Privacy Notice, and they stay on your phone until you create your account.
- Meal photos go to Google's Gemini AI to read your meal. feedwisely doesn't keep them, and Google doesn't use them for training.
- Usage analytics start only after you give the health consent, and never include health values.
- You can delete your account and all its data in the app at any time.
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") responsible for your information. feedwisely is offered only in the United States and only to adults 18 and over.
2. Information we collect, why, and on what basis
2.1 Account information
| What | Why | Basis |
|---|---|---|
| Your email address, and the name your Google account shares if you sign in with Google | To 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 text | Needed to provide the Service |
| A user ID that Firebase assigns to your account | To link your data, your subscription and your analytics to your account | Needed 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)
Collected only after you accept the Health Disclaimer and the Health Privacy Notice (Onboarding, "Your health data").
| What | Why | Basis |
|---|---|---|
| Birth date | To check you are 18 or over and to estimate your energy expenditure (age is part of the formula) | Your consent |
| Height | To estimate expenditure, set a minimum fat target and check that a goal weight stays at a healthy BMI | Your consent |
| Weight at sign-up, and every weigh-in you log | To estimate expenditure, show your trend weight and update your targets | Your consent |
| Body-fat range (for example 24–28%) | To estimate expenditure and protein needs | Your consent |
| Activity level and exercise sessions a week | To estimate expenditure | Your consent |
| Goal (lose, maintain or gain), goal weight and weekly rate | To set your targets and estimated finish date | Your consent |
| Diet style (for example Balanced or Keto) and training type | To split your calories into protein, fat and carbs | Your consent |
| Food log: foods, amounts, times, calories and nutrients, including AI dish results and their ingredients | To show your intake against your targets and update your expenditure | Your consent |
| Your programs (calorie and macro targets) and weekly check-in results | To show and adjust your targets over time | Your consent |
| Meal photos and typed meal descriptions you send to the AI | To 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 results | Your 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:
- Before a photo is sent, the app shrinks it and removes its metadata, so no location information leaves your phone.
- The copies the app makes on your phone are deleted right after the analysis. feedwisely does not store photos on its servers.
- feedwisely uses the paid Gemini API, under which Google doesn't use your photo or text to train its models. Google may keep requests for a limited time to detect abuse, as its terms allow.
- What is saved to your account is the result you log: the dish name, its ingredients, amounts and nutrients. The description you typed is not saved.
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.
2.5 Consent records
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 first screens of the app are held in memory on your phone and sent only after you consent; if you don't consent, 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 your device model, Android version and app version. IP address and location capture are turned off in our PostHog project.
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
- App Check and Play Integrity. To confirm requests come from the real feedwisely app, the app uses Firebase App Check with Google Play Integrity, which sends device and app integrity information to Google.
- Barcode reader. The barcode reader (Google ML Kit, built into the app) runs on your phone and may send device and app information to Google.
- Identifiers. Firebase installation, App Check, Crashlytics, RevenueCat and PostHog identifiers.
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 happen on your phone and are not sent anywhere.
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
- No precise location. Photo metadata, including location, is removed before a photo leaves your phone.
- No contacts, microphone or files. The camera is used only when you open Scan or Snap, and photos from your gallery come through Android's photo picker, which shares only the photo you choose.
- No Health Connect data in this version.
- No payment card details.
- No advertising identifiers and no ads.
3. What stays on your phone
- Before you create an account, your onboarding answers and consent records are kept only on your phone. If you go back from the consent screen, nothing is kept.
- The built-in USDA food list and your searches of it.
- Your plate (foods picked but not yet logged), view choices and similar settings.
- A copy of your account data, kept by Firebase so the app works offline. Changes made offline sync when you are back online. This copy is cleared when you log out or delete your account.
- The account last signed in on this phone (email, sign-in method and Google name), so the login screen can offer it. It is kept after you log out and removed when you delete your account. It is never uploaded.
- Photos you take or pick for the AI, deleted from the app's storage right after the analysis.
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:
| Provider | What it does for us | What it receives |
|---|---|---|
| Google Firebase (Google LLC): Authentication, Cloud Firestore, Crashlytics, App Check | Accounts and sign-in; stores your account data; crash reports; abuse protection | Account 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 descriptions | The photo or description you send, at the moment of analysis |
| RevenueCat (RevenueCat, Inc.) | Manages subscriptions with Google Play | Your Firebase user ID, purchase and subscription information, and device identifiers |
| PostHog (PostHog, Inc.) | Product analytics | The 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 lookups | Your search text or barcode number, the app's name and version, your IP address |
| Google Play (Google LLC) | Sells and bills subscriptions | Your 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
| What | How long |
|---|---|
| Account data (profile, weigh-ins, food logs, 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 photos | Not kept by feedwisely: deleted from the phone right after analysis, never stored on our servers |
| RevenueCat and PostHog records | Until you delete your account; then deleted within 30 days |
| Crash reports | 90 days |
| Support emails | Up to 2 years after the conversation ends |
| Google Play order records | Kept 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:
- In the app: More › Account & Data Deletion. You confirm it's you, and your account is deleted. You can also reach deletion from the "subscription ended" screen and from the "finish setup" screen.
- On the web: https://feedwisely.com/delete-account explains the steps. You can also email support@feedwisely.com from the email address on your account and ask us to delete it.
When you delete your account:
- your sign-in account and everything saved under it (profile, weigh-ins, food logs, goals, programs, check-ins, settings, consent records and AI reports) are permanently deleted from our servers;
- your RevenueCat and PostHog records are deleted too;
- all of this is completed within 30 days;
- the copy on your phone is cleared;
- Google Play keeps its own order records, which we can't delete.
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:
- Access the personal information we hold about you, and get a copy. Email support@feedwisely.com.
- Correct it. You can edit or delete your weigh-ins and food logs in the app. To correct your birth date, height or other details, contact Support.
- Delete it, as described in section 6.
- Withdraw your consent to the processing of your health data. In this version, you do this by deleting your account, or by contacting Support.
- Know who we share it with: the list in section 4.
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.
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:
- Camera: you can refuse or turn off camera access in Android settings. Search and Quick Add still work.
- Analytics: analytics stop when you log out or delete your account.
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. United States only
feedwisely is offered only in the United States, and your information is stored in the United States. The Service is not directed to people outside the US.
10. Security
- Data is encrypted in transit between the app and our providers.
- Server access rules let each signed-in person reach only their own data.
- Firebase App Check checks that requests come from the genuine app.
- Photos are stripped of location data before they leave your phone and are not stored by us.
- Health values are kept out of analytics and crash reports.
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.
11. 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.
12. Contact
Mohd Aqib, an individual based in India
Email: support@feedwisely.com