Consumer Health Data Privacy Policy

This policy applies to consumers in Washington, Nevada, Connecticut, and any other US state with a consumer health data law, and supplements our Privacy Policy. It is provided by Illia Kyselov, sole proprietor (FOP), Kyiv, Ukraine, support@calsn.app.

We collect:

• —Body and goal data. Sex, date of birth, height, current weight and weight history, activity level, weight goal, and any calorie target you set.
• —Food photos and estimates. Photos of food you log and the estimates of their calorie and macronutrient content, which are calculated from the foods and portion sizes the AI identifies in them.
• —Meal-log entries. Food names, portions, nutrition values, and times.
• —Water intake. The amount of water you log (in millilitres), the day it counts toward, and the time you logged it.
• —Corrections and feedback. Your corrections to estimates and "wrong result" feedback.
• —Fasting and eating-window data. If you turn on fasting: the eating-window schedule you choose (protocol, window time, days), when each fast starts and ends, why it ended, and whether a logged meal ended it.
• —Target weight and pace. In App version 1.0.1 and earlier these are stored only on your device and never sent to our servers. From App version 1.0.2 they are synced to our servers together with the rest of your body and goal data.

Apple Health. App version 1.0.1 and earlier do not access Apple Health. From App version 1.0.2, only if you choose to connect it, the App reads your step count, workouts and active energy from Apple Health, to show today's activity and to add the calories you burned to your daily calorie budget. This data is read and used only on your device: it is not sent to our servers, to the AI service, or to our analytics and crash-reporting providers. The App never writes to Apple Health, and you can revoke access at any time in the Health app or in iOS Settings.

Fasting is not medical advice. Calorie Snap is not a medical device and does not provide medical advice. Fasting isn't suitable for everyone. Consult a doctor before changing your eating pattern.

Directly from you: when you enter your profile, take or select a photo, log or edit a meal, log water, set up or change a fasting schedule, or submit feedback. We do not obtain consumer health data from any other source and do not infer health conditions from your data.

• —To calculate your daily calorie and macronutrient targets.
• —To recognise food in your photos and estimate its nutrition.
• —To keep your food diary, water log and weight history, and to keep a server copy so your log survives reinstalling the app on this device.
• —To measure and improve recognition accuracy (using your corrections and feedback; not to train AI models).
• —To run the fasting feature when you turn it on: to show where you are in your eating window and to tell you whether a meal you logged ended a fast.
• —To secure the service and prevent abuse.

We do not use consumer health data for advertising, marketing, or profiling, and we do not sell it.

We share consumer health data only with processors acting on our behalf, under contracts that restrict their use to our instructions:

Amplitude runs in three places on the same project key. On our backend, every food-photo recognition runs inside an Amplitude analytics session keyed to your account id — not an anonymous reference — and that session receives the model's entire response, which includes the nutrition estimates in the table above. In the iOS app, the same project also receives product-usage events, linked to your anonymous account id, that never include food names, weights, or photos but do include some health-related values. These events include: the calories of a meal that breaks a fast, the planned and actual length of a fast in hours, your fasting protocol and eating window, water logging events, when a fasting session starts or ends, when a plan is paused, an end time is edited, or a break is overridden, when fasting data is deleted, and whether fasting setup was blocked (because of your age, a health screening answer, or a declined consent). From App version 1.0.2, these events also carry your answers to the onboarding questions, also stored as properties of your anonymous analytics profile: how many workouts you do a week, your goal (lose / maintain / gain), your diet type, what gets in your way, what you would like to achieve, whether you have tried other calorie apps, whether you work with a trainer or dietitian, where you heard about the App, and whether you turned on the optional features of adding burned calories, connecting Apple Health, and rolling over unused calories. Your height, weight, target weight, date of birth, sex and pace are not sent to analytics. This list is not exhaustive and can grow as features are added. Amplitude also derives an approximate location (country, region, and city) from the IP address of each request. On this website, it records page views only, with no click or form capture, no session replay, and no cookie or persistent browser ID; each page view includes Amplitude's default device properties (browser type, operating system, language). In the iOS app, Amplitude Session Replay also records masked replays of in-app screens and interactions (taps and navigation) to help us understand how the product is used and to debug problems. Text you type, the camera view, and all food photos are masked (replaced with placeholders) before leaving your device. Because the masking covers typed text, the camera view and photos but not every number on screen, these recordings can include health values shown on screen, such as calorie totals, weight entries and fasting timers. Replays are tied to your anonymous account id, kept per Amplitude's retention policy, used for product analytics and debugging only, and deleted on request to support@calsn.app.

We do not share consumer health data with affiliates (we have none), advertisers, data brokers, or any third party for their own purposes. We may disclose it if required by law or to protect the safety of a person.

We do not sell consumer health data, and we will not sell it without first obtaining your separate, written, signed authorization as required by law.

We collect your body and goal data because you enter it yourself in onboarding, where the specific data and purposes are described. Recognition of food photos by Google requires your permission: the welcome screen shows, directly above the "Get Started" button, a notice that meal photos are analyzed by a third-party AI (Google Gemini) with links to the Terms and Privacy Policy, and tapping "Get Started" gives that permission. If permission was never given, or the "AI photo analysis" toggle in Settings is off, the camera asks (Allow / Not now) before sending a photo. You can withdraw or grant this consent at any time with the "AI photo analysis" toggle in Settings, and you can withdraw consent for your other consumer health data by deleting it in Settings → Account → Delete Account. Withdrawal stops future collection and processing but does not affect what was already lawfully done. Manual meal logging works without photo consent.

Fasting is off by default. We ask for your consent on a separate screen before any eating-window data is stored, and turning fasting on is the only thing that starts that collection.

You have the right to:

• —confirm whether we collect, share, or sell your consumer health data and to access it, including a list of third parties and affiliates with whom we have shared it (Section 04);
• —withdraw consent to collection and sharing;
• —delete your consumer health data. Deleting your data in Settings → Account → Delete Account removes it from our database and photo storage. Amplitude records, which are linked only to a random account ID, are deleted on request to support@calsn.app;
• —not be discriminated against for exercising these rights.

You can delete all fasting data on its own, without deleting your account, from Settings → Fasting plan → Delete all fasting data. It is removed from your device and from our servers.

Because your account is anonymous, the most reliable way to exercise these rights is from inside the App — Delete Account, Export data, and the "AI photo analysis" consent toggle are all in Settings. You may also email support@calsn.app; we may ask you to send the request from the App so we can match it to your account ID. We respond within 45 days, extendable once by 45 days where reasonably necessary.

If we deny a request, you may appeal by replying to our response or emailing support@calsn.app with "Appeal" in the subject line. We will respond within 45 days. If your appeal is denied, you may contact the Washington State Attorney General (opens in a new tab) or your state's Attorney General.

Consumer health data is retained until you delete the relevant entry or your account, as described in the Privacy Policy retention table. We do not keep consumer health data longer than needed for the purposes above. Fasting sessions are kept until you delete them or delete your account, the same as your meal history. Deleting a single water entry sets its amount to zero on our server; that zero-amount record is removed when you delete your account. Amplitude records are the exception: they are kept until you ask us to delete them.

We will update this policy if our practices change and will post the new effective date here. Where a change expands collection or sharing, we will ask for your consent again inside the App.

Illia Kyselov, sole proprietor (FOP), Kyiv, Ukraine · support@calsn.app