Privacy policy

Information EatLose uses

• Account information: your email address, account identifier and the profile details you choose to provide.
• Meal, weight and plan records: confirmed meals and nutrition values, weight entries, goals, daily summaries and consent choices needed to provide the app.
• Meal analysis inputs: a resized photo, voice transcript or text description collected directly from the content you select or enter, only when you ask EatLose to analyse a meal.
• Weekly review inputs: when you choose to generate an AI weekly review, EatLose derives only the minimum necessary confirmed summaries from your private account history: meal and nutrition aggregates, weight trend, confirmed intake, energy target, activity energy and data completeness.
• AI safety reports: when you choose to report an AI result, EatLose stores your selected reason and an allowlisted copy of that generated meal estimate or weekly summary. The report does not include your original prompt, photograph, voice audio or raw health records.
• Optional health information: only the Apple Health or Health Connect categories you choose to permit, such as weight, height, steps, active energy, resting energy and workouts.
• Purchase state: the minimum App Store or Google Play transaction information needed to verify and restore an EatLose Plus entitlement.

How information is used

Information is used to operate and secure your account, estimate your daily energy balance, show confirmed history and trends, provide the features you request, verify plan allowances, process account controls and understand technical failures. EatLose does not use health data for advertising or sell it.

Apple Health and Health Connect

Access is optional, granular and revocable in your device settings. Raw health records are read locally by the app and are never sent to an AI provider. If you grant write access, EatLose writes meal nutrition only after you review and confirm the meal, and writes weight only after you choose to save a weight entry; an AI draft is never written automatically. EatLose may synchronise only the profile values, confirmed weight entries and daily summary values needed to provide your account history across the service. Manual meal and weight logging remain available if you decline access.

AI meal analysis and weekly reviews

Named recipient: EatLose offers two separately disclosed AI-processing regions. International AI processing uses Google Gemini, provided under EatLose’s UK account by Google Cloud EMEA Limited. Mainland China AI processing uses Alibaba Cloud Model Studio Qwen in Beijing, contracted through 通义云启（杭州）信息技术有限公司. Before the first transfer, EatLose shows the selected processor and region and asks for a provider-specific, withdrawable permission. Changing the app language does not change the processor, and switching AI-processing region requires a new permission. This choice applies to the named AI processor and does not mean that the separate EatLose account backend is hosted in mainland China.

When you choose to analyse a meal, EatLose sends your selected text, editable voice transcript or temporary resized photograph through EatLose’s secure service only to the processor named in that permission, to produce the editable estimate you requested. When you choose to generate a weekly review, it sends only the minimum necessary confirmed summaries: meal and nutrition aggregates, weight trend, confirmed intake, energy target, activity energy and data completeness. Individual raw Apple Health and Health Connect records are never sent to either AI processor.

Google processes this information only to provide and protect the Gemini API service under its applicable Gemini API terms and data-processing terms. Google is required to provide the same or equivalent protection for this personal data as described in this policy. Under the terms applicable to this service, prompts and responses are not used to improve Google products. Google may retain prompts and responses for up to 55 days solely for abuse monitoring, service security and required legal disclosures, as described in its abuse-monitoring notice. EatLose does not enable model tuning, grounding, persistent interactions or the Gemini File API for these requests.

Qwen processes requests for the Mainland China AI-processing option through EatLose’s dedicated Alibaba Cloud Model Studio business workspace in Beijing. EatLose does not create a knowledge base, start a fine-tuning job or authorise Alibaba Cloud to use these requests for model training or optimisation. Alibaba Cloud’s official Model Studio privacy notice states that transmitted data is encrypted with AES-256. Its applicable Model Studio service agreement says customer business data is not used or disclosed without authorisation except to provide the service, meet content-safety obligations or comply with law; conversation data is retained only for the shortest period necessary to provide the service, while model and application call data may be stored where legally required. Under these contractual safeguards, Alibaba Cloud is required to provide the same or equivalent protection for this personal data as described in this policy.

On iOS, Apple speech recognition may process microphone audio on the device or through Apple to create a transcript. On Android, voice input is available only on Android 12 or later when the device reports on-device recognition support; EatLose uses only the on-device recognizer and never falls back to a network or cloud recognizer. EatLose does not store voice audio.

A generated meal estimate remains a draft and does not change your diary until you review and confirm it. EatLose does not sell meal content or use AI inputs for advertising.

If you report an AI result in the app, the report is linked to your EatLose account and is available only to the authorised EatLose Studio operator through restricted server-side moderation access. Reports are reviewed for safety and quality and are deleted automatically after 90 days, or sooner when you delete your account.

Storage and deletion

Account and confirmed app records are stored with service providers needed to operate EatLose. Meal photographs are placed in private temporary storage for the analysis you request and are removed after that workflow, with an additional stale-file cleanup safeguard.

When you delete your EatLose account, the app requests deletion of your profile, diary, consent choices, usage records, AI safety reports and private meal images. Where an active App Store or Google Play subscription exists, EatLose may retain only the minimum store transaction and status record needed for store notifications, fraud prevention and a verified restore, without keeping it linked to a usable app profile. That ownerless store record and any matching Google Play purchase token are deleted 30 days after the subscription period ends, or 30 days after the record’s last update when the store provides no period end. Pseudonymous Google Play notification metadata expires after 90 days. Limited backups may remain only for service recovery or legal obligations and expire under the hosting provider’s controlled schedule.

Your choices

You can decline or revoke health access, use manual logging, edit or discard an estimate, withdraw in-app health or AI-processing consent, export your data and delete your account. Device permissions and EatLose processing choices are managed separately so you can change either later.

Age and wellbeing

EatLose is intended for adults aged 18 and over and provides general wellness guidance. It does not provide medical advice, diagnosis or treatment.

Contact

For privacy questions, data requests or product help, email [email protected].