Lift Log

Privacy Policy

Effective date: October 8, 2026 · English

This policy applies to Lift Log — Gym Tracker (also called Lift Log), its Android and iOS apps, and related services at liftlogapp.com. The Android application ID is com.wise.liftlog.

Lift Log is published by Better World inc. In this policy, “we,” “us,” and “our” refer to the developer of Lift Log.

For privacy questions or requests, contact alexander.ch88@gmail.com.

1. Workout information

Lift Log stores the information you enter, including exercise names, workout dates and times, sets, repetitions, training weights, durations, effort ratings, notes, templates, goals, and app preferences. We use this information to record workouts, display progress, manage rest timers, and provide the features you select.

This information is kept in the app’s local storage. It can leave your device when you use AI coaching, enable cloud sync, export or share information, or write a workout to a connected health service. Analytics also include limited workout usage statistics, described in section 5.

2. Health Connect and Apple Health

Lift Log handles health and fitness data. On Android it can connect to Health Connect; on iOS it can connect to Apple Health through HealthKit. Both integrations are optional and require your permission. You can enable saving workouts and reading body weight separately.

Health data we read

With your permission, Lift Log reads body weight measurements and their measurement dates and times. We use them to display your latest body weight and its trend. The latest reading is cached locally for offline display. The app may refresh readings when it opens or returns to the foreground.

On supported Android versions, Lift Log requests Read health data history so the weight trend can include measurements older than Health Connect’s standard 30-day access window. This does not grant access to additional health data types.

Health data we write

With your permission, Lift Log saves completed strength-training workouts as exercise sessions or workouts. These records include the workout type, start and end times, duration, and supported workout metadata, such as its title and exercise names. A record identifier lets Lift Log update or remove its own exported workout without duplicating it.

Lift Log does not request access to heart rate, steps, sleep, blood pressure, or medical records. It does not write body weight measurements.

How health data is used and shared

Body weight readings obtained from Health Connect or Apple Health are not sent to Lift Log servers, the AI provider, or AppMetrica, and are not included in Lift Log’s in-app cloud backup or history export. If you type health information into an AI message, workout note, or shared file yourself, that information follows the rules for the feature you use.

Workout records created in Lift Log are separate from imported body weight readings. Those workout records may be included in AI context or backups when you use those features. Exporting a workout to Health Connect or Apple Health makes it available within that health service and to other apps you separately authorize there.

We use Health Connect and HealthKit access only for the health and fitness features described here. We do not sell health data, use it for advertising, transfer it to data brokers, or use imported health records to train AI models. Our use of Health Connect data is limited to these user-facing purposes and the applicable Health Connect permissions and limited-use requirements.

Your controls

You can turn either integration off in Lift Log settings and revoke permissions in Health Connect or Apple Health. Turning access off stops future access by the disabled feature; it does not automatically erase records already saved in the health service. Use that service’s own data controls to review or delete those records.

3. AI coach

When you send an AI question, Lift Log sends your message, relevant conversation history, and training context to Lift Log’s server. The server forwards the request to Z.ai, our AI service provider, to generate the answer and suggested exercise plans.

Training context can include recent workouts, exercise names and notes, completed sets, repetitions, training weights, durations, effort ratings, goals, preferences, and workout summaries. During an active workout it can also include exercises already performed, remaining exercises, actual completed sets, and rest-timer state. Workouts you attach to the conversation are included too.

The app does not automatically include body weight readings imported from a health service. However, anything you type or attach to a message can be transmitted, including sensitive information you choose to provide. Avoid including information that is unnecessary for your question.

Chat history is stored locally in Lift Log. Our API processes requests without maintaining a chat-history database, although operational error logs may contain request or response excerpts. Z.ai processes requests under its own service and data-handling terms; we do not promise zero retention by that provider. See Z.ai’s privacy policy.

You can use the workout logger without using AI. Clearing the chat removes its local history but does not automatically delete information already processed by our server or provider. AI responses are general fitness information and are not medical advice.

4. Cloud backups, sync, and exports

If you enable cloud sync, Lift Log uploads and downloads your completed workout history, custom exercises, exercise notes, templates, progression goals, and deletion markers through Google Drive on Android or iCloud on iOS. These copies are stored in your cloud account, not in a Lift Log workout database on our servers.

Google Drive access is limited to Lift Log’s app-data storage. Authentication is handled by Google or Apple; Lift Log does not receive your cloud-account password. The app and the cloud provider process the authorization needed to access your backup.

Lift Log keeps the current backup and a small rotation of older snapshots for recovery. Its in-app backup does not include AI chat history or imported health-service body weight readings. Your device’s separate operating-system backup settings may also apply to local app data.

Manual export creates a workout-history file. If you share or save it, the destination app or person receives its contents. You choose that destination and should protect exported files that contain private notes or fitness information.

See the Google privacy policy and Apple privacy policy for their handling of your account and cloud storage.

5. Analytics, diagnostics, and technical data

The app uses AppMetrica, provided by Yandex, to understand feature use and diagnose reliability problems. The SDK can collect app and operating-system versions, device characteristics, installation or device identifiers, advertising identifiers where available and permitted by the operating system, IP addresses, session and interaction information, and crash or performance diagnostics.

Lift Log also reports feature events and limited workout usage statistics, such as starting or completing a workout, workout duration, and numbers of exercises and sets. These are sent with analytics identifiers; they should not be treated as anonymous merely because they omit your name. We do not attach your workout notes, chat text, or imported body weight readings to these analytics events.

Analytics is initialized when the app starts. Device privacy settings can restrict certain identifiers; restricting an advertising identifier does not disable all analytics. See Yandex’s privacy policy and AppMetrica’s data-handling information.

When you use the website or API, our hosting infrastructure processes technical information such as your IP address, request time, requested path, response status, and error details to deliver and protect the service. This policy page does not use advertising pixels, analytics scripts, or cookies.

If you email us, we receive your email address and the information you include. We use it to answer your question, investigate a problem, or handle your privacy request.

6. Recipients and processing purposes

Recipients depend on the features you use: our hosting infrastructure processes API requests; Z.ai generates AI answers; Yandex/AppMetrica processes analytics; Google or Apple provides optional cloud and health services; and destinations you choose receive exported information. The sections above describe the information involved in each case.

We do not sell your personal or health data. We may disclose information when required by law or when necessary to investigate abuse, secure the service, or establish or defend legal claims. Any such disclosure is limited to the relevant purpose and applicable requirements.

Where applicable data-protection law requires a legal basis, we process information to provide the features you request, with consent where required, to meet legal obligations, or for legitimate interests in operating, securing, and improving the service where those interests do not override your rights. Health-service access depends on your affirmative permission. This policy itself does not grant health permissions or replace consent required for a particular use.

7. Retention and deletion

For information we hold, retention depends on the data’s sensitivity, the purpose of processing, unresolved support or security issues, and legal requirements. We delete or de-identify information when it is no longer needed for those purposes. You may request deletion at alexander.ch88@gmail.com; any legally required retention will be explained in our response.

Lift Log does not create a separate Lift Log user account. Signing in to Google Drive or using iCloud connects your existing provider account. Removing Lift Log data does not delete that Google or Apple account. Uninstalling stops future collection by the app, but it does not erase previously transmitted data, exported files, or cloud and system backups.

8. Your rights and choices

Depending on your location, you may have rights to access, correct, delete, or receive a copy of your personal data, restrict or object to processing, and withdraw consent. California residents may have rights to know, correct, delete, and opt out of sale or sharing as defined by applicable law, without discrimination. You may also complain to your local data-protection authority.

Contact alexander.ch88@gmail.com with “Lift Log privacy request” and enough information to identify the relevant interaction or data. We may need proportionate verification before acting. Do not send passwords or unnecessary health details. Since local workout data is on your device, we cannot retrieve or remotely erase that local copy for you.

You can withdraw health access in system settings, disable cloud sync, choose not to use AI, clear your local chat, and delete or export workout history. Withdrawing permission does not affect processing already completed. A deletion request can be subject to legal exceptions, which we will explain where they apply.

9. Security and international processing

Lift Log uses HTTPS for its production API and cloud-service connections, app-private storage on the device, and operating-system permissions for health access. Access to hosted services is restricted through administrative access controls. No storage or transmission method can guarantee absolute security. Protect your device, cloud account, and exported files.

Our providers may process information outside your country. Z.ai describes processing generally in Singapore, and AppMetrica describes storage in the European Union and Russia; Google and Apple operate international infrastructure. The linked provider policies explain their practices. Applicable protections and transfer requirements depend on your location and the service involved.

If a personal-data breach requires notification under applicable law, we will notify the affected users or authorities as required.

10. Children and policy changes

Lift Log is a general fitness tool and is not directed to young children. We do not knowingly solicit personal information from children where parental consent is legally required without that consent. If you believe a child has provided such information, contact us so we can investigate and take appropriate action.

We may update this policy as the app or our practices change. The current version will remain available at this URL with its effective date. We will provide additional notice or request consent when required for a material change. You may request a previous version or ask questions using the contact address below.