Privacy Policy — Niulyfe

Niulyfe is a weight, nutrition and training app. This policy says what it collects, who receives it, why, and what you can switch off. Niulyfe is built for you, not for advertisers: there are no ads and your data is never sold.

Questions or requests: support@niulyfe.com.

Who Niulyfe is for

Niulyfe is for adults 18 and over. Do not use it if you are younger. If we learn that an account belongs to someone under 18, we delete it.

What you can switch off

Two things are off until you turn them on, on the consent screen and later in Settings, Privacy:

Usage Analytics sends us which screens and features are used, so we can see where people get stuck, with a few facts about you to group them by: your platform, whether you finished onboarding, your activity level, how you sign in, your sex, your age group, whether a health app is connected and your subscription plan. It also turns on Performance Monitoring, which measures how fast the app starts and runs.
Crash Reports send us what broke, with the device, app version, your subscription plan and a trace of the failure, so we can fix it.

We use Google Analytics for Firebase, Firebase Performance Monitoring and Firebase Crashlytics for these. We set no user ID on any of them, so the data is not tied to your account by us. Turn a switch off and the app stops sending at once. Nothing is sent before you turn it on, and your choice is stored with your account.

What we collect to run Niulyfe

The rest has no switch, because Niulyfe cannot work without it. Each item says what is sent, who receives it, why, and on what legal basis under the GDPR. "Contract" means we need it to give you the service you asked for.

Your account. Your email, name, password (Firebase keeps only a hash) and your sign-in method (email, Apple or Google), with your IP address and device details, go to Firebase Authentication, run by Google. Sign in with Apple goes through Apple, and Google sign-in through Google, under their own terms. We use it to create your account, sign you in and reset your password. Basis: contract.
Your plan and logs. Your profile (name, sex, height, birth year), weigh-ins, water, mood check-ins and their notes, steps and heart rate, workouts, programs, food logs, your library of favourites, custom foods and recipes, AI food log requests and results, settings and usage counts are stored in Cloud Firestore, run by Google, and sync across your devices. Weight, food, training, heart rate, mood and step data are health-related, so we process it with your explicit consent, which you give by accepting this policy on the consent screen. Basis: contract, and consent for health-related data.
Your consent record. The versions of the terms and this policy you accepted, when, on which platform and app version, and your two switches are kept with your account as proof. It stays after you delete the account. Basis: legal obligation.
Photos for AI food logging. A photo you attach to an AI food log is stored in Cloud Storage, run by Google, and deleted with that log. Basis: contract.
AI food logging. When you send an AI food log, your meal text, photo, market, time zone and meal time go to our Firebase Functions. The meal text and photo go on to Anthropic, which reads the meal, and the foods it finds are looked up in our food catalog with your market. Your name and email are not sent to Anthropic. Nothing goes to Anthropic unless you send a log. Basis: contract.
Monitoring the service. To fix problems, our backend records how each AI food log ran in Google Cloud Logging and Trace: the steps it took, the AI model, how much of the AI allowance it used, how long it took and any error. It does not record your meal text, your photo or the AI's answer there. Some of our backend's log lines carry your account ID, and they are kept after you delete your account. The check before an AI food log adds your subscription plan and the AI allowance it reserves, and cleaning up a deleted AI food log adds its photo's path if it had one. For each call the app makes to our backend, including deleting your account, Google Cloud's request logs record your IP address and the app's user agent (which app and system made the call). These copies are kept for Google Cloud's log retention period and are not removed when you delete a log or your account. Basis: legitimate interest in running and fixing the service.
Checking the app is ours. App Check asks Apple (App Attest) or Google (Play Integrity) for a token that shows the call comes from a genuine copy of Niulyfe on a genuine device. Basis: legitimate interest in keeping the service secure.
Fetching settings. Each launch, Firebase Installations and Remote Config, run by Google, receive an installation ID, the app and OS version, your language and country, your time zone and your IP address, and send back the current configuration, including the version of this policy and the terms. Basis: legitimate interest in running and updating the app.
Your subscription. RevenueCat handles purchases and restores. It receives an anonymous ID before you sign in and your account ID after, your store receipt, your IP address and your device model, OS and app version. Its Firebase extension writes your purchase status back to your account. Deleting your account deletes your RevenueCat customer, which holds your account ID and purchase history, and the purchase status with it. It does not cancel your subscription: you cancel that in your store, and Apple or Google keeps its own records of your purchases. Basis: contract, and legal obligation for payment records.
Shared workouts. A workout you share is a record with your account ID that anyone signed in who holds its link can open. It is deleted with your account. Basis: contract.
Food search. The text you search for, your market and your IP address go to our own search server. No account ID is sent. Basis: contract.
Barcode scans. When you scan a barcode, the barcode, your language and country, and your IP address go to Open Food Facts, an independent open food database, which also serves the product photos. Basis: contract.
Dictation. When you tap the microphone, your phone's own speech service (Apple's, or Google's on Android) turns your voice into text under its own terms. We receive only the text. Basis: contract, and your permission to use the microphone and speech recognition.
Health sync. If you connect Apple Health or Health Connect, Niulyfe reads steps, weight and heart rate from it, and writes weight, nutrition and exercise to it. What it reads is saved to your plan and logs above, so it syncs with your account; what it writes goes only to your phone's health store. You can turn the connection off in Settings and in your phone's health permissions. Basis: your permission.
Reminders. They are set and shown by your phone. No server sends them and no device token is kept.
Pictures and video. Exercise images and videos load from Cloud Storage, which sees your IP address as it does for any download. Basis: contract.

The App Store and Google Play handle your payment and see your purchases under their own policies.

Keeping and deleting your data

You can delete your account in Settings. That removes your profile, logs, plans, photos, purchase status and shared workouts and your sign-in. Your consent record stays, as above, and so do the monitoring copies. We also delete your RevenueCat customer first, so a failure there stops the deletion and you can try again. Your subscription keeps renewing until you cancel it in your store, and the store keeps its own records. Copies you shared that a friend saved are the friend's own.

Your rights

Where the GDPR or a similar law applies, you can ask us for a copy of your data, to correct it, to delete it, to restrict or object to its use, and to take it with you. You can withdraw consent at any time, which does not undo what was done before. You can also complain to your data protection authority. Write to support@niulyfe.com.

Changes

When this policy changes in a way that matters, the app asks you to read and accept it again, and says what changed.