PRIVACY POLICY
CaloClaw Privacy Policy
How CaloClaw handles confirmed meal records, accounts, optional record photos, AI analysis, ads, purchases, and deletion requests.
1. Information we process and why
CaloClaw is available only to people age 18 or older. Age is used to enforce that service boundary; the app is not intended for children or teenagers.
CaloClaw may use age range, height, weight, activity level, calorie target, and other profile values that a user chooses to enter for starting targets and record trends. These are not used for medical decisions, and each input screen identifies whether a field is required.
Food name, calories, optional protein, carbohydrates and fat, meal type, note, record time, and settings that the user confirms may be used for record sync, trends, and Cat Coach reactions. Only the value the user reviews and saves becomes the official record; an initial AI suggestion does not.
2. Record photos and AI analysis
A user may keep an optional local record photo in the app. CaloClaw does not upload record photos to its own cloud, but a photo may be included in an operating-system backup or device transfer that the user enables. Manual entry remains available, and the saved photo and numeric record can be managed independently.
Photo analysis is optional. Before transfer, the app identifies the AI provider, purpose, data-use terms, and retention terms and asks the user to consent. The current production provider is OpenAI.
After consent, an analysis copy of the meal photo and optional description is sent temporarily to the disclosed provider. CaloClaw does not retain the original analysis upload on its server; it keeps only the structured estimate needed for the record. Manual entry remains available without photo analysis.
3. Accounts and authentication
A device account uses an installation identifier and authentication tokens. If Google or Apple sign-in is chosen, provider identifiers, email, name, and other provider-authorized data may be used for authentication and account linking. Sensitive mobile tokens are kept in operating-system secure storage.
4. Ads and purchases
The free version may use Google Mobile Ads for banners outside the active logging flow and rewarded ads that the user chooses. Device or advertising identifiers, approximate device data, ad requests, and interaction data may be handled under Google's policies.
Blocking food, weight-loss, or other categories that may interfere with the product's purpose is an operating control that reduces unwanted exposure. CaloClaw cannot review every ad in advance or guarantee that every individual ad will be blocked; reports and blocklists require ongoing management.
App Store transaction and product identifiers and receipt-validation results may be processed to verify Plus or a legacy permanent remove-ads entitlement. CaloClaw does not directly store payment-card numbers.
5. Retention, editing, and deletion
Users can edit or delete a photo and numeric record separately. Deleting a local photo does not have to remove its confirmed numeric record, and a numeric record can be deleted without removing every local photo.
Account deletion starts in app settings after a review of scope and irreversibility. It removes identity, meal detail, and photo-analysis results. De-identified reward and purchase ledgers and the minimal linkage needed for fraud prevention, transaction evidence, and legal obligations may remain for the necessary period; the confirmation screen must disclose this retained scope.
6. Providers and international processing
Apple, Google, Google Mobile Ads, and the disclosed AI provider may process the relevant account, advertising, or analysis data in other countries under their own policies. Photo analysis transfers occur only after the in-app disclosure and consent.
7. User rights and safeguards
Where applicable law allows, a user may request access, correction, deletion, restriction, or withdrawal of consent by emailing microcephalus7@gmail.com.
CaloClaw uses HTTPS transport, authenticated access controls, and operating-system secure storage, but cannot promise absolute security. Confirmed incidents will be handled under applicable law and the finalized operating procedure.