Privacy Policy
Last updated: 2026-10-29
WellBite (“we”, “us”) is a nutrition tracking app operated by Ilsur Gabdulkhakov, an independent developer. This policy explains what we collect, why, and your choices. Short version: your data stays on your device first and is backed up privately to your account, the copy of a photo sent for AI analysis is discarded, we don’t sell your data, and there are no ads.
Information we collect
You provide:
- Goal-quiz answers: sex, age, height, weight, activity level, and your goal (bulk, cut, maintain, weight loss, GLP-1 support). Used solely to compute your protein and calorie targets.
- Food logs: meals, dishes, recipes, pantry items, custom foods, portion weights, and body-weight entries.
- Meal and nutrition-label photos you choose to take, and barcodes you scan.
- If you choose to sign in with Apple or Google: the email address and name that provider shares with us (with Apple you can hide your real email). Signing in is optional.
Created automatically:
- An account identifier (Firebase UID). WellBite works without a signup — the app starts with an anonymous account, and no name or email is required unless you choose to sign in.
- AI request metadata: a daily counter and request log used to apply the AI scan allowance (3 scans on the free plan, fair use of up to 100 a day on Premium — see the Terms) and for abuse prevention and cost control.
- Subscription status: whether Premium is active and when the current period ends (see Subscriptions).
- Usage analytics and crash reports (see Analytics & crash reports).
- Food searches that find nothing: the words alone, without your account (see Analytics & crash reports).
Analytics & crash reports
We use Firebase Analytics to understand which features help people reach their protein goal — for example, that onboarding was completed, a meal was logged (and how: photo, label, barcode, search, dish), a daily protein goal was hit, or the paywall was shown. Events carry counts and categories only — never food names, photos, body measurements or health data — plus coarse device information (model, OS version, country, app version). We set your goal type, units, Premium status and whether you’re signed in as properties to segment these numbers. Advertising identifiers (IDFA, Android Advertising ID) are not collected, analytics are not linked to your email, and nothing is used for advertising or shared with ad networks.
Firebase Crashlytics collects crash reports and error diagnostics (stack traces, device model, OS version, app version, and your account identifier so we can fix a problem you report).
Searches that find nothing. Food searches are matched by their words on our own server and are never sent to an AI service. When a search finds nothing, our server keeps the words you typed with the day, the app’s language and your country — not your account identifier, device or IP address, so a record can’t be traced back to you. It tells us which foods the catalog is missing. Words that look like contact details (an email or web address, a long number) are not kept, and the records are deleted after 180 days.
You can turn all of this off at any time in Settings → Share usage data: nothing more is sent to analytics or crash reporting, and searches that find nothing are no longer kept.
Photos
AI analysis. When you scan a meal or a nutrition label, the photo is sent to our servers to be analyzed by an AI model that recognizes foods and estimates nutrition. That copy is processed and discarded — we keep only the structured result (food names, grams, macros). Your scan history (the last 50 scans) stays on your device. AI nutrition estimates can be inaccurate — they are editable and provided for information only.
Photo backup. The photos you keep in WellBite — a meal you log from a photo, and photos you add to dishes and custom foods — are saved on your device as a compressed copy (up to 1000 pixels on the longer side, plus a small preview) and backed up to our server, so they come back if you reinstall the app and appear on your other devices. They are stored privately in Google Cloud Storage under your account identifier, are never public, and are only sent back to the app signed in to your account. When you remove a photo, or delete the entry, dish or food it belongs to, its backup copy is deleted the next time the app syncs; deleting your account deletes all of them.
How we use information
- Compute your targets and power tracking, suggestions, and the Gap Closer feature (which runs on your device).
- Back up your logged data and the photos you keep (keyed to your account ID) so they can be restored if you reinstall, and keep them in sync across your devices when you sign in.
- Let you sign in and recognize your account on another device.
- Maintain, debug, and improve the app (server error logs, crash reports, aggregated usage analytics).
- Prevent abuse of the AI features.
We do not sell personal information, share it for advertising, or show ads.
Subscriptions
Payments are processed by Apple App Store or Google Play — we never see your payment details, name or Apple ID. We use Adapty to manage subscriptions: the Adapty SDK in the app sends Adapty your anonymous ID and your store purchase receipts, and Adapty tracks which products you bought and whether your subscription is active.
Our server keeps one record per account: whether Premium is active and when the current period ends. Adapty sends us this status when it changes, and our server can also ask Adapty for it directly, for example right after a purchase or a restore. We store nothing else about your purchases (no prices, products or transaction history). The record is deleted with your account.
Third-party services
| Service | Purpose | What it receives |
|---|---|---|
| Firebase Authentication (Google) | Account sign-in (anonymous, Apple or Google) | Account UID; email and name if you sign in |
| Firebase Analytics & Crashlytics (Google) | Usage analytics and crash reports | App events, device info, account UID (crash reports) |
| Google Cloud | Hosting of our API, the backup database and photo storage (United States) | Anonymous UID, your backed-up logs and photos |
| Cloudflare | Network delivery of our API, website and app updates | Request metadata (e.g. IP address) |
| OpenAI | Photo → nutrition analysis | The photo (transient) and your device’s locale/time zone; no account identifiers |
| Open Food Facts | Product lookup when a barcode isn’t in our database | The barcode number only |
| Adapty | Subscription management | Anonymous UID, store purchase receipts, subscription status |
| Apple, Google | Payments, receipts, Apple Health, Sign in with Apple / Google | Handled under their own policies |
Health data
Your quiz answers, food logs, and weight entries are health-related information. We use them only to provide the app’s features, never for advertising, and never share them except with the processors listed above as needed to run the service.
Apple Health. If you allow it, WellBite reads your active energy, resting (basal) energy and step count from Apple Health to show your daily calorie balance. It never writes to Apple Health. Health data stays on your device: it is not sent to our servers or to any third party, and it is never used for advertising or sold. You can revoke access at any time in iOS Settings → Health → Data Access & Devices.
Retention & deletion
Your data lives primarily on your device. The server backup is retained while your account is active. Settings → Delete account erases your server backup (photos included), usage records, subscription-status record, and the account itself, including the email and name from sign-in (a Sign in with Apple authorization is revoked too); deleting the app removes all local data, including scan history. If you also use Batyr, our workout app, with the same account, Delete account deletes your Batyr data too, as Batyr’s Privacy Policy describes. Signing out erases the data on that device while your account keeps it. You can also email us (below) or use wellbite.app/delete-account to request deletion. Analytics data is kept by Google for up to 14 months; crash reports for up to 90 days; searches that found nothing, which aren’t linked to any account, for 180 days.
Your rights
Depending on where you live (e.g. GDPR, CCPA/CPRA), you may have rights to access, correct, export, delete, or restrict processing of your personal information. Because WellBite is anonymous-first, most data is directly visible and editable in the app; for anything else, contact us and we will respond within 30 days. We do not discriminate for exercising your rights. California residents: we do not “sell” or “share” personal information as defined by the CCPA.
Children
WellBite is not directed to children under 13, and we do not knowingly collect their data. If you believe a child has used WellBite, contact us and we will delete the data.
Security
Data in transit is encrypted (TLS; our domain enforces HTTPS). Server access is restricted, and every request is authenticated with a short-lived token tied to your account.
International transfers
Our servers are located in the United States. If you use WellBite from elsewhere, your information is processed in the US under this policy.
Changes
We’ll post updates here and update the effective date; material changes will be announced in the app.