TitanCal Privacy Policy

01 Information We Collect

1.1 Data You Give Us

An account is optional. Without one, TitanCal keeps your data on your device and sends none of it to us. The features that run on our servers need an account: logging a meal from a photo or a description, looking up foods and barcodes online, importing a recipe from a link, and syncing across your devices.

Account: you can sign up with an email and password, Sign in with Apple, or Sign in with Google. Sign-in runs through Supabase, our database and sign-in provider. Supabase keeps your account record: your email address, a user ID, the sign-in method you used, sign-in dates, and, for email accounts, your password in hashed form. We never see your password. With Sign in with Apple we ask Apple for your email address only; if you choose Hide My Email, we receive an Apple relay address instead of your real one. With Google, the account record also holds the basic profile Google shares, such as your name and profile photo link.

Profile: during setup and in Settings you enter your sex, birth year and month, height, weight, goal weight, activity level, goal pace, and units. TitanCal uses them to set your calorie and macro targets.

Support email: if you email us, we receive your name, email address, and whatever you write.

1.2 Data the App Creates

Content you create inside the app: food logs and meals; saved foods, meals, recipes, and favorites; fasts; weight entries; your calorie and macro targets; and the settings you choose. A thumbnail of each food photo you log is kept on your phone so you can see what you logged.

Portion edits: if you turn on "Keep a log of my portion edits" in Settings, TitanCal records the portion it estimated and the portion you changed it to, and uses that to tune estimates for you. It is off unless you turn it on.

1.3 Purchase Information

TitanCal Premium is an optional subscription. Apple's App Store (on iPhone) or Google Play (on Android) processes the payment. We do not receive your payment method or billing address.

We use RevenueCat to tell the app whether Premium is active on your devices. RevenueCat receives an app user ID (a random identifier, which is your account's user ID once you sign in) and your purchase history. It receives no food logs or health data. Our server keeps your subscription status and a count of the photo logs you use each day, which is how the free plan's limit is applied.

1.4 Data We Do Not Collect

1.5 Health App Access — Apple Health & Health Connect

Connecting Apple Health on iPhone or Health Connect on Android is optional, and TitanCal works without it. If you connect, TitanCal reads and writes only the data types you turn on, chosen from this list:

• Body: weight, body fat, and height.
• Activity: active energy, basal energy, and steps.
• Nutrition: dietary energy, protein, carbohydrates, fat, fiber, sugar, and sodium.

Apple Health and Health Connect data is used only to provide the features you turned on. It is never used for advertising or data mining, never sold, and never stored in iCloud. If you have an account, weight entries imported from Apple Health or Health Connect sync to our cloud database with the rest of your weight history, so the same trend shows on each of your devices. You can turn off any type in TitanCal under Settings → Health, or revoke access in the Health app or in Health Connect, at any time.

1.6 Food Photos & AI Meal Logging

Photos: when you log a meal from a photo, the photo is sent over an encrypted connection to our server, which asks an AI model, Anthropic's Claude, to name each food and estimate the portions. The photo is held in memory only while it is analyzed. It is never written to storage, a database, or logs. Calories and macros come from nutrition databases, not from the AI model.

Typed and spoken meals: when you type or speak a meal description, the text is sent to our server and on to the AI model to be broken into individual foods. If you speak, your phone's speech recognition service (Apple's or Google's) turns your speech into text first, under Apple's or Google's own privacy terms.

Food search and barcodes: the words you search for and the barcode numbers you scan are sent to our server, which looks them up in USDA FoodData Central and Open Food Facts. A barcode number identifies a product, not you.

Recipe links: when you paste a recipe link, our server fetches that page to read the recipe.

Food names, portions, calories, and macros are estimates and can be wrong. Check them before you save a meal. TitanCal does not give medical advice.

1.7 Analytics & Crash Reports

Usage analytics (optional): if you turn on "Share anonymous usage analytics" in Settings, TitanCal sends usage events to PostHog so we can see which features get used. Events are things like onboarding complete, meal logged, fast started, and paywall shown. They never include food names or health numbers. Nothing is sent to PostHog, not even a device identifier, until you turn this on, and you can turn it off at any time.

Crash reports: when the app crashes or hits an error, TitanCal sends a report to Sentry so we can fix it. A report holds the technical details of the error, your device model, operating system version, and app version. We do not attach your name, email, or account to it, and console and network records are stripped before it leaves your phone, so food names and health numbers are not included. Apple and Google may also collect standard crash data through iOS and Android under their own privacy policies.

1.8 Location for Sunset Reminders

Location is asked for only if you choose a fast reminder "At sunset." TitanCal reads your location once, at low accuracy, rounds it to about a kilometer, and uses it on your phone to work out sunset. It is not sent to us and is not synced. If you decline, you can pick a set time instead.

02 Where Your Data Lives

• On your device — your logs, fasts, weight, profile, targets, settings, and photo thumbnails are stored inside the app's private storage. Without an account, this is the only place they are kept.
• In our cloud database, only if you create an account — your account record and your synced data are stored with Supabase, in the United States. Synced data is your food logs and meals; saved foods, meals, recipes, and favorites; fasts; weight entries, including ones imported from Apple Health or Health Connect; your profile; your targets and settings; and your portion edits if you turned that log on.
• In Apple Health or Health Connect — records you chose to have TitanCal write there are kept by those services, under your control.
• With RevenueCat — your app user ID and purchase history (1.3).
• With PostHog and Sentry — usage events if you opted in, and crash reports (1.7).
• Nowhere — food photos are not kept on our servers after they are analyzed, and your rounded location for sunset reminders never leaves your phone.

03 How We Use the Information

• To run the app's features: logging meals, timing fasts, charting your weight trend, and setting your calorie and macro targets.
• To sync your data across the devices you sign in to, if you have an account.
• To name foods and estimate portions from the photos and descriptions you send.
• To validate purchases, unlock Premium, and apply the free plan's photo limit.
• To find and fix crashes, and, if you opt in to analytics, to see which features get used.
• To respond to support requests you initiate by contacting us.

We do not use any data for advertising, marketing, profiling, or sale. We do not use your photos for training unless you opt in (1.6).

04 Tracking

TitanCal does not track you across apps or websites owned by other companies, as Apple defines "tracking" under its App Tracking Transparency framework. We do not request the ATT permission, and TitanCal does not use the IDFA or the Android Advertising ID.

05 Sharing

We do not sell, rent, or lease your personal information, and we do not share it for advertising or marketing. The only third parties that touch any data are the services TitanCal runs on. Each receives only what it needs to do its job:

• Supabase — hosts our database, sign-in, and server functions. It holds your account and synced data, only if you create an account.
• Anthropic (Claude) — receives the food photos and meal descriptions our server sends for analysis. It acts as our service provider, and our contracts bar it from training on your photos.
• USDA FoodData Central and Open Food Facts — receive the food searches and barcode numbers our server looks up. The requests come from our server and carry nothing that identifies you.
• Apple and Google — provide payments, Sign in with Apple and Sign in with Google, speech recognition, Apple Health, and Health Connect. Their handling is governed by their own privacy policies.
• RevenueCat — receives an app user ID and your purchase history to report subscription status.
• PostHog — receives usage events, only if you opt in.
• Sentry — receives crash and error reports.
• Recipe websites — when you import a recipe link, our server requests that page. The site sees a request from our server, not from you.
• Legal requirement — we would disclose information only if compelled by a valid legal process directed at us.

06 Data Retention & Deletion

• Your entries: you can edit or delete any log, fast, weight entry, saved food, meal, or recipe in the app at any time.
• Local data: removed when you delete the app. Without an account, that deletes everything.
• Account and synced data: kept for as long as your account exists. Settings → Your data → Delete my account and data removes your account and logs from our servers within 30 days. It cannot be undone.
• Export: before you delete, you can export your data as a CSV file from the delete account screen, free for everyone. Premium subscribers can also export at any time from Settings.
• Subscriptions and purchase records: deleting your account does not cancel a subscription; cancel it in your App Store or Google Play subscription settings. Apple and Google keep transaction records under their own policies, and we cannot delete them. Deleting your account also asks RevenueCat to delete the purchase history it holds for that account. If you never created an account, RevenueCat holds only a random ID from your phone, with no name or email attached.
• Apple Health and Health Connect: records TitanCal already wrote there stay there unless you delete them in those services.
• Sign in with Apple: revoke access in Settings → Apple ID → Sign In with Apple → TitanCal → Stop Using Apple ID.
• Food photos: not kept on our servers after analysis. Thumbnails on your phone are removed with the app.
• Analytics and crash reports: turning off Share anonymous usage analytics stops new events. PostHog and Sentry keep what they already received under the retention settings for our account and then delete it.
• Support email: kept only as long as reasonably needed to resolve your issue, then deleted.

You may also email us to request deletion of any data we hold. We will delete it within 30 days.

07 Children's Privacy

TitanCal is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe we have inadvertently received such information, contact us and we will delete it promptly.

08 Your Rights (GDPR / CCPA)

Health information, such as weight and nutrition data, is sensitive personal information under California law and special category data under the GDPR. We process it only to provide the features you ask for. If you reside in the EEA, UK, or California, you have the right to:

• Access the personal information we hold about you. You can see all of it in the app.
• Correct or delete it. You can edit or delete entries in the app, or delete your account in Settings.
• Object to or restrict processing. You can turn off analytics, photo training, the portion edit log, or any Health data type at any time.
• Receive a copy in a portable format. The CSV export provides one (Section 06).
• (CCPA) Opt out of "sale" or "sharing" of your data — we do neither.

For anything you cannot do in the app, email us at the address below. Yost Group LLC is based in the United States, and if you use TitanCal from elsewhere your data is processed there. You may also lodge a complaint with your local data protection authority. We do not discriminate against users who exercise these rights.

09 Security

Data on your device is protected by your phone's built-in data protection and your device passcode. Everything TitanCal sends to our server and to the services above travels over encrypted connections (TLS). In our database, each account can read and change only its own rows, and the server functions the app calls refuse requests that are not signed in. Our server logs record that a request happened and whether it worked, and nothing you sent: no photos, food text, or food names. No method of transmission or storage is completely secure, so use a device passcode and, if you sign up with email, a strong password you use nowhere else.

10 Changes to This Policy

We will update this page when we make material changes and revise the "Last Updated" date above. Significant changes will be surfaced inside TitanCal on its next launch.