Last Updated: May 11, 2026
Overview
SimpleLifts is a gym and workout tracking app that prioritizes your privacy. SimpleLifts does not operate a backend server. All of your training data is stored on your device and, optionally, synced to your other devices through your own iCloud account. This policy explains what data we collect, how it’s used, and your rights.
Data We Collect
Data Stored Locally on Your Device
The following data is stored entirely on your device using SwiftData, UserDefaults, App Groups, the Keychain, and the app’s cache directory. This data is never sent to any SimpleLifts server, because no SimpleLifts server exists.
• Workouts and sets — every workout you log, including exercise names, sets, reps, weight, set type (warmup / working), notes, perceived effort (“feel”), gym name, who you worked out with, duration, start/end timestamps, and the workout type. • Exercise library — the catalog of exercises you use, both the bundled defaults and any custom exercises you create. • Templates and programs — workout templates and multi-day programs you build, including their schedule and content. • Run data — for outdoor runs, the route polyline (GPS coordinates), distance, pace, elevation, and any waypoints. For indoor runs, just the distance/pace data you logged. • Health-derived metrics — heart rate, calories, and HealthKit workout identifiers attached to each workout. Read live from HealthKit during workouts; never sent off-device by SimpleLifts. • App settings and preferences — your display options, unit preferences (lbs / kg), enabled features, onboarding status, and tab layout. • Notion connection (optional) — if you connect Notion, the OAuth access token and the database ID you authorized. Both are stored only in your device’s Keychain. • Share-extension drafts — text snippets shared into SimpleLifts that are still in the “parse to workout” review state. • Imported workout history — any CSV files you’ve imported and the workouts they produced.
Data Synced via Your Own iCloud Account
If you are signed into iCloud and have iCloud Drive enabled for SimpleLifts, the items above (excluding the Keychain-stored Notion token, which never leaves your device, and locally cached run polylines, which are bound to the device that recorded them) are synced between your own devices via Apple’s CloudKit framework.
This sync uses your own private iCloud account. SimpleLifts does not have access to your iCloud data — only Apple does, and only as part of the iCloud service you’ve already signed up for under Apple’s own privacy policy. We do not operate any “SimpleLifts servers” that proxy, store, or process your data. You can disable iCloud sync at any time in iOS Settings → Apple ID → iCloud → iCloud Drive → SimpleLifts.
Data Written to Apple Health
With your permission, SimpleLifts writes the following to Apple Health:
• HKWorkout entries — one per completed workout, with the workout type (functional strength training, running, etc.), start/end times, duration, total energy burned, and total distance (for runs).
• Workout route — for outdoor runs, the GPS polyline is attached to the corresponding HKWorkout as an HKWorkoutRoute.
• Heart rate samples — heart rate data captured by the Apple Watch during the workout is associated with the HKWorkout so it appears on the workout detail view in the Health app.
You can revoke SimpleLifts’ write access to Apple Health at any time in Settings → Health → Data Access. Workouts already written remain in Health under your control and can be deleted from the Health app.
Data Read from Apple Health
During an active Apple Watch workout, SimpleLifts reads:
• Live heart rate — used to display BPM on the Watch and attach to the saved workout. • Active energy burned — used to display calories on the Watch and attach to the saved workout.
These samples are read from HealthKit in real time and stored with the workout on your device. They are not sent anywhere.
Location Data
SimpleLifts uses location only during outdoor runs:
• Permission level — “When In Use” only. There is no “Always” or background-location request.
• When location is captured — only while an outdoor run workout is actively in progress. As soon as you end or cancel the run, location tracking stops.
• How it’s used — coordinates are appended to the run’s route polyline as you move. The polyline is stored on your device with the workout, optionally synced via iCloud to your other devices, and optionally attached to the corresponding HKWorkout in Apple Health as an HKWorkoutRoute.
• Where it goes — nowhere outside Apple’s platforms. SimpleLifts has no backend; your route is never transmitted to us.
Third-Party Services
SimpleLifts interacts with third-party services only when you explicitly enable an integration:
| Service | When Used | Data Sent |
|---|---|---|
| Notion API (api.notion.com) | Only if you connect a Notion account. Used to obtain an OAuth token and to append a new row to the database you authorized when you complete a workout. | Notion OAuth flow: the standard OAuth handshake (no personal data beyond what Notion’s own login screen collects). After connection: the workout fields you’ve mapped to your database’s columns (e.g., date, type, duration, total volume, notes). |
| Apple iCloud (CloudKit) | If you’re signed into iCloud and have it enabled for SimpleLifts. | Your workouts, templates, exercise library, and app settings, encrypted and synced through your own iCloud account between your own devices. |
| Apple HealthKit | If you grant Health permissions. | Workouts, heart rate readings, calorie totals, and run routes (write); live heart rate and active energy during a Watch workout (read). Stays on device. |
SimpleLifts does not include any analytics SDKs, advertising frameworks, crash reporting services, or tracking pixels. There is no telemetry sent on launch, on crash, or at any other time.
On-Device Intelligence
• Exercise matching, set-type detection, and workout suggestions are computed entirely on your device. No workout content is sent to any AI or cloud service. • Where SimpleLifts uses Apple’s Foundation Models framework (iOS 26+) for natural-language features such as parsing a shared workout into structured sets, all processing happens locally on your device using Apple’s on-device models. Inputs and outputs never leave your phone.
Apple Watch and Widgets
• The Apple Watch companion app runs as a native watchOS application. It shares data with the iPhone app via Apple’s standard iCloud / App Group mechanisms (not via any SimpleLifts server). • Home-screen widgets and Watch complications read their data from the app’s local on-device store via an App Group container. They do not register for push notifications and do not transmit any data off the device.
Share Extension
When you share text into SimpleLifts from another app (e.g., copy a workout from Notes and tap Share → SimpleLifts), the shared text is delivered to the SimpleLifts share extension by iOS. The text is processed entirely on your device — both rule-based parsing and any on-device AI parsing — and is never sent to any server.
Data Sharing
We do not sell, rent, trade, or share your personal data with any third parties. There is no SimpleLifts backend that could share it even if we wanted to.
Apple’s role in iCloud sync: when you have iCloud sync enabled, your data is transmitted to Apple’s iCloud (CloudKit) under your Apple ID. Apple’s handling of iCloud data is governed by Apple’s privacy policy and is the same mechanism that Apple’s own apps (Notes, Reminders, etc.) use for sync. SimpleLifts cannot see, decrypt, or extract your iCloud-synced data; only your devices, authenticated with your Apple ID, can.
Notion’s role in the optional integration: when you connect Notion, the data you’ve chosen to send (workout rows in your selected database) is transmitted directly from your device to Notion’s API over HTTPS. Notion’s handling of that data is governed by Notion’s privacy policy. SimpleLifts does not act as a proxy.
Data Retention and Deletion
Since SimpleLifts stores data only on your device and (optionally) in your own iCloud:
• Uninstalling SimpleLifts removes all locally stored data, including your workouts, templates, settings, run routes, and cached state. • The Notion OAuth token stored in your Keychain is deleted when you tap “Disconnect Notion” in Settings or when you uninstall the app. Workouts that were already appended to your Notion database remain in your own Notion workspace and are entirely under your control there. • iCloud-synced data is managed by Apple’s iCloud. You can delete it at any time from iOS Settings → Apple ID → iCloud → Manage Storage → SimpleLifts → Delete Data, which removes the app’s data from your iCloud account and from all of your devices that sync it. • Workouts written to Apple Health are managed by Apple Health and can be deleted from the Health app at any time. Deleting them from Health does not delete the corresponding workout in SimpleLifts (or vice versa) — they are stored independently.
Children’s Privacy
SimpleLifts does not knowingly collect data from children under the age of 13. The app does not require account creation, does not collect personal information, and does not communicate with any SimpleLifts-operated server.
Changes to This Policy
We may update this privacy policy from time to time. Any changes will be reflected by updating the “Last Updated” date at the top of this page.
Contact
If you have questions or concerns about this privacy policy, please contact us at:
[azeltzdev@gmail.com]
SimpleLifts is a privacy-first gym and run tracker for iPhone and Apple Watch. Your training data lives on your device and, if you choose, in your own iCloud — never on a SimpleLifts server, because there is no SimpleLifts server. No accounts, no ads, no tracking. Just your workouts, your way.