LiftEats Privacy Policy

This Privacy Policy explains how LiftEats processes information when you use the LiftEats iOS app and its related marketing and support pages. LiftEats is operated by Ahmad Ali Tariq in Pakistan ("we", "us", or "our").

LiftEats is intended for users aged 13 and older. If you are under the age of majority where you live, use LiftEats with parent or guardian involvement where required by law.

When you create or use an account, LiftEats may process your Firebase user ID, email address, authentication provider, display name where provided, and session information. You may sign in with email and password, Sign in with Apple, or Google Sign-In. Those providers process information under their own policies.

LiftEats processes the profile and fitness information you enter, including your name, age, height, weight, gender, fitness goal, activity level, onboarding status, and calculated calorie and macronutrient targets. This may be considered health or fitness-related information in some places.

LiftEats also processes content you create, including typed meal and workout descriptions, meal photos, entry titles, dates and times, manual corrections, saved meals, calories, macronutrients, exercise details, and requests to reinterpret an entry with AI.

Meal photos may be captured with your camera or selected from your photo library. A photo can incidentally contain people, locations, documents, or other information visible in the image. Please avoid submitting unnecessary sensitive information.

LiftEats uses a backend hosted on Google Cloud Run and the OpenAI API to generate meal and workout estimates. Typed input, meal images, and relevant goal context may be transmitted to these services for analysis. Generated information can include estimated calories and macros, food-item breakdowns, exercise information, assumptions, confidence information, goal-fit scores, and explanations.

AI-generated information is an estimate. It can be inaccurate, incomplete, or unsuitable for your circumstances. We do not state that OpenAI never retains API data or never uses it for model improvement; applicable handling depends on OpenAI's current terms, account settings, and data controls.

LiftEats uses Firebase Authentication, Cloud Firestore, Firebase Storage, Firebase Cloud Functions, Firebase App Check, and Google Cloud Run to authenticate users, store user-owned records and meal images, operate account deletion, protect requests, provide backend processing, and enforce AI usage allowances.

We use your information to operate the app, personalize targets and goal-fit feedback, save your history, provide AI analyses, maintain security, prevent abuse, resolve support issues, and improve reliability.

LiftEats records information needed to enforce its fair-use policy, such as a user identifier, subscription product, entitlement state, current usage-cycle dates, AI scan limit, successful AI analyses used, and update time.

Apple processes payments, free trials, renewals, cancellations, and refunds through the App Store. LiftEats does not receive or store your full payment-card details.

LiftEats uses RevenueCat to manage offerings, packages, entitlements, purchase and renewal information, restore behavior, and subscription lifecycle synchronization. RevenueCat's App User ID is mapped to your Firebase user ID. Apple, RevenueCat, and our backend may process product identifiers, trial or paid status, entitlement dates, transaction or receipt metadata made available through StoreKit or RevenueCat, and store environment information.

LiftEats uses Firebase Analytics, Crashlytics, and Performance Monitoring. These services may process app version, device and operating-system information, Firebase installation or app-instance identifiers, session and feature-use information, authentication method, onboarding progress, AI request outcomes, crash and non-fatal error reports, network and performance timing, IP address or similar technical information, and an opaque Firebase user ID where configured.

The app's custom telemetry is designed not to send raw meal text, meal images, email addresses, names, or macro values as custom analytics event parameters. This does not mean that service providers receive no technical metadata.

Reminder preferences are stored locally using AppStorage or UserDefaults. If you choose a reminder mode that requires notifications, LiftEats requests permission and schedules local notifications. It does not currently use remote push notifications or background tasks for these reminders.

LiftEats may request camera access to photograph meals, photo-library access to select a meal image, and notification permission to schedule local reminders. You can change these permissions in iOS Settings. Declining a permission limits only the related feature.

LiftEats does not currently use HealthKit, location, or microphone access.

We may share information with service providers that operate LiftEats: Apple for distribution, App Store purchases, subscriptions, and Sign in with Apple; Google and Firebase for authentication, storage, backend services, analytics, diagnostics, performance monitoring, and Google Sign-In; Google Cloud Run for backend processing; OpenAI for AI interpretation; and RevenueCat for subscription and entitlement services.

We may also disclose information where required by law, to enforce our terms, to address fraud, abuse, or security incidents, or as part of a merger, acquisition, financing, or asset transfer with appropriate safeguards. We do not sell personal information in the ordinary sense and do not use the app for third-party advertising.

Account, profile, meal, workout, saved-meal, and image content is generally retained while your account is active or until you delete the relevant content or your account, subject to legitimate legal, security, operational, and backup requirements.

The in-app account-deletion flow deletes the Firebase Authentication account, the user's Firestore data subtree (including profile, saved meals, logged history, and private subscription-state documents), user meal images in Firebase Storage, and usage-quota records. Deleting an account does not cancel an Apple subscription.

Apple, RevenueCat, backups, security records, and operational subscription or transaction records may retain information where needed for billing, fraud prevention, entitlement reconciliation, legal obligations, or provider operations. RevenueCat webhook records are designed for limited operational retention, but this policy does not promise a fixed deletion period.

We use reasonable technical and organizational safeguards, including authenticated Firebase access controls, Firebase App Check, user-specific database and storage paths, backend authorization for subscriptions and quotas, and HTTPS or TLS in transit. No system is completely secure.

LiftEats uses service providers that may process information in countries other than your own. Firebase Authentication is operated from United States data centers, and other Firebase or Google services may process information on global infrastructure according to their service settings and terms.

We may update this policy as LiftEats changes. The latest version will be published at this URL.

For privacy questions, support, or account-deletion help, contact support-lifteats@ahmadtariq.co.