Skip to content
Kaltro Get Kaltro
  • Features
  • How it works
  • Switching
  • Pricing
  • Learn
  • Get Kaltro

Privacy Policy

Last updated: October 2026 · Applies to the Kaltro iOS and Android apps and kaltro.fit

The short version: your workout data lives on your iPhone and syncs through your own private iCloud. Kaltro has no accounts, no servers of its own, no ads, and no third-party tracking — we never see your training history and could not read it if we wanted to. Beyond your iCloud, your data leaves your device only when you export it yourself or choose to sync with Apple Health.

On Android there is no iCloud. Your data is kept in the App on your phone. Android’s own backup can copy it to your Google Account, only when that backup is end-to-end encrypted, and to a new phone you set up. Health Connect, Google Play billing and that backup are covered in Section 13.

On this page

  1. Data the App Stores
  2. iCloud Sync
  3. Apple Health
  4. Heart Rate Monitors and Wearables
  5. Analytics and Diagnostics
  6. Data We Do Not Collect
  7. Third-Party Tracking
  8. Data Sharing
  9. Data Retention and Deletion
  10. Children’s Privacy
  11. Data Security
  12. Your Rights
  13. Kaltro on Android
  14. Changes to This Policy
  15. Contact

Kaltro (“the App”) is a strength training companion for iPhone and Android, made by Kaltro LLC (“we,” “us”). This privacy policy describes what data the App handles, how it is stored, and how it is used. Sections 1 to 12 describe the iOS app. The Android version of the App differs where Android and Google services differ, and Section 13 sets out those differences.

1. Data the App Stores

All of the following data is stored on your device, in the App’s local data container and App Group shared storage, and — for the categories listed in Section 2 — synced to your private iCloud database. Everything else in this section — including the derived analytics in 1.2 (performance trends, e1RM calculations, exercise frequency and recency) and the app settings in 1.3 that Section 2 does not list (theme, notification preferences, onboarding state, quieted suggestions) — is not part of that sync, and remains only in the App’s local container. None of it is transmitted to servers we operate or to third parties.

1.1 Workout Data

  • Exercises performed, sets, repetitions, weight, and RPE
  • Rest times, workout duration, date, and time
  • Notes you add to sets or workouts
  • Personal records (PRs) derived from your logged sets

Purpose: core functionality — logging, tracking, and displaying your training history.

1.2 Exercise History and Analytics

  • Performance trends per exercise (weight, reps, volume over time)
  • Estimated one-rep max (e1RM) calculations
  • Exercise frequency and recency

Purpose: powering analytics charts, progression suggestions, and exercise detail views.

1.3 Profile and Preferences

  • Optional profile details: experience level, training goal, weekly workout goal, display name, preferred weight unit
  • App settings: theme, rest timer preferences, notification preferences, onboarding state
  • Suggestions you quiet (“Quiet This Suggestion”): for each exercise, the kind and direction of the suggestion you quieted, its weight and reps, the rule it came from, and when you quieted it, so Kaltro does not suggest it again until your numbers change. This is stored only on your device, in the App’s shared App Group storage; it is never synced to iCloud and never included in exports. Each entry stops applying after 56 days (sooner if many are stored, oldest first) and is deleted the next time this list is updated, and Clear All Data in App Preferences erases it.

Purpose: personalizing suggestions and remembering your preferences. Profile data is never required — the App functions fully without it.

2. iCloud Sync (CloudKit)

The App uses Apple’s CloudKit framework to sync your data between your own devices and keep it available if you reinstall the App. Synced data includes your workout history (workouts, exercises, sets), exercise library including custom exercises and their muscle-group mappings, workout templates, personal records, tested one-rep maxes, rest timer preferences, profile, body metrics you enter yourself, and exercise flags.

Body-metric values read from Apple Health are the exception: they are stored in a separate local table on your device that is deliberately excluded from iCloud sync, so Health-sourced values never leave your device through the App.

  • Where it goes: your private iCloud database, tied to your Apple Account and governed by Apple’s iCloud terms and security. It is not a server we operate — we cannot read, access, or delete it.
  • When it syncs: automatically, whenever you are signed into iCloud. If iCloud is unavailable or sync cannot start, the App runs fully in local-only mode with no loss of functionality. Sync pauses in Low Power Mode.
  • Your control: you can limit or disable the App’s iCloud access in iOS Settings. If the signed-in iCloud account changes, the App alerts you and asks whether to keep or remove the data stored locally on the device.

3. Apple Health (HealthKit)

If you choose to connect Apple Health, the App requests access only after you initiate your first workout or explicitly enable the connection in Settings. You can decline or revoke access at any time in iOS Settings without losing any App functionality.

3.1 Data We Read

  • Heart rate — to show your live heart rate during a workout
  • Workout sessions — to check your saved workouts so the App does not save the same session twice
  • Body weight — to calculate relative strength and to give training suggestions bodyweight context
  • Body fat percentage — to display alongside your weight on the Body Metrics screen

3.2 Data We Write

  • Workout sessions (strength training type) — so your completed sessions appear in your unified Apple Health record

3.3 HealthKit Commitments

  • Health data collected through HealthKit is never sold to advertising platforms or data brokers.
  • Health data is never used for advertising or marketing purposes.
  • Health data is not shared with third parties without your explicit consent.
  • Health data is not used to determine insurance eligibility, lending decisions, or employment decisions.

4. Heart Rate Monitors and Wearables

The App has no direct integrations with third-party wearables. If you use an Apple Watch, chest strap, or other heart rate device, its data reaches the App only through Apple Health, under the permissions described in Section 3. The App shows that heart rate live during your session; it is not saved into your workout history. It is subject to the same commitments as Section 3.3.

5. Analytics and Diagnostics

The App does not collect analytics or usage data. No usage events are recorded, and none are transmitted anywhere — not to us, and not to any third party. This is why the App will be filed under the App Store’s Data Not Collected label.

The App contains internal event-tracking code capable of recording anonymous usage events to an on-device store, but it is gated behind an opt-in that is off, and it records nothing. If that ever changed, any events would be processed on-device, would not be linked to your identity, would contain no workout content, and would not be shared with third-party analytics services — and this policy and the App Store privacy label would be updated first.

Crash and performance diagnostics are handled through Apple’s built-in MetricKit framework. Crash data contains no personal information and is not linked to your identity. Apple’s collection of anonymized diagnostics is controlled by your device’s “Share iPhone Analytics” setting, not by the App. If you have that setting turned on, Apple may share anonymised crash reports with us through Xcode Organizer; that channel is Apple’s, is governed by your device setting, and carries no data that identifies you.

6. Data We Do Not Collect

  • No location data
  • No contacts, photos, camera, or microphone data
  • No browsing or search history
  • No advertising identifiers (IDFA) — the App never requests tracking permission
  • No financial information — purchases are handled entirely by Apple’s App Store on iPhone and by Google Play on Android; we never see your payment details

7. Third-Party Tracking

The App uses no third-party tracking of any kind: no third-party analytics SDKs, no crash-reporting SDKs, no advertising networks, no social media SDKs, and no cross-app or cross-site tracking. This website likewise sets no cookies and runs no trackers. On Android, the App includes Google’s Play Billing Library to sell subscriptions; it is Google’s billing library, not an analytics or advertising SDK, though it sends Google diagnostic logs, which the App’s Google Play data safety section declares; see Section 13.4.

8. Data Sharing

We do not share your data with any third party. Your data leaves your device only when:

  • It syncs to your private iCloud — governed by Section 2. This is your Apple Account, not a party we can share with or read from.
  • You export it — the App’s CSV export of your workout history saves a file to a location you choose (Files, AirDrop, email, and so on).
  • You sync with Apple Health — governed by Section 3 and your iOS permissions.
  • Apple collects MetricKit diagnostics — controlled by your iOS settings, as described in Section 5.
  • On Android — through Android’s encrypted backup, Health Connect and Google Play billing, as described in Section 13.

9. Data Retention and Deletion

Your workout data is stored on your device for as long as the App is installed, and in your private iCloud database as described in Section 2. Deleting individual items in the App removes them from the device and from your iCloud copy on the next sync.

Deleting the App removes all locally stored data. Data already synced to your private iCloud remains there — under your Apple Account, not ours — until you remove it, either by reinstalling the App and deleting the data inside it, or through your device’s iCloud storage management. There are no Kaltro-side accounts or copies to request deletion of; we hold nothing. Data you wrote to Apple Health remains in Apple Health under your control until you delete it there.

10. Children’s Privacy

The App does not knowingly collect data from children under 13. It is rated 4+ and contains no age-restricted content. We run no backend for the App and hold no copy of your data: there are no accounts, no Kaltro server the App sends your data to, and no third-party analytics, advertising or tracking SDKs. Data you enter stays in the App’s local container on your device and, when you are signed into iCloud, syncs to your own private iCloud database under your Apple Account (§2) — a transfer to your own Apple Account under Apple’s iCloud terms, not a collection by us. For a child, that Apple Account is created and managed by a parent under Family Sharing, so the consent relationship is with Apple, not with us. This website is a separate static site; opening a support or policy link from the App produces ordinary web-server request logs and nothing more. On that basis the App is designed to comply with the Children’s Online Privacy Protection Act (COPPA) and equivalent regulations.

11. Data Security

All data stored by the App benefits from iOS platform security: it lives in the App’s sandboxed container, inaccessible to other apps, and is protected by iOS Data Protection (encrypted at rest on the device). Data synced through iCloud is encrypted in transit and stored in your private iCloud database under Apple’s iCloud security. Because your training history never touches servers we operate, our side adds no attack surface.

12. Your Rights

Because your data never comes under our control, you exercise your privacy rights directly. View your data in the App. Export your workout history — workouts, exercises and completed sets, including any notes and effort ratings you logged — as a CSV file from App Preferences → Export Data (open App Preferences from the gear icon on your profile). The file covers workout history only: your profile, preferences, templates and body metrics are not included, but you can still view them in the App. Erase everything by deleting your data in the App (which also clears your iCloud copy) and then deleting the App. If you have questions about your rights under GDPR, CCPA, or similar regulations, contact us at the address below.

13. Kaltro on Android

Sections 1 to 12 describe the iOS app. For the Android app, this section governs storage, backup, health data, diagnostics, billing and deletion, and where it and Sections 1 to 12 differ, this section applies.

13.1 Storage and Backup

  • On your phone: your workouts, exercises, templates, profile, body metrics and settings are stored in the App’s private storage on your phone, protected by your phone’s storage encryption (standard on every phone that launched with Android 10 or later). The Android app does not use iCloud, has no account, and sends none of this to servers we operate; we have none.
  • Android backup: the App leaves Android’s own backup turned on, so that your training history is not lost when you change phones. Android can copy the App’s data, including the weight and body fat imported from Health Connect (13.2), to your Google Account, but only when that backup is end-to-end encrypted, which requires a screen lock on your phone. Without a screen lock, no cloud backup of the App’s data is made. Android can also copy the data directly to a new phone when you set one up. We cannot read either copy. You can turn cloud backup off in your phone’s backup settings, and skip copying apps when you set up a new phone. Your phone maker’s own backup or transfer tools may also copy app data, under their own terms.
  • Export: you can save a copy of your workout history (workouts, exercises and sets) with Export CSV or Export JSON in the App’s Settings, to a location you choose. Your profile, body metrics, templates and settings are not included.

13.2 Health Connect

If you connect Health Connect, the App asks for Health Connect permissions only when you use a feature that needs them, and you can decline or revoke any of them in Health Connect’s settings without losing the rest of the App. The App requests exactly these five data types:

  • Exercise sessions (write) — if you have connected Health Connect, the App saves each workout you finish to Health Connect as an exercise session, with one segment per exercise and its rep count, so it appears in your Health Connect history. Each workout is written once. The App writes nothing else.
  • Weight (read) — when you choose to import your bodyweight on the Profile screen, the App reads your latest weight and stores it as your profile bodyweight, where it is used for bodyweight-relative milestones.
  • Body fat (read) — read with your weight during the same import, if your scale recorded one, and stored in your body-metric history alongside it.
  • Heart rate (read) — on a finished workout’s detail screen, the App shows the average and maximum heart rate that another app, such as your watch, recorded during that workout. It is displayed only: it is not stored and is used for nothing else.
  • Active calories burned (read) — shown next to that heart rate, the active calories another app recorded during the workout. It is displayed only and not stored. The App never estimates or writes calories.

Health Connect data is used only for the features listed above. The use of information received from Health Connect will adhere to the Health Connect Permissions policy, including the Limited Use requirements. Health Connect data is never sent to us, never sold, never used for advertising or marketing, never transferred to third parties, and never used to determine credit, insurance or employment eligibility. The weight and body fat the App stores can be copied by the backup and transfer paths described in 13.1; heart rate and active calories are never stored, so they are never backed up. Workouts the App wrote to Health Connect stay there, under your control, until you delete them in Health Connect.

13.3 Analytics, Diagnostics and Crash Reports

Apart from the Google Play Billing Library diagnostics described in Section 13.4, the Android app collects no analytics or usage data, and it contains no third-party analytics, crash-reporting or advertising SDK. The App’s own diagnostic records are written to your phone’s system log and to a short list held in memory while the App runs; they are not saved and are never sent anywhere. The App’s own code does not read your advertising ID or any other device identifier. If you have chosen to share usage and diagnostics data with Google, Android and Google Play may collect crash and app-not-responding reports, and Google may show us aggregated figures and crash details in the Play Console; that is Google’s channel, controlled by your phone’s settings, and it carries no data that identifies you to us.

13.4 Google Play Billing

On Android, Kaltro Pro is sold through Google Play. Google Play collects your payment details directly, and no payment information reaches us. To decide whether Pro is unlocked, the App asks Google Play, through the Play Store app on your phone, which Kaltro purchases your Google Account holds, and confirms new purchases back to Google Play; the result is used on your phone and sent nowhere else. Google’s Play Billing Library, which runs inside the App to do this, sends Google diagnostic logs about billing requests (such as whether they succeeded) and connection problems. Those logs go to Google as the provider of the billing service, under Google’s privacy policy, not to us, and Google decides how long they are kept. Because of them, the App’s Google Play data safety section lists app diagnostics as collected, for app functionality and analytics.

13.5 Retention and Deletion on Android

Your data stays in the App on your phone until you delete it. Clear All Data in the App’s Settings erases the App’s database on the phone, and uninstalling the App removes all of its local data. A backup Android made before you cleared or uninstalled can still restore the old data if you reinstall the App or set up a new phone, until Android’s next backup of the App replaces it. You can delete a backup from your Google Account; Android backs up each phone as a whole, so this deletes that phone’s entire backup, not only the App’s data. There are no Kaltro-side accounts or copies of your data to request deletion of; we hold none. Data you wrote to Health Connect remains there until you delete it in Health Connect.

14. Changes to This Policy

We may update this policy to reflect changes in the App’s data practices. The “Last updated” date above will be revised, and material changes (new data types, new integrations) will be communicated in the App’s release notes before they take effect.

15. Contact

Questions about this policy or the App’s data practices: feedback@kaltro.fit · kaltro.fit/support

Kaltro

Every rep has a reason.

Progressive overload tracking for iOS. Every suggestion shows its reason; every decision stays yours.

This site uses no cookies and no trackers.

Product

  • Features
  • How it works
  • Switching
  • Compare
  • Pricing
  • Import guide
  • Get Kaltro for iPhone
  • Press kit

Resources

  • Lifting Calculators
  • e1RM Calculator
  • Volume Calculator
  • Training Glossary
  • Workout Templates
  • How Kaltro Decides

Support

  • Support & FAQ
  • feedback@kaltro.fit

Legal

  • Privacy Policy
  • Terms of Service
© 2026 Kaltro LLC. All rights reserved.
Privacy Terms Support