Privacy Policy - Kalarie
Updated November 3, 2026. This policy explains Kalarie's data practices, including the version-specific behavior below.
On your device and Apple Health versions
Kalarie stores your profile, logs, imported workouts and saved guidance on your device. In Kalarie 2.0.5 (build 23) and later, imported Apple Health workouts stay local and are excluded from automatic AI requests, including their calorie totals, derived budgets, summaries and activity patterns. Those builds use a separate AI budget from food logs and activities with a known in-app source; unclear older activity stays local. Earlier builds, including 2.0.4 (build 10) and 2.0.5 (build 21), can include imported-workout-derived totals or activity context in AI guidance. This version distinction describes existing behavior; it does not authorize additional collection. Information you deliberately type or paste into an AI request is processed as submitted input.
AI and nutrition services
AI-assisted logging sends submitted text through Kalarie's backend to OpenAI. Relevant requests can include manually supplied age, weight, gender, calorie target, goal, time preferences and eligible direct-log context. Nutrition lookups send food terms or barcodes to the necessary nutrition services. We do not sell your AI input.
Voice transcription
Voice transcription uses Apple's Speech framework and may use Apple's servers. The app keeps the recording locally until the next recording replaces it or local app data is removed. The active flow does not send recordings to OpenAI; submitting an AI-assisted log can send the transcribed text.
Service and purchase records
Our backend receives a random installation identifier and stores allowance-use counts, activity timestamps and Premium verification metadata. The app can send the full App Store receipt to our backend, which forwards it to Apple for validation. Stored verification records include product, purchase/expiry information, transaction identifiers and a receipt fingerprint. Apple handles billing; we do not receive payment-card details. IP addresses are used for security and rate limiting; hosting systems may retain connection logs.
Retention and choices
The backend does not write AI prompt/response bodies to its entitlement database. Providers and hosting systems may retain data under their policies; we do not promise zero retention. Removing the app does not trigger deletion of backend records. Contact support@myvacationplans.com for questions or access, correction and deletion requests.
Changes to this policy
We may update this policy when our practices change. The revision date appears above. The version-specific Apple Health explanation identifies the builds with the local-only AI-context correction.
Contact: support@myvacationplans.com.