Information collected
The App handles the following types of information.
Health data
Calorithm integrates with Apple Health and Google Health Connect to access and display the following health-related data.
| Type | Operation |
|---|---|
| Active Energy | Read & Write |
| Resting Energy | Read |
| Weight | Read & Write |
| Dietary Energy Consumed | Read & Write |
| Nutrients (Protein, Fat, Carbohydrates, Sodium) | Read & Write |
| Body Fat Percentage | Read & Write |
| Steps | Read |
| Sleep | Read |
| Water | Read |
This data is used to provide insights about calorie balance, body composition, and weight trends. Raw data retrieved from Apple Health / Google Health Connect is processed locally on your device; when you use AI features, only the necessary summaries may be used for AI processing.
Steps, sleep, and water are read only if you allow it; Calorithm never writes them. Steps and sleep are used to show today’s steps and last night’s sleep on the dashboard, and to show day-to-day changes in trend charts and Reflection reports. Water is used to show how much you drank on the Water card when you add it to the dashboard or trends. When you use AI features, the only step, water, and sleep data that may be sent is summarized values: daily and period step and water totals, and each night’s sleep time, time in bed, bedtime, and nap time, plus their averages. Individual sleep and water records are not sent.
On Android, after you grant access, Calorithm may also read Health Connect data in the background — including while the app is not on screen — to keep calorie balance and body composition up to date. Reads are not limited to times when the app is in the foreground.
If health data carries over via iCloud, that is Apple Health’s own sync. Calorithm does not store health information in CloudKit.
User-provided information
You can manually enter calorie intake. This information is stored locally on your device. When you use AI features, your input, photos, or summaries derived from your records may be transmitted for AI processing.
Body measurements you provide (such as height, gender, age) are stored in an encrypted local database and are used solely for calorie balance estimation.
Camera & photo library
When you choose to estimate calories from a food photo, Calorithm may access your device's camera or photo library. Photos are sent to Google AI services (Vertex AI Gemini) solely for AI processing. The App itself does not store photos externally.
Purchase information
When you subscribe to Plus or buy additional AI points on iOS, the App's server verifies the App Store's signed transaction information and uses it to grant points and manage your balance. The server stores keyed hashes of the purchase and subscription identifiers, together with the state of point grants, balances, and refunds. The App does not receive your payment method or name.
When you subscribe to Plus on Android, the App's server sends the Google Play purchase token to Google Play to verify the state of the subscription when the purchase is confirmed, when you use AI features, and when your remaining points are shown, and uses it to confirm the purchase, grant points, and manage your balance. When you resume a subscription in Google Play without opening the App, for example, the server receives a notification from Google Play and verifies it in the same way. The server does not store the purchase token itself; it stores a keyed hash of it, together with the subscription number linked to it and the state of point grants and balances. The App does not receive your payment method, name, or Google Account. Additional AI points are not sold on Android.
In-app inquiries
When you contact us from within the App, the App sends the category you chose, your message, your reply-to email address, and diagnostic information (app and OS version, device model, Plus status, error type and time, and the screen the contact form was opened from). A reply-to address is required for the How to use, Purchases and billing, and Privacy and data categories, and optional for the others. You can choose not to send diagnostic information. This information reaches the developer's email through Resend, an email delivery service, and is used only to respond to your inquiry. The App's server does not store your message or reply-to address.
Usage data
In-app usage analytics and crash reporting are disabled by default. They are collected only after you separately opt in to each category in Settings, and you can withdraw either consent at any time. The website may collect minimal usage information such as page views.
- App feature usage statistics
- App performance data
- Crash reports
- Website page views and button clicks
The App does not send calories, meals, weight, body fat, activity, goals, or ranges or classifications derived from them to Analytics or Crashlytics. Crash reports do not include health or food data or user-entered content.
Where ad consent is required, the App presents Google's User Messaging Platform consent form and uses the resulting eligibility to decide whether ads may be requested. When required, you can review or change your choices from Ad privacy options in the App. When ads are displayed, Google Mobile Ads may collect approximate location, device and advertising identifiers, ad or in-app interactions, performance data, and other diagnostics. These may be used for ad delivery and measurement, analytics, fraud prevention, and app functionality. Health and food data are not used for advertising.
How information is used
Collected information is used to:
- Provide, maintain, and improve the App's functionality
- Develop new features and services
- Understand how users interact with the App
- Detect, prevent, and address technical issues
Data retention
| Data | Retention |
|---|---|
| Health data | Stored locally; AI features may use the necessary summaries when needed for processing. |
| Analytics data | Sent only after you enable usage analytics; retained under Google's standard policies. |
| Crash data | Sent only after you enable crash reports; retained for 90 days by Firebase Crashlytics. |
| AI feature data | Input, photos, and record summaries for estimation and similar features are processed by Google AI services. The App does not store the input, photos, or record summaries externally; generated outputs are saved in the encrypted on-device database. |
| Temporary storage of AI responses | The text of estimation, suggestion, reflection, and consultation responses is stored temporarily on the App's server, together with the record of your AI allowance, so that the result of the same request can be received again if the connection drops. Input and photos are not stored. It is kept until one day after the allowance period (one month) ends and then deleted automatically. It is also deleted when you withdraw consent to AI data sharing. |
| Consultation content | Processed by OpenAI. The App asks OpenAI not to store responses, but OpenAI may keep the data for up to 30 days for abuse monitoring by default, or longer when required by law or reasonably necessary to protect its services or third parties from harm. Conversations and answers are saved in the encrypted on-device database. |
| Purchase records (iOS) | Keyed hashes of the purchase and subscription identifiers, together with the state of point grants, balances, and refunds, are stored on the App's server. Purchased points do not expire, so the record of their balance is kept without a set period. The record of points granted by a subscription is kept until one day after its grant period ends and then deleted automatically. |
| Purchase records (Android) | The link between a keyed hash of the purchase token and the subscription number is stored on the App's server until 60 days after the last verified expiry of the subscription and then deleted automatically. Each verification counts again from that expiry. In case Google Play does not respond temporarily, the last verified state of the subscription (such as the plan and expiry) is also stored until one day after the subscription's expiry and then deleted automatically. When the server verifies that a subscription has ended, that fact is kept for 7 days and then deleted automatically. The record of points granted by a subscription is kept until one day after its grant period ends and then deleted automatically. |
| Inquiries | Delivered to the developer's email through Resend and kept in the developer's email to respond to you. Resend handles them under its own data retention policy. The App's server does not store your message or reply-to address. |
| Google Search for estimation | Google may retain search terms and related context for up to 3 days for debugging the search infrastructure, without associating it with you. |
| Consultation search terms | When a Plus consultation uses web search, the search terms are handled under the data retention policies of OpenAI and its search providers. |
| Ad-related data | Per Google AdMob's privacy policy. |
Records past their storage period are deleted automatically, but actual deletion can take about a day after the period ends.
Data security
Sensitive personal data — including body measurements, AI estimation history, and generated AI reports — is stored in an AES-256 encrypted database on your device. However, no method of transmission over the internet or electronic storage is 100% secure, and absolute security cannot be guaranteed.
Your data rights
You have the following rights regarding your personal data.
- Usage analytics: disabled by default; enable or withdraw consent in Settings > Privacy & Data > Usage Analytics.
- Ad choices: make your selection in Google's UMP consent form. Where required, review or change it in Settings > Privacy & Data > Ad privacy options. On iOS, ATT separately controls cross-app tracking.
- Crash reporting: disabled by default and controlled independently from usage analytics.
- AI data sharing: withdrawing consent in Settings stops new AI transfers and deletes the AI responses temporarily stored on the server and the record of your AI allowance. The balance of purchased points remains. Requests already processed cannot be undone.
- Consultation history: you can delete it from this device. Deleting a conversation does not delete logged meals or the original reflection, and does not mean that data already processed by external services is immediately erased.
Requests for disclosure, correction, or suspension
For personal data held on the App's server or by the operator, you can request notice of the purpose of use, disclosure, correction, addition or deletion, suspension of use or erasure, and suspension of provision to third parties. Send your request to the email address below. After confirming that you are the person concerned, we will respond without delay in accordance with applicable law.
Data stored only on your device is not received by the operator, so you can review and delete it in the App.
The operator's name and address are provided without delay upon request. Complaints and questions about how personal information is handled are accepted at the same email address.
Changes to this policy
This Privacy Policy may be updated from time to time. Any changes will be posted on this page with an updated “Last Updated” date at the top.
Contact
If you have any questions about this Privacy Policy, please contact us.
duck8823@gmail.com
We will reply as soon as we can.