LiftCue Privacy Policy

Last updated: November 7, 2026

Zetegy LLC develops LiftCue. You can log a workout without creating a Zetegy account. The following sections explain where your training records go and how you can control their use.

Workout records and iCloud

LiftCue stores your workout history in a database on your device. Records can include exercises, sets, repetitions, weights, dates, notes, effort and energy ratings, plans, templates, and feedback on suggestions. When you import a file, LiftCue reads the file you select on your device. The workouts you choose to import become part of your history.

When iCloud is available and enabled for LiftCue, the app uses Apple's CloudKit to synchronize training records through your private iCloud database. Synchronized records include workout sessions, exercises, sets, plans, templates, and suggestion history. If you save a workout to Health, its LiftCue record can also contain the corresponding Health workout identifier, export date, or export error. You can manage iCloud access for LiftCue in your device's iCloud settings. Apple's guide to private iCloud databases

Apple Health

On supported devices, LiftCue requests permission to write completed strength workouts to Health and to read workouts so it can recognize an earlier export. A workout saved to Health can include its title, start and end times, exercise and set counts, total weight lifted, and an identifier linking it to the LiftCue session. You can choose automatic export in LiftCue or save an individual workout. You can change read and write permissions, and delete previously exported workouts, in Apple's Health app. LiftCue excludes HealthKit records from its product analytics and advertising attribution. Manage Health data

Workout suggestions

When Workout Suggestions are enabled, LiftCue can ask Apple's Foundation Models to recommend an exercise using selected context from your current workout and history. This can include workout titles and notes, sets, perceived effort, energy ratings, and feedback on earlier suggestions. On supported systems, LiftCue uses Apple's Private Cloud Compute when available, which sends this context to Apple for processing. It can also use an on-device model. In LiftCue Settings, you can turn off Workout Suggestions or adjust how much history they use. The Intelligence section shows the available processing mode. Apple Intelligence and privacy

Optional usage analytics

Share Usage Data is enabled by default in release builds. When enabled, LiftCue uses PostHog to understand which features people use and where they encounter errors. Events include app opens, onboarding, use of workout assistance, purchase and restore outcomes, and broad categories of import, save, or purchase errors. Workout events can report that you finished a workout and rough ranges for the number of exercises or sets. Even these coarse counts are fitness information.

Events include a random installation identifier, timestamps, platform, and app version. The identifier lets us associate events from the same installation over time. It is separate from your Apple, iCloud, and RevenueCat identifiers. LiftCue's event payloads exclude names, workout and exercise titles, notes, weights, repetitions, search text, import filenames, HealthKit records, and model prompts or responses. LiftCue disables session replay and geographic enrichment in its PostHog configuration.

Turn off Settings → Privacy → Share Usage Data on each device to stop LiftCue from sending new feature and workout analytics. Events already queued may finish sending, and this control does not erase events previously delivered. Turning it back on uses the same installation identifier.

Purchases and attribution

Apple handles App Store payments. LiftCue uses RevenueCat to check access to LiftCue Unlimited, restore purchases, and measure the use of purchase screens. RevenueCat generates a customer identifier for the app and associates it with purchase and subscription information such as the product, transaction or receipt information, and current access status. LiftCue also enables Apple's AdServices attribution token collection through RevenueCat to learn whether an installation came from an Apple ad. RevenueCat sends production paywall views and interactions, purchases, and subscription changes to PostHog so we can measure how often a view leads to a trial or a payment. These events use RevenueCat’s customer identifier and can include the product, transaction identifier, price, and currency. They operate independently of Share Usage Data and use a different identifier from LiftCue’s workout and feature analytics. Purchase validation and Apple Ads attribution operate separately. App Store and privacy · RevenueCat purchase data · RevenueCat Apple Ads attribution

Support and privacy requests

When you submit the in-app support form, you send us your reply email, message, request category, any attachments you choose, and device model, system version, and app version/build. Our support endpoint forwards the request to our support mailbox through Google Workspace. We use that information to investigate and respond. You can email us directly instead.

You can delete individual workouts in LiftCue and manage the separate copies in Apple Health and iCloud through Apple's controls. For questions about this policy, or to request access, correction, or deletion of information Zetegy holds, contact support@zetegy.com or write to Zetegy LLC, 5830 E 2nd St, Ste 7000 #4540, Casper, WY 82609, United States. We will post revisions to this policy here with an updated date.