SnapCal Privacy Policy

This policy applies to the SnapCal mobile app, operated by Mobtive. It is separate from the policy covering the mycookingcalendar.com website and from the ones covering our other apps — each is a different product with different features, so each gets its own policy.

SnapCal is a tracking tool for meals, fasts and water. It is not a medical service, it does not give medical or dietary advice, and its calorie figures are estimates rather than measurements.

Unlike a purely on-device tracker, this app is account-backed by design: what you log on your phone is the same data you see when you sign in on the website. The following is written to your device and also synced to our servers in Germany:

• Meals you log — the name, the date and time you ate, the meal type, and the calorie and macronutrient figures
• Whether each figure came from a photo estimate, a text estimate or your own typing, and the original estimate before you edited it
• Fasts — protocol, start and end time, target length, whether you completed it, and any notes
• Water you log — the amount and when, plus your daily goal and glass size
• Any calorie target, and the height, weight, age and activity level you enter to derive one

The app keeps a copy on your phone so the fasting timer, water logging and manual meal entry keep working with no network connection. Entries you make offline are uploaded when you reconnect.

When you photograph a meal, the image is sent to our server and forwarded to OpenAI, which returns an estimate of what the food is and roughly what it contains. We do not keep the photo. It exists only for as long as the request takes, is not written to our storage, and is not attached to your saved meal.

What we do keep is the estimate itself — the food names and numbers the model returned — stored alongside your meal so you can see what was suggested before you edited it. Per OpenAI's API terms, content sent through the API is not used to train its models.

Photo estimates are guesses made from a picture and can be wrong, sometimes substantially. Every value is editable before you save it. Treat them as a starting point, not a measurement.

You can start using the app immediately without giving us anything. On first launch it creates an anonymous account identified only by a random identifier, so your entries have somewhere to live.

If you later sign in with Apple or Google, we receive the identifier that provider gives us and, if you allow it, your email address. We use the email to identify your account and to reach you about the service. We never see your Apple or Google password. Authentication tokens are held in your device's secure keychain.

Signing in also links the app to your mycookingcalendar.com account, which is what lets the same meals, fasts and water appear in both places.

When you type a food description to get a calorie estimate, that text is sent to our server and forwarded to OpenAI to produce the estimate. Meal titles and fasting notes you save are stored with your entries and are not sent anywhere else.

Before the fasting features unlock, the app asks whether you are under 18, pregnant or breastfeeding, have diabetes or take blood-glucose medication, have a current or past eating disorder, or believe you are underweight.

Your individual answers are held in memory only while you are on that screen. They are never written to storage, never sent to us, and never sent to any third party. Only the outcome is recorded — that the screening did or did not block the feature — without the answers behind it.

We use Firebase Analytics and Firebase Crashlytics (both Google) to understand how the app is used and to find crashes. Events record that an action happened — completing onboarding, analysing a photo, logging or editing a meal, starting or ending a fast, logging water, opening an analytics screen, viewing or dismissing the paywall, completing or failing a purchase, exporting your data, deleting your account.

These events carry coarse context such as which module you were in. They do not carry your meal names, calorie figures, notes, weight or screening answers. Crashlytics collects diagnostic information about crashes, including device model, operating system version and a stack trace.

The free tier shows ads supplied by Google AdMob: a banner on the daily summary and meal list, and an optional rewarded video you can choose to watch for extra photo scans. There are no full-screen interstitials, and no ads appear on the photo-analysis result screen or on the fasting timer.

On iOS the app asks for your permission through Apple's App Tracking Transparency prompt before the ads SDK starts. If you allow tracking, AdMob may use your device's advertising identifier to personalise and measure ads. If you decline, the app works exactly the same and you get non-personalised ads.

If you have a paid subscription the ads SDK is not started at all. We do not use your meal, fasting, water or body data to target advertising, and we do not share that data with advertising partners.

Paid features are sold as auto-renewing subscriptions through the Apple App Store and managed with RevenueCat. Each module can be bought separately or all together. We receive your subscription status, which products you hold and transaction identifiers, so the app can unlock what you paid for. We do not receive or store your payment-card details — Apple handles the payment. Renewal and cancellation are controlled from your App Store account settings.

We do not sell your personal information, we do not use your health or nutrition data for advertising, and we do not share your entries with anyone outside this table.

• Export — Settings can write your meals, fasts and water history to a file you can keep or share.
• Delete — you can delete your account and everything attached to it from Settings. This is immediate and cannot be undone. Uninstalling the app alone removes only the on-device copy.
• Edit — every estimated figure is editable, and any entry can be deleted individually.
• Tracking — you can change the advertising-tracking permission at any time in your device's privacy settings.
• Notifications — fasting and water reminders are opt-in and can be turned off in the app or in your device settings.

Depending on where you live, you may also have rights under the GDPR, the CCPA/CPRA or Türkiye's KVKK, including rights of access, correction, deletion, portability and objection. Email bugra@mobtive.com and we aim to respond to verified requests within 30 days.

Your entries are kept until you delete them or delete your account. Deleting your account removes your meals, fasts, water history, profile and preferences from our database. Crash reports and analytics are retained according to Google's Firebase retention settings. Subscription records are retained as long as we are required to keep them for tax and accounting purposes.

This app is not intended for anyone under 18. The screening in onboarding asks about age and blocks the fasting features if you indicate you are under 18. We do not knowingly collect personal data from children.

If we change what the app collects — for example if we ever begin storing your meal photos — we will update this page and the date at the top before that change ships.