1. Who operates YanliFit and what this covers
YanliFit is operated by the developer of the YanliFit application.
YanliFit email support is temporarily unavailable while we complete the public launch. A dedicated support address will be published here before the app is released publicly.
Production account deletion is temporarily unavailable while its required backend migration and deletion function await separate deployment approval.
This policy covers the YanliFit mobile application and this website. The website is static: it does not use analytics, advertising pixels, account sessions, contact forms, or cookies, and it does not collect support messages.
2. Information the application handles
Account and profile
Using YanliFit requires an account. YanliFit handles your email address, email-verification state, authentication identifiers, profile settings, body measurements, fitness preferences, and goals. Email sign-in and account re-verification may use a six-digit one-time code. Never send that code to support.
Nutrition and daily records
Your YanliFit account may contain foods, meal timing, calories, macronutrients, available advanced nutrients, portions, water, body weight, and YanliFit-owned step records. Food entry can be manual, AI-assisted from an image or text, barcode-based, or based on nutrition-label recognition.
Training and progress
YanliFit may store strength plans and sessions, exercises, sets, repetitions, load, perceived effort, cardio session details, goals, achievements, and streak-related progress. Cardio may use foreground location access to help determine distance while a session is active; YanliFit does not currently save a route map.
Local device information
The application uses local storage for settings, caches, recent Coach conversation history, notification preferences and reminder state, and other data needed to operate on the device. Local notifications, when enabled, are scheduled by the application; YanliFit does not currently use an advertising or third-party analytics SDK.
YanliFit does not currently offer a production paid subscription. If subscriptions are introduced, YanliFit and its payment provider may process entitlement and transaction information under updated disclosures and the provider's terms.
3. AI, barcode, and nutrition-label processing
Food image and text analysis
When you choose AI food analysis, YanliFit sends the submitted meal description or a compressed copy of the selected food image, together with relevant meal context, through a YanliFit Supabase Edge Function to Google Gemini. The result is an estimate that can be reviewed and edited before saving. It is not a clinical measurement.
YanliFit’s product database is not designed to retain the raw AI food image or raw meal description after the request. It may retain the food record you choose to save and operational metadata such as request timing, model usage, status, and account usage. Google and Supabase may process request data and keep service or security logs under their own terms and configured service settings.
YanliFit Coach and generated workouts
When you message YanliFit Coach, the current message, recent conversation context, and relevant fitness context can be sent through YanliFit’s backend to Google Gemini to generate a reply. Recent chat history is also stored locally on your device. Certain workout-generation features can use the same processor. Do not treat generated output as medical diagnosis or treatment.
Barcodes and labels
For barcode lookup, the scanned code can be sent to Open Food Facts through YanliFit’s backend. Product responses may be stored in a shared cache so repeat lookups work efficiently. Nutrition-label text recognition is performed on-device with ML Kit; information you choose to save can then become part of your YanliFit food record.
Community food contributions
If community-food submission is enabled in the application and you submit a food, the submission may be reviewed, rejected, grouped, or promoted into shared food data. A shared food contribution may remain after its account identifier and submission metadata are removed. This can include non-account food details such as locale, country, raw food name, brand, and nutrient fields. YanliFit does not represent that remaining contribution as your private food history.
4. Health Connect
On supported Android devices, YanliFit can request permission to read step data from Health Connect. The current integration imports steps for a trailing period of up to 30 days and can store those imported copies in your YanliFit account. Health Connect access is optional and permission-controlled.
You can revoke YanliFit’s permission through Android or Health Connect controls. Deleting your YanliFit account removes YanliFit-owned imported step records and revokes YanliFit’s connection where supported, but it does not delete provider-owned records held by Health Connect or the apps that originally wrote them. HealthKit access is not currently available in the iOS implementation.
5. Progress photos
Progress photos and their thumbnails are stored in the application’s private document storage on your device. The progress-photo feature is not designed to upload them to Supabase or send them to Gemini. You can remove them through YanliFit’s local Data controls or by removing the application; the pending account-deletion implementation is also designed to clear them after a successful deletion.
Your operating system, device-management software, or a device backup may have behavior outside YanliFit’s control. Use your device’s privacy and backup settings if you need to manage copies held outside the application.
6. Why information is used and who processes it
YanliFit uses information to authenticate accounts, keep user-selected records synchronized, provide nutrition and training features, answer Coach requests, import permitted step data, prevent abuse, maintain reliability, respond to support, and comply with applicable obligations.
- Supabase provides authentication, database, and serverless processing infrastructure.
- Google Gemini processes information submitted to AI food, Coach, and certain generation features.
- Open Food Facts receives barcode identifiers for product lookup.
- Google ML Kit supports on-device nutrition-label recognition.
- Android Health Connect provides permitted step data on supported devices.
These providers may process data in countries or regions where they operate. Their infrastructure, security logging, and retention practices are also governed by their terms and YanliFit’s configured service settings. The current service does not include advertising, data-broker, session-replay, or third-party analytics integrations.
7. Retention and account deletion
Production account deletion is not operational yet. The deletion behavior below describes the reviewed implementation that remains pending separate backend deployment approval and production verification.
Account-owned cloud records are generally kept while your account is active and until you delete them or your account. Local data remains on the device until it is removed by the application, account deletion, application removal, or device controls. Operational, abuse-prevention, and provider logs may follow separate security and service retention periods.
Successful account deletion removes your Supabase authentication identity and account-owned profile, goals, food, water, weight, steps, workout, AI-account-usage, entitlement, and relevant private submission records. It also clears YanliFit’s local account caches, progress photos, and account-specific reminder state.
Some shared data may remain: promoted community-food information after account identifiers and submission metadata are cleared; canonical food and alias data; shared barcode cache entries; aggregate install or monthly counts; and abuse-prevention records keyed by pseudonymous install or network hashes. Current network-hash records do not have a fixed public purge schedule.
A non-identifying completed deletion receipt has a seven-day retry window. Expired receipts are purged during subsequent deletion processing, so deletion processing does not promise deletion at the exact seven-day mark. If recovery is needed after an interrupted deletion, a cleanup record may temporarily retain the account identifier until processing completes. Supabase authentication or infrastructure logs, and processor logs outside YanliFit’s product tables, may follow provider retention.
See the account deletion instructions for the exact in-app flow and current support availability.
8. Your controls and requests
You can review and edit many records in YanliFit and control Health Connect and notification permissions through your device. The app contains an account-deletion control, but the production backend cannot complete deletion yet.
Production account deletion is temporarily unavailable while its required backend migration and deletion function await separate deployment approval.
When a dedicated support address becomes available, YanliFit may need to verify that a requester controls the account before acting. Applicable privacy rights vary by location; this policy does not claim certification under a particular privacy or healthcare framework.
9. Policy updates
This policy may change when YanliFit’s features, providers, or legal obligations change. The effective and last-updated dates at the top will be revised when material text changes. Where appropriate, additional notice may be provided in the application.
10. Contact
YanliFit email support is temporarily unavailable while we complete the public launch. A dedicated support address will be published here before the app is released publicly.
Production account deletion is temporarily unavailable while its required backend migration and deletion function await separate deployment approval.
When support becomes available, do not include passwords, one-time codes, payment-card details, JWTs, or unrelated sensitive health information.