Fasting AI keeps your fasting data local-first.
Effective date: 2026-04-05. Fasting AI is designed to keep your fasting, food, exercise, and profile data on your device unless you choose a feature that requires a third-party service or you share content yourself.
What Fasting AI stores on your device
- Profile settings, onboarding choices, fasting sessions, food logs, and exercise logs.
- Appearance preferences, onboarding completion state, and premium state.
- An anonymous app user identifier stored locally in Keychain and UserDefaults.
Health data
If you grant permission, Fasting AI reads step count from Apple Health. Step data is processed locally for calorie and fasting guidance and is not uploaded to our own backend.
AI meal photos
If you choose AI meal photo estimation, the selected image is normalized, cropped when needed, resized, and compressed on your device before it is sent to Google's Gemini API for a one-time nutrition estimate. We do not store meal photos on our own servers, but the submitted image is sent to that third-party provider to generate the result.
Sharing
If you choose to share a daily recap, the generated image may include meal, fasting, and step information from your device. Share assets are prepared locally and are only sent to another app or service when you trigger the share action.
Purchases and subscriptions
Subscriptions are handled through the App Store and RevenueCat. The local anonymous app user identifier may also be used as the RevenueCat app user ID so purchases can be restored. We do not store payment card information.
Analytics and logging
Fasting AI does not include a third-party analytics SDK. Debug file logging is limited to debug builds. Release builds may still emit limited OS-level runtime logs for operational events such as errors or purchase flow state, without storing full meal photos or full personal identifiers in our own backend.
Questions
Questions about privacy can be sent to karahan.harunn@gmail.com.