LiftingView is an iOS app for strength training plans, workout logging and trend analysis. This policy is provided by the developer of LiftingView (referred to as “we” or “us”). It explains how information is handled when you use LiftingView and this privacy policy website, the choices available to you, and how to contact us.
Privacy contact: liftingview@gmail.com.
Training data is stored locally on your device. When iCloud is available and sync is enabled in the app, plans, training records and the body weight you enter manually are synced through Apple CloudKit. Reading Apple Health data requires your permission. Daily step counts, HRV, resting heart rate and sleep data are processed on your device and are not uploaded to CloudKit by the app. Sharing a plan makes the content you select visible to recipients. Tencent CloudBase distributes public plans and hosts this website; the app does not upload your private training records or health data to CloudBase.
1. Information we handle and why
1.1 Training and body records you enter
The training plans, exercises, sets, repetitions, weights, RPE, workout dates and completion status, rest times and training notes you create or edit, as well as the body weight, record dates and notes you enter, are used to save training schedules, log completion, calculate training volume and strength estimates, and display history and trends. Please do not enter sensitive information unrelated to training in free-text fields.
1.2 Apple Health data
With your permission, the app can read daily step counts, resting heart rate, heart rate variability (HRV) and sleep records. These provide activity references, step counts in body weight records, recovery and fatigue references, and trend comparisons. See “Apple Health and sensitive information” below for details of how this data is handled.
1.3 Sync and collaboration information
When you use iCloud sync or plan sharing, the app handles information such as CloudKit user identifiers, record identifiers, sharing participants and permissions, modification times and sync status. This identifies data ownership, merges changes, displays sharing participants and supports collaboration. Sharing interfaces may display participant names or alternative identifiers supplied by Apple. The app does not require a separate LiftingView account and does not provide us with your Apple Account password.
1.4 Purchases and feature settings
Payments for LiftingView Pro are processed by the Apple App Store. The app uses StoreKit to obtain product information, verified transactions and entitlement status to unlock features, restore purchases and display membership expiry dates. We do not receive your bank card number or full payment credentials. Language, training preferences, sync settings and feature usage allowances are stored locally on your device to maintain your settings and the corresponding features.
1.5 Network access and technical information
Browsing public plans sends requests to Tencent CloudBase to download the public catalog and plan files. Checking for updates sends the app identifier to Apple to look up public version information. Visiting this website sends your IP address, request path and technical information supplied by your browser with the request to hosting and network services. These services may process access logs as part of their operations, security and troubleshooting procedures. Such access does not require you to submit private training content.
The app currently does not integrate third-party advertising, cross-app tracking or third-party behavioral analytics SDKs, and does not request advertising tracking permission. We do not sell personal information or use Apple Health data for advertising, marketing or profiling. This website does not set analytics cookies and contains no advertisements, third-party analytics scripts or information submission forms.
1.6 Other optional features
The current workout generation tool creates training schedules locally on your device using built-in rules. It does not send your input or health records to external AI services. If you use a version that supports connecting to a smart barbell, Bluetooth permission is used to connect the device and handle training motion data. You do not need to grant Bluetooth permission if you do not use this feature.
2. Apple Health and sensitive information
Health and body-related information is sensitive. After understanding the purposes, you can choose which types of data the app may read through the Apple Health system permission interface. If you deny or withdraw health permissions, recovery, activity and trend features that depend on that data may not display fully. You can still use training record features that do not depend on those permissions.
The app currently requests read access to the HealthKit types listed above. It does not write workout or body measurement records to Apple Health. Daily step counts, HRV, resting heart rate and sleep data are used for display and calculations on your device. Step counts may be cached locally with body weight records. The app does not upload this HealthKit data to Apple CloudKit or restore old step-count snapshots from CloudKit. The body weight you enter manually is still uploaded to Apple CloudKit when iCloud sync is enabled. This policy therefore does not describe all body-related information as being processed only on your device.
Older versions may have uploaded step-count snapshots to CloudKit with body weight records. The new version neither reads nor continues uploading these cloud snapshots. When the corresponding body weight record is next saved normally to CloudKit, its old step-count field is cleared. Updating the app does not immediately delete all historical cloud snapshots.
Turning off iCloud sync in the app stops subsequent automatic syncing but does not automatically delete existing cloud data. Withdrawing health read permissions also does not automatically delete retained body weight records or locally cached step counts. See Section 5 to manage permissions and data. Recovery, fatigue and strength estimates are training references and are not intended for medical diagnosis or treatment.
4. Storage, retention and security
Training records, plans, preferences and public plan caches are stored on your device. Content with sync enabled is also stored in Apple CloudKit. The Tencent CloudBase environment for public plan resources is located in Shanghai, China, and this website uses static hosting in the same environment. Network distribution nodes may vary by access location. For Apple service storage locations and data handling, refer to your account region, service configuration and Apple’s explanations. You should not assume that all data is stored only within China.
Your records are generally retained until you delete the relevant content or stop using the corresponding storage feature. To prevent syncing from restoring deleted records, the system may retain necessary deletion markers, record identifiers and modification times. Copies independently saved by sharing recipients are outside the control of deletion on your device. Network caches, backups and service logs are retained and cleared by the relevant systems and service providers. Contact emails are retained only as needed to handle requests, resolve disputes or meet applicable obligations.
The app uses safeguards including iOS app storage isolation, Apple’s CloudKit mechanisms and HTTPS network connections. Purchase entitlements are based on StoreKit transaction verification. No storage or network transmission method can guarantee absolute security. Please protect your device and Apple Account, and share links carefully. If a security incident involving your personal information occurs, we will take response and notification measures as required by law.
5. Your choices and rights
- Access, correction and deletion: You can view and edit plans, training records and body weight records in the app, and use the deletion features in the relevant record screens. For actions not provided in the interface, requests for copies of personal information or other privacy rights requests, contact us at the email address below.
- Manage health permissions: Turn off LiftingView’s read permissions by data type in the iOS Health app or the health data access management page in system settings. The system path may vary by iOS version. This does not delete the original records in Apple Health.
- Manage sync: Turn off automatic sync in LiftingView under Settings → Data Sync → iCloud Sync. Local changes are retained and may be uploaded after sync is enabled again. Turning off the switch does not delete cloud data. Before deleting cloud content, check your synced records and sharing relationships. Contact us if you need assistance.
- Manage sharing: Use sharing management to revoke access, change participants or leave a collaboration. Independent copies already imported cannot be remotely retrieved by revoking an invitation.
- Manage other permissions: If you use Bluetooth features, you can withdraw Bluetooth permission in system settings. The app does not require camera, microphone, contacts or precise location permissions to use training record features.
- Purchases and subscriptions: Manage automatic renewal on Apple’s subscription management page. Purchases and refunds are handled under App Store rules. Uninstalling the app does not automatically cancel a subscription or mean that iCloud data or shared copies have been deleted.
We will respond to privacy requests within the time required by applicable law. Where necessary and proportionate, we may confirm the connection between your request and the data to prevent disclosure to others or accidental deletion. For data managed directly by your device or Apple Account, we will explain the relevant steps and permission limitations. Withdrawing consent does not affect processing carried out on the basis of valid consent before its withdrawal.
6. Protecting minors
Minors should read this policy and use the services under a guardian’s guidance. Where personal information of children under 14 is involved, the guardian should give consent as required by law and guide the relevant actions. If a guardian discovers that a child has provided personal information to us without appropriate consent, please contact us so we can address it.
7. Policy updates
When features or data handling practices change, we will update this policy and the dates at the top of the page. For material changes to purposes, scope of processing, sharing recipients or your rights, we will notify you through in-app notices or other appropriate means. Where renewed consent is required by law, we will obtain it separately.
8. Contact us
If you have questions about this policy or wish to exercise rights relating to your personal information, contact the LiftingView developer:
We suggest using “LiftingView Privacy Request” as your email subject and briefly describing your request and app version. Do not send your Apple Account password, payment credentials or full health records unrelated to your request.