Last updated: August 16, 2026
This Privacy Policy describes how BiteBot (“BiteBot,” “we,” “our,” or “us”) handles information when you use our iOS mobile application (the “App”).
Summary
Meal logs, water intake, goals, profile fields, favorites, and reminders are stored on your device (we do not operate a cloud database of your daily logs).
When you use certain features, the App sends food photos and/or food-related text from your device to third-party services to provide recognition, nutrition estimates, and recipe suggestions.
We do not sell your personal information. The App shows ads through Google AdMob to help keep BiteBot free; if you grant App Tracking Transparency (ATT) permission, some ads may be personalized using your device’s advertising identifier. You can decline or change this choice anytime in iOS Settings.
Contact (all inquiries): azhartahir.bitebot@gmail.com
By using BiteBot, you agree to this Privacy Policy. If you do not agree, please do not use the App.
1. Information We Collect and How We Use It
1.1 Information you enter (stored on your device)
When you use BiteBot, you may enter or generate:
Food and meal entries (names, calories, macros, meal type, notes, dates)
Water / hydration logs and related preferences
Profile and goals (for example: nickname, age, weight, height, gender, activity level, weight goal, daily calorie and macro targets, dietary preference, units)
Favorites, history, streaks, and in-app settings
This information is stored locally on your device using on-device storage (SwiftData and similar local storage). We do not sync your full meal history to our own servers.
How we use it: To show your Today dashboard, charts, streaks, reminders, favorites, and other core App features.
1.2 Device permissions
Depending on how you use BiteBot, the App may request the following permissions:
Camera: To take a meal photo in Scan Meal
Photo Library: To choose an existing meal photo in Scan Meal
Notifications: For meal and water reminders you enable in the App
App Tracking Transparency (Tracking): To personalize ads and measure their performance across apps. This is a separate, one-time system prompt — you may allow or deny it, and change your choice anytime in iOS Settings → Privacy & Security → Tracking.
You can grant or revoke permissions in iOS Settings. Some features will not work without the relevant permission.
We do not use camera or photos for facial recognition, identity verification, or advertising.
1.3 Information sent to third-party services (when you use connected features)
BiteBot does not require account creation or login. When you choose to use the features below, data is sent from your device directly to third-party providers over the internet.
A) Scan Meal (photo analysis)
When you tap Analyze on a meal photo:
Your meal photo (as image data) is sent for automated food classification (identifying what food appears in the image).
Based on the detected food label, the App may request recipe matches and nutrition-related information.
The photo uploads immediately when you tap Analyze; there is no separate consent dialog. If you'd rather not send a photo to these services, simply don't use the Scan Meal analyze feature.
B) Instant Nutrients (text lookup)
When you look up nutrition from ingredient or meal text you type (for example, “2 eggs, 1 slice bread”):
That text is sent to parse ingredients and return nutrition estimates.
C) Meal suggestions and recipes
When you use Smart Ideas, meal plans, or recipe detail features:
The App may send information such as your daily calorie target, diet filter (for example Keto, Vegan, Halal-oriented exclusions), meal type, ingredient exclusions you enter, and recipe identifiers needed to fetch results.
What we do not send with these API requests
We do not intentionally send your email address, Apple ID, or your full on-device meal history as part of these third-party requests. Requests are made using App-configured API access; providers may still receive technical data (such as IP address, timestamps, and request metadata) under their own policies.
D) Advertising (Google AdMob)
The App shows ads (interstitial, rewarded, and native ad formats) through Google AdMob to help keep BiteBot free to use.
If you grant App Tracking Transparency (ATT) permission, your device’s advertising identifier may be used to show more relevant ads and measure their performance.
If you deny or have not yet responded to the ATT prompt, or where required by regional consent gathered through Google’s User Messaging Platform (UMP), ads are shown without using your advertising identifier for cross-app tracking.
Watching a rewarded ad is always optional and only used to unlock a feature you choose; declining just means that specific one-time unlock is not available.
See Section 3.4 for details on Google’s role and privacy policy.
E) Analytics (Firebase, Google)
The App uses Firebase Analytics to understand which features are used (for example, screens viewed, meal-logging actions, and subscription events) so we can improve BiteBot, and Firebase Remote Config to remotely adjust feature availability and ad behavior without requiring an app update. This does not include your meal content, name, or contact details.
1.4 Subscriptions and purchases
If you purchase BiteBot Premium, payment and subscription management are handled by Apple through the App Store (StoreKit). We receive subscription status through Apple’s systems to unlock Premium features in the App. We do not receive or store your full payment card number.
Apple’s collection and use of purchase data are governed by Apple’s Privacy Policy.
1.5 Support and contact
If you email us at azhartahir.bitebot@gmail.com, we receive your email address, message content, and any information you choose to include. We use this only to respond and maintain support records as needed.
1.6 Information we do not intentionally collect
Unless you voluntarily include it in a message or entry, we do not intentionally collect:
Government ID numbers
Payment card numbers (handled by Apple for purchases)
Precise GPS location
Contacts from your address book
Health data from Apple Health / HealthKit (BiteBot does not require HealthKit access for core features)
We do not sell your personal information. Advertising identifiers are only used for ad personalization as described in Section 1.3(D), and only if you have granted App Tracking Transparency permission.
2. How We Use Information (purposes)
We use information only to:
Provide core App functionality (logging, dashboards, streaks, charts, favorites)
Perform food photo recognition and nutrition / recipe lookups when you use those features
Deliver local notifications you configure
Manage Premium access via Apple subscriptions
Show ads and, where you have granted App Tracking Transparency permission, personalize them and measure their performance (Google AdMob)
Understand feature usage and improve the App (Firebase Analytics)
Respond to support requests
Maintain and improve reliability and security of the App
We do not use your data for:
Selling your personal information
Cross-app or cross-site tracking, except through your device’s advertising identifier where you have granted App Tracking Transparency permission for ad personalization as described in Section 1.3(D)
3. Third-Party Services
We rely on a limited set of third parties:
3.1 Hugging Face
Purpose: Analyze meal photos you submit in Scan Meal to suggest what food is in the image. Data: Meal photo (image data) you choose to analyze. Privacy: See Hugging Face’s privacy policy at https://huggingface.co/privacy.
3.2 Spoonacular
Purpose: Nutrition parsing, recipe search, meal plans, and related nutrition information. Data: Food text you enter, recipe/meal parameters (such as calorie target and diet filters), and queries derived from scan results. Privacy: See Spoonacular’s terms and privacy information at https://spoonacular.com/food-api/terms.
3.3 Apple (App Store, StoreKit, optional system diagnostics)
Purpose: In-app purchases, subscriptions, distribution, and (if enabled by you at the system level) anonymized crash diagnostics. Privacy: https://www.apple.com/legal/privacy/
3.4 Google (AdMob, Firebase, User Messaging Platform)
Purpose: Serving and measuring ads (AdMob), gathering region-appropriate consent for ads (User Messaging Platform), and app analytics and remote configuration (Firebase).
Data: Your device’s advertising identifier (only if you grant App Tracking Transparency permission), ad interaction data, app usage/analytics events, and your consent choices.
Privacy: See Google’s Privacy Policy at https://policies.google.com/privacy and AdMob-specific information at https://support.google.com/admob/answer/6128543.
These providers process data under their own policies. We contractually expect them to provide services to us and not use your content for unrelated purposes, subject to their terms.
4. Data Storage, Retention, and Security
4.1 On your device
Your logs and profile data remain on your device until you delete entries, clear App data, or uninstall BiteBot. Uninstalling may permanently delete local data unless you have a device backup.
4.2 Third-party processing
Photos and text sent to Hugging Face or Spoonacular are processed to return results for your request. Those companies may retain logs or technical records according to their retention practices. Advertising and analytics data (Section 3.4) is retained and processed according to Google’s own retention practices. We do not control third-party servers.
4.3 Security
We use reasonable measures appropriate to a mobile app, including encrypted connections (HTTPS) for network requests and reliance on iOS security features. No method of transmission or storage is 100% secure.
4.4 Retention summary
Meal/water/profile logs on device: Until you delete them or uninstall the App
Support emails: As long as needed to handle your request and reasonable record-keeping
Third-party API logs: Per Hugging Face / Spoonacular / Google policies
5. Your Choices and Rights
5.1 In the App
Edit or delete individual meal and water entries (where the App provides those actions).
Turn notifications on or off in iOS Settings.
Allow or deny tracking via the App Tracking Transparency system prompt, and change your choice anytime in iOS Settings → Privacy & Security → Tracking.
Manage ad-related privacy/consent options via BiteBot Settings → Privacy Options (shown where required by your region).
Manage subscriptions: Settings → Apple ID → Subscriptions.
Restore purchases from BiteBot Settings when applicable.
5.2 Deletion
Local data: Delete in the App or uninstall BiteBot.
Third-party data: We cannot delete data held on Hugging Face, Spoonacular, or Google servers on your behalf; contact them or us and we will help where we can.
Support emails: Email azhartahir.bitebot@gmail.com to request deletion of correspondence we retain.
Depending on where you live (for example EEA/UK), you may have rights to access, correct, delete, restrict, or object to certain processing, or to lodge a complaint with a supervisory authority. Contact azhartahir.bitebot@gmail.com to exercise these rights.
6. Children’s Privacy
BiteBot is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has contacted us or used the App inappropriately, email azhartahir.bitebot@gmail.com and we will take appropriate steps.
7. International Users
Our third-party providers may process data in countries other than your own. Those countries may have different data protection laws. Where required, we rely on appropriate safeguards offered by providers or applicable law.
8. Changes to This Policy
We may update this Privacy Policy from time to time. We will update the “Last updated” date at the top. Material changes may be accompanied by an in-app notice. Continued use of BiteBot after changes means you accept the updated Policy.
9. Contact Us
For privacy questions, data requests, support, or any other inquiry:
Email: azhartahir.bitebot@gmail.com
Privacy Policy URL: https://sites.google.com/view/bitebot-privacypolicy/home
Terms of Use: https://sites.google.com/view/bitebot-terms/home