Short version: Lift & Log does not have an account system or Lift & Log servers that receive your workout, nutrition, measurement, or HealthKit data. Your on-device SwiftData store is the source of truth. The app has no ads, tracking, or third-party analytics.
Overview
This privacy policy applies to the Lift & Log app for iPhone and iPad, its Apple Watch companion, and this website. “Lift & Log,” “we,” “us,” or “our” refers to the developer of Lift & Log.
The app is a fitness planning and tracking tool. You can use its core local features without creating a Lift & Log account because no Lift & Log account system exists.
Data stored on your device
Lift & Log uses Apple’s SwiftData framework for local storage. Depending on how you use the app, this may include:
- training plans, scheduled sessions, workout definitions, completed workouts, sets, scores, times, and notes;
- gyms, available equipment, movements, substitutions, and preferences;
- nutrition targets and entries;
- body mass and other body measurements;
- benchmarks, personal records, progress calculations, and related inputs; and
- local settings and records used to avoid duplicate Apple Health syncs.
The local store remains writable offline. Planning, library, and gym records can also replicate through your private iCloud database as described below. SwiftData is the source of truth; Apple Health is not a backup of your Lift & Log data.
Optional Apple Health access
You choose which permissions to grant in Apple's authorization sheet. iPhone reads body mass and workout records to import bodyweight and reconcile completed workouts. It writes body mass and completed workouts when you enable or request those actions.
Optional nutrition export separately requests permission to write dietary energy consumed, protein, carbohydrates, and total fat. Watch reads heart rate and active energy during a workout and saves completed workouts and their measurements to Apple Health.
Health data supports these fitness features. It is not used for advertising, tracking, or marketing. You can change permissions in Apple Health or your device's privacy settings. Apple may not disclose denied read access to the app. App records and Apple Health records are separate; deleting one does not necessarily delete the other.
Optional Calendar access
Calendar sync requests full calendar access through Apple's EventKit framework so the app can read and update linked workout events in a writable calendar you choose. Events contain workout titles, dates and times, gym names and addresses or venue text, and a link that opens the scheduled workout. Workout results and personal notes are excluded.
The provider of your chosen calendar may sync these events to its servers and other devices under its own settings and policies. Connection and event-link records stay on your device and are excluded from the app's CloudKit replica and portable backups. You can revoke calendar access in device settings.
Disconnecting Calendar sync, resetting the app, or restoring a portable backup leaves existing calendar events in place. Manage those events in Calendar. After a restore, reconnect deliberately on your primary iPhone.
CrossFit Workout of the Day import
Automatic CrossFit WOD import is disabled in the current beta. In versions where this integration is enabled, the app makes network requests to crossfit.com to retrieve publicly available workout content.
Lift & Log does not include your Lift & Log workouts, plans, nutrition entries, body measurements, or HealthKit data in those requests. As with ordinary web requests, the destination service and network providers may receive or process standard connection metadata such as an IP address, request time, device or network information, and requested URL under their own practices. CrossFit is an independent service and is not controlled by Lift & Log.
Apple StoreKit purchases
If optional tips or monthly support are available in your version of the app, purchases are offered and processed through Apple’s StoreKit and App Store systems. Apple handles the transaction and payment details. Lift & Log does not receive your payment-card number or other full payment-card details.
Apple may provide the app with product availability, transaction status, and verified entitlement information needed to complete or manage the purchase. Apple’s handling of App Store transactions is governed by Apple’s terms and privacy policy.
iCloud synchronization and recovery
Lift & Log uses your private Apple CloudKit database for workout plans, library definitions, schedules, and gym equipment. Your Apple account controls access. There is no Lift & Log account or developer-operated database of these records.
Completed workouts, personal performance history, nutrition, body measurements, weight goals, and Health records stay local and are excluded from CloudKit payloads. The Watch exchanges workout data with its paired iPhone. Earlier beta versions may have replicated personal records; updated devices replace those older payloads with deletion markers. Update all your devices so an older version cannot upload them again. Cleanup requires an iCloud connection.
Synchronization can spread edits and deletions. It is not a backup. Settings → Backup & Recovery creates a plaintext .liftandlog export containing your local history, nutrition, measurements, profile, and provenance. You choose its destination through the system share sheet. Anyone with the file can read it. Use a destination you trust, and delete exported files there when you no longer need them.
Restore validates the file and creates a local rollback artifact before replacing local data. Only planning and library records are republished to iCloud. Protected recovery artifacts and preserved failed stores remain on the device until you remove them through recovery controls. They are not automatically sent to the developer.
Barcode lookup and label scanning
Barcode lookup sends the scanned or entered product code to Open Food Facts. It requests product names, serving descriptions, and nutrition values; no meal history, Health records, or images are uploaded. As with other internet requests, Open Food Facts and network providers receive connection metadata such as your IP address and request time. Their own policies govern that information.
Product results are reused for up to 30 days. The local cache holds at most 200 products. Expired results are removed when looked up again, and older cached products are removed as new ones are added. Camera barcode recognition and nutrition label text recognition run on your device. Review the serving basis and every value before saving.
TestFlight diagnostics
Apple's TestFlight service provides beta installation, usage, crash information, and feedback to the developer under Apple's TestFlight terms and privacy practices. Feedback includes text and attachments you choose to send. Review screenshots for workout, meal, measurement, and Health details before sending them. The app has no third-party analytics SDK or automatic upload of personal records to the developer.
Retention, reset, and deletion
Local records remain until you delete them. Allowed CloudKit records remain in your private database until deleted; deleting the app alone does not remove that replica. Deleting a synchronized record propagates when devices reconnect. Content-free deletion markers prevent delayed devices from recreating records.
- Deleting local entries: Use the app’s available editing and deletion controls to remove individual records.
- Removing all local app data: Deleting Lift & Log from your device removes the app’s local data from that device under iOS behavior. Offloading an app may retain its documents and data, so choose “Delete App” when your intent is removal.
- Developer or beta reset tools: Some development or testing builds may expose a Reset Personal Data action. That action removes personal records and restores the built-in reference catalog.
- Apple Health is separate: Resetting or deleting Lift & Log does not necessarily delete body mass or workout records already written to Apple Health. Manage those records separately in the Health app.
- Device backups: Copies may remain in device backups until those backups expire or are deleted according to your backup provider’s controls.
Because there is no Lift & Log account or server-side user profile, we generally have no remote app-data record to locate or delete on your behalf.
This website
This is a static website. It does not use advertising cookies, tracking pixels, or third-party analytics. If you email support, we receive the information you choose to include and use it to respond to your request.
The site is delivered through GitHub Pages. Like most hosting services, GitHub and network providers may process standard request and security metadata when serving a page. Their handling of that information is governed by their own policies.
Changes to this policy
We may update this policy when the app, its integrations, or applicable requirements change. The “Last updated” date identifies the current version. Material changes will be reflected on this page.
Contact
Questions about privacy or Lift & Log data practices can be sent to support@liftandlog.com.