Privacy Policy

This policy describes how CaloCalo (“we”, “us”) collects, uses, and protects your information when you use the CaloCalo mobile app and the calocalo.app website. CaloCalo is a calorie and nutrition tracker.

Yes, we collect user data. To run the app we collect account details, the food and health data you log, the meal photos you scan, purchase status, and app usage and crash diagnostics. We use artificial intelligence to analyse the meal photos and descriptions you submit, and we share data with a small set of named third-party providers listed below. We do not sell your data, we do not share it with advertisers or data brokers, and we show no ads. Everything below is the detail.

Account. When you sign in with Google or Apple we receive your email address and display name. We never see your password.

Food and health data. The meals you log, water intake, weight entries, exercise entries, nutrition goals, and profile details you enter during onboarding (such as height, date of birth, sex, and activity level). This is the core data the app exists to manage, and some of it counts as health data under GDPR.

Photos. Meal photos you take for AI scanning, and progress photos you add to a weight entry, are uploaded to private storage buckets so they survive a reinstall. Those buckets are not public: they have no public read access, row-level security limits every object to the folder belonging to its owner, and images are served only through links that we sign and that expire within minutes. Nobody but you and our servers can fetch them.

Voice input. If you describe a meal by voice, speech-to-text is performed by your device’s own operating system (Apple or Google). We receive only the resulting text; we never receive or store the audio recording.

Apple Health. Only if you grant permission, we read workouts and energy burned from Apple Health to show them in the app, and we write the workouts you log back into Apple Health. This data is exchanged directly between the app and Apple Health on your device. Revoking the permission in iOS Settings stops it immediately.

Purchases. Subscriptions are processed by the App Store. We receive your subscription status and an anonymous purchase identifier, never your payment details.

Usage analytics and crash diagnostics. We record which screens you open and which core actions you take (for example: a scan started, a meal saved), plus crash reports and error logs containing device model, OS version, and app version. This is used to find bugs and see which features are used, never to build advertising profiles.

Notifications. Tracking reminders are scheduled locally on your device. We do not operate a push server and do not collect push tokens.

Technical logs. Our servers keep short-lived request logs (IP address, endpoint, timestamp) for security and debugging.

To run the app: keep your diary in sync across reinstalls and devices, analyse meal photos and descriptions you submit, check your subscription entitlement, operate the referral programme, fix crashes, and answer support requests. We do not sell your data, share it with advertisers, or use it for marketing profiles.

If you are in the EU/EEA or the UK, our legal bases are: performing our contract with you (running the app and your subscription), your explicit consent for health data and for Apple Health access, and our legitimate interest in keeping the service secure and working (diagnostics, abuse prevention). You can withdraw consent at any time by deleting your account or revoking the relevant permission.

CaloCalo uses artificial intelligence. When you scan a meal, the photo (or the text description you type or dictate) is sent to a third-party AI model to estimate its nutrition. We use established vision models through their business APIs. Images are shared through a link that expires within minutes, and the requests run under terms that do not permit your content to be used to train their models. Scan results are returned to your device and stored in your diary; the analysis job itself is deleted from our servers within minutes of completing.

AI output is an estimate, not a measurement, and it can be wrong. It is not medical, dietary, or clinical advice, and CaloCalo is not a medical device. Do not rely on it for medical decisions.

The AI is limited to identifying food and estimating nutrition; it does not provide mental-health, crisis, or medical guidance of any kind. If you are struggling with disordered eating, self-harm, or thoughts of suicide, please stop using calorie tracking as a coping tool and talk to a qualified professional or a local crisis line. In the US call or text 988; elsewhere see findahelpline.com. If you tell us you are in crisis by email, we can only point you to these resources; we are not an emergency service.

Your diary is stored on our secure cloud infrastructure, so your data survives a lost or new phone. All traffic between your device and our servers is encrypted with TLS, every request is authenticated, and access is scoped to your account, so no other user can read your rows or your photos. The photo storage buckets are private: they have no public read access, and every image fetch requires a signed URL minted for your own objects only.

Our providers operate in the United States and other countries, so your data may be processed outside the country you live in. Where the law requires it, these transfers are covered by the providers’ standard contractual clauses.

We share data only with the processors needed to run the service. These are all of them:

• Supabase: sign-in, database, and private photo storage
• AI providers: nutrition analysis of the photos and descriptions you submit
• RevenueCat: subscription and entitlement status
• PostHog: product analytics (screens opened, core actions taken)
• Sentry: crash and error reporting
• Apple and Google: sign-in and payment processing

Each of them acts as our processor under contract and may only use the data to provide their service to us. We disclose data beyond this list only if the law requires it. There are no ad networks, no advertising SDKs, and no data brokers in the app, and we never sell or “share” personal information as those terms are defined by the CCPA.

We keep your diary, your profile, and your uploaded meal photos for as long as your account exists, because that is the record the app is built to show you.

You can delete everything yourself, from inside the app: Profile → Delete account. It takes effect immediately: we delete your sign-in identity, delete your uploaded photos from storage, and delete your account row, which cascades to every meal, food, log, referral, and AI job you own. There is no waiting period and nothing to email us for.

If you prefer, you can instead email us and we will complete the deletion within 30 days. AI analysis jobs are deleted within minutes of completing, and server request logs are rotated automatically. Backups roll off within 30 days. Records we must keep by law (such as purchase records held by Apple) are outside our control.

You can ask us to show you the data we hold about you, export it, correct it, restrict or object to its processing, or delete it, and you can exercise the right to delete yourself at any time in the app. Depending on where you live (including the EU/EEA and UK under GDPR and California under CCPA/CPRA), these rights are backed by law, and we will never discriminate against you for using them. Write to us and we will respond within 30 days. EU/EEA and UK users also have the right to complain to their local data protection authority.

CaloCalo is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will delete it.

If this policy changes in a way that matters, we will update the date below and notify you in the app before the change takes effect.

Questions, requests, or complaints: support@calocalo.app