Privacy Policy
Last updated: February 24, 2026
1. Introduction
This Privacy Policy describes how NutriiFit AI ("we," "us," or "our") collects, uses, and shares information when you use our mobile application ("the App"). By using NutriiFit AI, you agree to the collection and use of information in accordance with this policy.
NutriiFit AI is an AI-powered calorie and nutrition tracking application for iPhone. We are committed to protecting your privacy and being transparent about our data practices.
2. Information We Collect
2.1 Information You Provide Directly
- Body statistics: Gender, age, height, current weight, and target weight (entered during onboarding)
- Food logs: Manually searched foods, meal categories, and serving sizes
- Weight entries: Weight measurements logged via the weight tracker
- Water intake: Number of glasses of water tracked
- Dietary preferences and health goals: Diet type, activity level, goal (lose/gain/maintain), and selected challenges
- Meal descriptions: Text descriptions of meals provided via voice or text input
2.2 Information Collected Through Device Features
- Camera: Food photos and nutrition label images captured for AI analysis. Images are sent to our server-side API proxy, forwarded to Google's Gemini API for processing, and discarded immediately after the nutritional analysis is returned. Photos are not saved to any server, not stored in any database, and not used for any purpose other than the immediate AI analysis you requested.
- Microphone: Used exclusively for voice-based food logging. The microphone is activated only when you explicitly tap the microphone button on the Today screen. It is never activated in the background or without your action.
- Speech Recognition: Voice audio is processed entirely on-device by Apple's native iOS Speech Recognition framework (SFSpeechRecognizer). The raw audio recording is never transmitted to our servers, Google, or any third party. Only the resulting text transcript (e.g., "two eggs and toast") is sent to Google's Gemini API for nutritional analysis. Apple may process speech data according to Apple's Privacy Policy.
- Apple HealthKit (with your explicit permission): We read active energy burned, step count, and body mass. We write dietary energy consumed (kcal), dietary protein (g), dietary carbohydrates (g), dietary fat total (g), dietary water (mL), and body mass (kg). HealthKit data is never sent to Google Gemini or any AI service.
2.3 Information Collected Automatically
- Anonymous subscription identifier: Generated by RevenueCat, tied to your Apple ID via the App Store receipt. This is not linked to your personal identity.
- Purchase history: Subscription plan selected, managed through Apple's App Store and RevenueCat.
2.4 Information We Do NOT Collect
- Name, email address, phone number, or any contact information
- Location data
- Browsing or search history
- Advertising identifiers (IDFA)
- Social media accounts
- We do not create user accounts or require login
3. How We Use Your Information
- To provide core app functionality: calorie tracking, nutrition logging, macro calculations, water tracking, and weight management
- To analyze food photos, nutrition labels, and meal descriptions using AI (Google Gemini API)
- To look up food products by barcode (Open Food Facts, USDA FoodData Central)
- To synchronize health data with Apple Health (with your explicit permission)
- To validate and manage your subscription (RevenueCat)
- To send local notification reminders (with your permission)
- To calculate personalized nutrition targets (BMR, TDEE, macro splits)
We do NOT use your health, fitness, nutrition, camera, or HealthKit data for advertising, marketing, or data mining purposes.
4. Third-Party Services and Data Sharing
We share data with the following third-party services only as necessary to provide the App's features. We do not sell, rent, or share your personal information with third parties for their marketing or advertising purposes.
4.1 Google Gemini API (AI Food Analysis)
- What is sent: Food photos (as images), nutrition label images, voice transcripts (text), and meal descriptions (text)
- Purpose: AI-powered food recognition, nutrition estimation, and nutrition label parsing
- Data transmitted via: Our secure server-side API routes — no direct client-to-Google communication
- No personal identifiers sent: No name, email, device ID, or Apple ID is included in any request
- Google's data handling: On the paid API tier, prompts and responses are not used for model training. Data may be logged for up to 55 days for safety and abuse monitoring, then deleted.
For more information, see Google's Privacy Policy and Gemini API Terms.
4.2 RevenueCat (Subscription Management)
- What is shared: Anonymous user identifier and purchase/subscription history
- Purpose: Subscription validation, entitlement management, and analytics
- No personal identifiers: Uses anonymous IDs only; not linked to your identity
See RevenueCat's Privacy Policy.
4.3 Open Food Facts (Food Database)
- What is sent: Barcode numbers and food search queries
- Purpose: Looking up product nutrition information
- No user data sent: Only barcode strings and search terms are transmitted
See Open Food Facts Privacy Policy.
4.4 USDA FoodData Central (Food Database)
- What is sent: Barcode numbers and food search queries
- Purpose: Looking up product nutrition information from the U.S. government database
- No user data sent: Only barcode strings and search terms are transmitted
4.5 Apple HealthKit
- What is shared: Nutrition data (calories, macros), water intake, and body mass (written to Apple Health); activity data, steps, and weight (read from Apple Health)
- Purpose: Synchronizing health data for a unified health management experience
- Data stays on device: HealthKit data remains in Apple's Health ecosystem. It is NOT transmitted to Google, RevenueCat, or any other third party.
- User control: You can revoke HealthKit access at any time in iOS Settings > Health > Data Access & Devices
5. Apple HealthKit Data
Important: This section specifically addresses our use of Apple HealthKit data, as required by Apple's App Store guidelines.
We access Apple HealthKit data solely to provide you with an integrated health tracking experience.
| Direction | Data Type | Unit |
|---|---|---|
| Read | Active Energy Burned | kcal |
| Read | Step Count | steps |
| Read | Body Mass | kg |
| Write | Dietary Energy Consumed | kcal |
| Write | Dietary Protein | g |
| Write | Dietary Carbohydrates | g |
| Write | Dietary Fat Total | g |
| Write | Dietary Water | mL |
| Write | Body Mass | kg |
HealthKit data is:
- NEVER used for advertising or marketing
- NEVER sold to third parties
- NEVER shared with third parties (including Google, RevenueCat, or any analytics service)
- NEVER used for data mining
- NOT stored in iCloud
You may revoke HealthKit access at any time through iOS Settings > Health > Data Access & Devices.
6. AI and Automated Processing
Third-Party AI Disclosure (Apple Guideline 5.1.2): NutriiFit AI sends certain user-provided content to Google's Gemini 2.0 Flash API, a third-party artificial intelligence service operated by Google LLC. By using AI-powered features, you explicitly consent to this data transfer. You are informed of this before your first AI interaction within the App.
6.1 What Triggers AI Data Transfer
The following actions cause data to be sent from your device to our server-side API proxy, which forwards it to Google's Gemini API:
- Photo Scan: Your food photo (image data) is sent for AI-powered food recognition and nutrition estimation
- Nutrition Label Scan: Your nutrition label photo (image data) is sent for OCR analysis and structured data extraction
- Voice Log: Your meal description as text only (converted from speech on-device by Apple's Speech framework) is sent for nutrition parsing
- Describe Meal: Your typed meal description (text) is sent for nutrition parsing
6.2 What Is NOT Sent to Google Gemini
- No personal identifiers (name, email, phone number, device ID, Apple ID)
- No Apple HealthKit data (activity, steps, weight, nutrition)
- No user profile data (age, gender, height, weight, goals)
- No food log history or stored meal data
- No location data
- No raw audio recordings (only text transcripts from on-device speech recognition)
6.3 How AI Data Is Transmitted
- All AI requests are routed through our server-side API proxy hosted on EAS Hosting (Cloudflare Workers). Your device never communicates directly with Google's servers.
- All transmissions use HTTPS/TLS encryption.
- Our API proxy is stateless — it forwards requests to Google Gemini and returns responses. No user data is logged, cached, or stored on our servers.
- The Google Gemini API key is stored securely on the server and is never exposed to the client device.
6.4 Google's Data Handling
- NutriiFit AI uses Google Gemini's paid API tier.
- On the paid tier, prompts and responses are not used to train or improve Google's AI models.
- Google may retain API inputs and outputs for up to 55 days for safety monitoring, abuse prevention, and debugging, after which data is automatically deleted.
- Google processes data in accordance with Google's Privacy Policy and Gemini API Terms of Service.
6.5 AI Accuracy
- AI-generated nutritional estimates are approximations only and may contain errors, inaccuracies, or omissions.
- You should verify AI outputs before relying on them for dietary decisions.
- NutriiFit AI is not a medical device and AI outputs do not constitute medical or dietary advice.
6.6 Your Consent and Control
- You are informed before your first AI interaction that data will be sent to Google's Gemini AI.
- AI-powered features are optional. You can choose not to use them; manual food search and barcode lookup work without AI and do not send data to Google.
- AI analysis is limited to 30 requests per day (combined across photo scan, label scan, voice parse, and describe meal). Barcode lookups are not subject to this limit.
- You may withdraw consent at any time by ceasing to use AI-powered features. No further data will be sent to Google.
7. Complete Data Flow Summary
The following table summarizes every type of data the App handles, where it goes, and whether it is stored:
| Data Type | Destination | Stored? | Shared With |
|---|---|---|---|
| Food photos | Our API proxy → Google Gemini | No (processed and discarded) | Google (Gemini API) |
| Nutrition label images | Our API proxy → Google Gemini | No (processed and discarded) | Google (Gemini API) |
| Voice audio | On-device only (Apple Speech) | No | Apple (on-device Speech framework) |
| Voice text transcript | Our API proxy → Google Gemini | No (processed and discarded) | Google (Gemini API) |
| Typed meal descriptions | Our API proxy → Google Gemini | No (processed and discarded) | Google (Gemini API) |
| Barcode numbers | Open Food Facts / USDA APIs | No | Open Food Facts, USDA |
| Food search queries | USDA / Open Food Facts APIs | No | USDA, Open Food Facts |
| Food log entries | On-device only (AsyncStorage) | Yes (locally) | None |
| Weight entries | On-device only (AsyncStorage) | Yes (locally) | Apple Health (if enabled) |
| Water intake | On-device only (AsyncStorage) | Yes (locally) | Apple Health (if enabled) |
| User profile (age, gender, etc.) | On-device only (AsyncStorage) | Yes (locally) | None |
| HealthKit data | On-device (Apple Health) | Yes (Apple Health) | None (never sent to AI or servers) |
| Anonymous device ID | RevenueCat servers | Yes (RevenueCat) | RevenueCat |
| Subscription status | Apple / RevenueCat | Yes (Apple/RevenueCat) | RevenueCat |
8. Data Storage and Security
- All personal data (food logs, weight history, profile, preferences) is stored locally on your device using encrypted local storage.
- No cloud database or server-side user accounts exist.
- Data transmitted to third-party APIs uses HTTPS/TLS encryption.
- Food photos and nutrition label images are processed transiently and are not permanently stored on any server.
- HealthKit data is protected by Apple's device-level encryption.
- Personal health information is not stored in iCloud.
9. Data Retention
- Local data: Retained on your device until you delete it or uninstall the App.
- Google Gemini API: Logs retained for up to 55 days for abuse monitoring, then automatically deleted. Data is not used for model training.
- RevenueCat: Purchase history retained per RevenueCat's data retention policy.
- Open Food Facts / USDA: No user data is retained. These are stateless API queries.
10. Your Rights and Choices
10.1 All Users
- Access: View all your data within the App (food logs, weight history, profile).
- Deletion: Delete individual entries via swipe-to-delete, or uninstall the App to remove all local data.
- HealthKit control: Enable or disable HealthKit sync at any time in the App's Profile settings or via iOS Settings.
- Notification control: Enable or disable notifications in-app or via iOS Settings.
- Camera/Microphone: Revoke permissions at any time via iOS Settings.
10.2 European Economic Area (EEA) Residents
Under the General Data Protection Regulation (GDPR), you have the following rights:
- Right to access your personal data
- Right to rectification (correction) of inaccurate data
- Right to erasure ("right to be forgotten")
- Right to restrict processing
- Right to data portability
- Right to object to processing
- Right to withdraw consent at any time
- Right to lodge a complaint with a supervisory authority
Legal basis for processing: consent (AI analysis, HealthKit) and legitimate interest (core app functionality).
10.3 California Residents
Under the California Consumer Privacy Act (CCPA/CPRA), you have the following rights:
- Right to know what personal information is collected, used, and disclosed
- Right to delete personal information
- Right to opt-out of the sale or sharing of personal information
- Right to non-discrimination for exercising privacy rights
We do not sell or share your personal information as defined by the CCPA/CPRA.
11. Notifications
The App uses local notifications only for meal reminders. No notification data is sent to any server. You can manage notification preferences in-app or through iOS Settings. Notification permission is requested via a soft prompt and is never required.
12. Children's Privacy
NutriiFit AI is not directed to children under the age of 13 (or under 16 in the European Economic Area). We do not knowingly collect personal information from children under 13. The App's onboarding includes an age selection starting at age 14.
If we learn that we have inadvertently collected information from a child under 13, we will take steps to delete such information promptly. Parents or guardians who believe their child has provided information may contact us at support@nutriifit.ai.
13. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last Updated" date. Material changes will be communicated through the App. Continued use of the App after changes constitutes acceptance of the updated policy.
14. Contact Us
If you have questions about this Privacy Policy or our data practices, please contact us:
- Email: support@nutriifit.ai
We will respond to your inquiry within 30 days.