Explicit Consent Text

The app offers separate settings for AI processing, analytics, and error reporting. The information/acceptance shown in the Movement feature is recorded with its version and date. The Movement record and the account-level AI-processing setting are separate from each other. This text explains the data processed, the purpose, the recipients, and the controls in the app. For details, see the Disclosure Notice.

A single consent screen is shown at entry. The app uses the general wording “our AI service providers abroad”; the provider names are listed here in this policy. Acceptance of the Terms of Use and Privacy Policy and explicit consent to processing health data such as weight, fasting, meals and steps to prepare your plan are required to use the app. AI processing (sending content to our AI service providers abroad for meal analysis, menu scanning and Momo Coach), and crash reporting and anonymous usage analytics are optional. “Accept and start” enables the optional permissions but does not turn on AI permission that an existing user previously turned off explicitly. “Choose and continue” starts optional switches off. Acceptance includes your declaration that you are 18 or older. You may close the app if you prefer not to accept. The accepted version, server date, language and permission choices are recorded on your account; guest or offline choices sync when a session and connection become available. You may withdraw optional permissions in Settings → My permissions. Turning AI off stops new coach processing; earlier encrypted audit records remain for the periods and purposes in this text. You can use account deletion to end required processing. Photo/route publication and leaderboard participation remain separate switches at the point of use; HealthKit/Health Connect and notification system permissions are managed separately.

1. Processing of Health Data and the Movement Record

The Movement information/acceptance is recorded with its version and date

Storage location: Account and Movement records are stored in the account-linked server database hosted by Supabase (EU/Frankfurt). Account-linked local copies may exist on the device so that the app can work.

Retention period: Movement profile, readiness, and session records are kept until the account is deleted and are deleted together with the account when the account is deleted. No shorter automatic retention period is applied to these records.

Transfer: Raw pain, body region, joint limitations, doctor restriction, pregnancy or postpartum indicator, raw readiness responses, and rule reason codes are not sent to Google Gemini. By contrast, the weekly health-related summaries listed one by one in Section 2 below are sent to Google Gemini (Google LLC, USA) while the AI-processing setting is on. If the analytics setting is on, limited Movement events may be sent to PostHog.

Apple Health / Health Connect: Health integration is optional. With the read permissions you choose, the app can read supported steps, active energy, workouts, weight, height, sleep, and resting heart-rate data and can transfer the data needed to provide the features to our servers (Supabase, EU/Frankfurt). Reading/synchronization and writing/export are separate controls in the app. Your logged meal energy and macros, water, and manual weight are written only while the account-level "Write to Apple Health" (iOS) or "Write to Health Connect" (Android) control is on and the related system write permissions have been granted. You can turn off either control in the app and revoke system access in iOS Settings > Privacy & Security > Health or in Health Connect on Android. This data is not used for advertising purposes. The weekly summaries produced from this data and listed in Section 2 may be transferred to Google Gemini while the AI-processing choice is on.

2. Choice of AI Processing and Transfer to the USA

Fields sent to our AI service providers and the account-level AI-processing setting

Before starting a food-text, food-image, or activity analysis request, the mobile client checks the account's AI-processing setting. The weekly server process sends a Gemini request only while the account value is true; a missing, false, or unreadable value blocks a new weekly Gemini request.

2.1 Food and Activity Analysis

2.2 Weekly Analysis

To create the weekly text, the following fields are sent to Google Gemini:

• Week information: weekKey, weekStart, weekEnd, daysCovered, coveredThrough, and tz
• Steps: Daily step series with date and weekday, average, goal, number of days the goal was reached, and low days with date/weekday/steps
• Active calories: Average active calories
• Sleep: Average hours, average bedtime minute, and number of days with data
• Meals: Total and daily average meals, snack count, late-night meal count and days, macro split, average daily kcal, evening calorie percentage, and the daily evening-percentage series
• Calorie balance: Calorie goal, daily intake and difference from the goal with date and weekday, and the average difference
• Water: Average ml, goal, number of days the goal was met, evening share, average minute of the first log, and morning share
• Fasting: Number of fasts started and completed, average actual and target hours, completion rate
• Weight: Start, end, change, goal, and number of logs
• Daily Movement and totals: movement.byDay[].date, weekday, minutes, neutral outcome, effort, and plannedMinutes; movement.daysMoved; movement.totalMinutes
• Movement outcomes and effort distribution: movement.outcomes.completed, partial, skipped, and rest; movement.effortDistribution.reported; the counts for ratings 1, 2, 3, 4, and 5 in movement.effortDistribution.byRating
• Movement effort at a comparable dose, if available: movement.effortAtComparableDose.dose.plannedMinutes, level, and volumeStep; previousAvg, currentAvg, delta, previousSamples, currentSamples, direction, and lookbackDays
• Movement progression: movement.progression.levelStart, levelEnd, and each levelChanges[].date, from, and to; volumeStepStart, volumeStepEnd, and each volumeStepChanges[].date, from, and to
• Movement/step correlation, if available: movement.correlations.steps.movementDaysAvg, nonMovementDaysAvg, difference, movementSamples, and nonMovementSamples
• Movement/fasting-hours correlation, if available: movement.correlations.fasting.avgHoursAtMovement, sampleDays, longFastDays, and longFastThresholdHours
• Movement/sleep correlation, if available: movement.correlations.sleep.beforeAvgHours, afterAvgHours, afterMinusBeforeHours, and sampleDays
• Meal plan: Planned and completed counts and adherence rate
• Request context: The derived count of field groups with data (dataDomains), the requested output language/locale, and static system instructions

2.3 Data Not Sent in the Weekly Analysis

Not added to the weekly request: Direct user or account ID, name, email, raw meal logs, raw readiness or body values, reason codes, pain flag, body region, rest reasons, readiness energy value, qualification data, and recent insight free text.

Contextual identification risk: Exact dates, time zone, and language/locale information remain in the weekly request. These are not direct identity information; however, they can contextually help to single out the person.

Retention and model use: Only Fasting does not store the weekly Gemini request text as a separate user record. Temporary retention, logging, and model use on Google's side are subject to Google's service settings and the applicable provider terms. This text gives no commitment about a specific provider retention period or about model training.

2.4 Momo Coach (AI Chat)

Scope: Momo Coach is an optional chat feature for Premium users aged 18 or older, where available. The entry consent bundle records your adult declaration and optional AI choice, including Momo Coach; the account-level AI-processing setting must be on. Older app versions may use the former separate coach notice.

Momo Coach recipients are Anthropic, PBC (Claude API) and Google LLC (Gemini API), in the United States. For users who accepted the current in-app consent text, Momo Coach's primary provider is, where available, Anthropic, PBC (Claude API), with Google LLC (Gemini API) as the fallback. When the fallback is used, the same message may also be sent to Google LLC (Gemini API). Momo Coach messages from users who accepted an earlier in-app consent text are processed by Google LLC (Gemini API) until they accept the current text. With each Momo Coach message, the following is sent to the provider processing the message:

• The message you write (up to 300 characters) and, for context, up to the last three questions and answers of the same chat
• A summary of your records for today, each of the last 7 days and a 28-day total: water, meals and logged calories, fasting, weight trend, meal-plan progress and, if connected, supported Apple Health / Health Connect totals such as steps and sleep, and the results of your recent weekly insights
• Your goals and plan settings, your diet-type and allergy selections, the date, your time zone and the app language
• The answer Momo prepares, which passes a second automated safety check before it is shown to you

Not sent: Your name, email, profile photo, direct user or account ID, friends, challenges, community posts, and free-text meal names and notes.

Retention: Unlike the weekly analysis, Momo Coach conversations are stored. For every request an encrypted record is kept with your message, Momo's answer or the fixed message shown, the record summary sent to the model, the model's raw output, the automated safety decisions, and technical details (model and instruction version, language, app version, platform, time, usage counts and cost). The chat history you see in the app is deleted automatically after 30 days; you can also delete it yourself at any time in the app with "Delete chat history". Deleting the visible history does not delete the encrypted Momo Coach record, which remains until the end of its retention period. The encrypted Momo Coach record is kept for 2 years and then deleted automatically; only where it is needed for a specific legal claim or dispute may it be kept until that matter is closed. If you delete your account, the visible chat history is deleted with it, while the Momo Coach record is kept until the end of its 2-year period under a pseudonymous code instead of your account ID. A pseudonymous code is still personal data. Usage-limit records (coded digests of your account and store-purchase identifiers, and a receipt per request) are kept for 32 days so that the limits cannot be bypassed, and are then deleted. Your like/dislike marks on answers are kept for the same period.

Purpose and access: Providing the chat and the chat history; checking and improving the quality and safety of answers; preventing misuse and enforcing the usage limits; and the establishment, exercise, or protection of a right. Only authorized persons can access the record, for these purposes, and every access is logged. The records are not sold and are not given to third parties to train AI models; improvement means internal review and adding de-identified examples to test sets.

Legal grounds we rely on: Your explicit consent given in the app for processing the health-related information in the chat and transferring it to Google LLC and Anthropic, PBC (USA) (KVKK Art. 6 and 9); legitimate interest for security and preventing misuse (KVKK Art. 5(2)(f)); and, for keeping the record after consent is withdrawn or the account is deleted, processing being necessary for the establishment, exercise, or protection of a right (KVKK Art. 5(2)(e) and Art. 6).

Withdrawing consent: You can withdraw your Momo Coach consent at any time in the app (you can also write to privacy@onlyfasting.com). After withdrawal, no new Momo Coach message is sent to our AI providers listed here; records already created are kept and deleted within the periods above. Temporary retention, logging, and model use on the provider's side are subject to the provider's service settings and the applicable provider terms; this text gives no commitment about them.

3. Analytics and Error Monitoring Choices

On by default; can be turned off under Profile > Privacy & Data

Analytics data: Usage events and limited event properties are sent to PostHog with the account-linked user ID. Email and name are not sent. Movement events may include energy, effort, date, general outcome, plan, level, and volume information. Raw pain, body region, body values, reason codes, and the decision rationale are not sent.

4. Changing the Choices

You can change the choices in the app at any time:

In the App

1. Open the Profile screen by tapping the profile button at the top of the page
2. Open Privacy & Data on the Profile screen
3. Turn off the relevant setting (AI Food Analysis, Usage Analytics, or Crash Reporting). For health synchronization, turn off the "Connect Apple Health" (iOS) or "Connect Health Connect" (Android) switch in the Health & Sync section of the Profile screen.

By Email

You can send an email to privacy@onlyfasting.com with the subject "Data processing choice".

5. Contact