Privacy Policy — Android App Addendum
Last updated: November 11, 2026
← Back to common Privacy Policy
This English translation is provided for reference only. The Japanese version is the authoritative and legally binding version.
This addendum covers privacy information specific to the Kalori Android app (the "App"), in addition to the common Policy.
Article D1 (Android Permissions)
The App uses the following permissions, requested through the standard Android screens when you first use the related function:
- Camera: capturing meal and menu photos, and reading product barcodes, nutrition labels, and QR codes. Reading is performed on your device. Barcode numbers and nutrition label values that are read are sent to our servers to match them to products or to record them. If a QR code contains a web address, the App may show its destination on screen. A destination shown is opened in your device's browser (or in the app that handles that address, if there is one) only when you tap “Open”
- Photo selection: the App uses the Android photo picker and receives only the photos you choose. It does not request access to all photos on your device
- Notifications (Android 13 and later): meal reminders, photo analysis results, and announcements (Article D6)
- Health Connect: with your permission, the App reads the information described in Article D2, and writes the information described there if you turn on export
- Location (while using the App): showing the map and choosing a nearby store (Article D8). The App does not collect location in the background or track your movements
You can revoke each permission at any time in Android Settings. A related function may become unavailable when its permission is disabled.
Article D2 (Health Connect)
Only if you allow the App to connect with Health Connect (Android's system for sharing health information), the App reads the following information from Health Connect. You grant permission for each data type in Health Connect and can revoke it at any time.
- Data read: steps, active calories burned, body weight, and body fat percentage. In addition, only when you turn on “Sleep” or “Heart” in the App settings and grant the corresponding read permission, the App reads sleep duration and stages (deep, REM, light, and awake) or resting heart rate, respectively. Both settings are off by default. The App does not read heart rate variability. The App does not read records that the App itself wrote to Health Connect
- Purpose: steps and active calories burned are used as exercise-calorie records for each part of the day, and body weight and body fat percentage as weight records, for your records, goal calculations, and trend displays in the App. For this purpose, the values read are sent to our servers and stored as your exercise and weight records (weight for the last seven days, and on first connection, from 14 days before your registration date). For sleep and resting heart rate, only daily summaries calculated on your device are sent to and stored on our servers, for reading your records through chat AIs or other services you have connected. Normal synchronization covers the last 14 days; the first synchronization after turning an item on covers the last 30 days. Individual sleep and heart-rate measurements are not sent. Sleep and resting heart rate are not used to calculate your goals
- Writing: only if you turn on “Export to Health Connect” in the App and allow writing, the App writes the calories, protein, fat, and carbohydrates of the meals you log in the App, and your body weight (for the last 30 days), to Health Connect. The App updates or deletes the records it wrote to match edits and deletions of your records in the App. On days when another app, such as a smart scale, has written your weight, the App does not write weight (to check this, it reads weight from Health Connect on your device). Records already written stay in Health Connect after you turn export off, and you can delete them in Health Connect. Information read from Health Connect for writing is not sent to our servers
- Disclosure and sharing: we do not sell information obtained from Health Connect, use it for advertising or marketing, or use it to determine creditworthiness, insurance eligibility, or employment. We share it with third parties only through your own actions and consent: (1) when you consent to share your records with a gym or trainer (Article 5 of the common Policy; shown as exercise and weight records), and (2) when you enable an integration with a chat AI or other external service and direct it to read your records (Article 3 of the common Policy). Values obtained from Health Connect are not sent for usage analytics (Article D3); only whether the connection succeeded is recorded
- Retention and deletion: imported records are kept until you delete them or delete your account (Article 8 of the common Policy). Revoking Health Connect permission does not delete records already imported. When turning off Sleep or Heart, you can choose to delete that category’s imported records from our servers or keep them. Records you keep remain available to chat AIs or other services you have connected. This action does not delete the original records in Health Connect. You can delete exercise records in the App, and you can request deletion of other records under Article 11 of the common Policy
- Security: data is encrypted in transit (HTTPS) and stored in encrypted storage on our servers. Access is limited to the personnel and systems that need it (Article 9 of the common Policy)
Article D3 (Usage Analytics and Diagnostics)
To improve quality, maintain security, and investigate technical issues, the App collects the following:
- Firebase (Google LLC): we use Google Analytics for Firebase to analyze screen views, actions, and other usage. Firebase collects a per-installation identifier, device model, operating system and language, app version, and approximate region inferred from the IP address. Usage information we send to Firebase may include part of a search term and values associated with record actions (weight, exercise, and goal values you enter, and purchased products and amounts). We do not send names or email addresses to Firebase and do not link Firebase data to your account. See How Google uses information from sites or apps that use our services
- Records on our servers: the same usage information is also recorded on our servers and, after sign-in, may be associated with your account. When the App shows the destination of a QR code captured by the camera, and when you open it, the App records the host name of the destination (for example, order.example.jp) on our servers. No other part of the address is recorded, and the host name is not sent to Firebase
- Diagnostics: when the App crashes, stops responding, or fails to communicate, details (error type, location, device model, OS and app versions, and time) are sent to our servers
- Device identifier: an identifier created for each installation of the App (it changes when you reinstall) is attached to communications with our servers and used to detect unauthorized sign-ins and maintain security
Article D4 (Advertising)
The App currently does not use third-party advertising services, does not collect the advertising ID, and does not track activity across other companies' apps or websites for advertising. If this changes, we will update this addendum and request permission when required.
Article D5 (Purchases through Google Play)
Subscription purchases and renewals are processed through Google Play's billing system. We receive purchase and subscription-status information necessary to provide Premium features (information used to verify the purchase, the product, and the subscription status) from Google and use it to verify eligibility and prevent misuse. We do not receive card numbers or similar payment details.
When you make a purchase, we pass Google Play a value derived irreversibly from your account identifier, to prevent purchases from being improperly transferred to another account. Purchase records (product, amount, currency, and order number) are also recorded for usage analytics (Article D3).
Deleting your Kalori account does not automatically cancel your Google Play subscription. Cancel it in the Google Play Store app under "Payments & subscriptions" → "Subscriptions".
Article D6 (Notifications)
With your permission, the App displays meal reminders and other notifications. Push notifications for announcements are delivered through Firebase Cloud Messaging (Google LLC); for delivery, your device's notification identifier is registered with our servers. You can turn off each type of notification in Android Settings.
Article D7 (On-Device Data Storage)
The App stores information on your device as needed to maintain sign-in state, save settings, improve display performance, and show home-screen widgets. Authentication information is encrypted with the key protection provided by Android (Android Keystore). This information is excluded from device backups and device-to-device transfers.
Article D8 (Location and Maps)
- Use of location: with your permission, the App uses your device's location while the App is in use to show the map and choose a nearby store. The App does not continuously track your location (no background collection, no movement tracking). Precise coordinates are never sent to our servers
- Search records: to understand which area a search was made in, we store an approximate location (coarsened to roughly a 1 km square) alongside the search record. This coarse location is removed from the search record after 90 days, and search records are deleted entirely when you delete your account. If provided to third parties for statistics or analysis, it is first coarsened further (to roughly a 20 km square or larger) and shared only as aggregated values that cannot identify an individual
- Store information: when you choose a store on the map and record a meal, information identifying that store (its Google Maps place ID) is stored with the meal record
- Google Maps: the map is provided by Google Maps (Google LLC). When the map is shown, Google collects device information, the IP address, and similar information. Use of the map is subject to the Google Maps/Google Earth Additional Terms of Service and the Google Privacy Policy