Privacy Policy

Last updated: October 23, 2026

Support and privacy email: leanmusclegod.support@gmail.com

This policy describes how Lean Muscle God handles information. No app account is required. The current version has no developer-operated server for uploading records, embedded advertisements, or third-party analytics or tracking SDKs. Workout, meal, weight and profile records are primarily processed and stored on your device.

1. Information processed on your device

You may enter your date of birth, height, weight, biological sex, activity level, fitness goal and target weight. These details are used to display your profile and estimate age, calorie targets and protein targets. You can edit targets manually or skip initial profile setup.

Workout names, exercises, weights, reps, sets, times and unfinished drafts, as well as meal names, dates, calories, protein, nutrition targets and weight records, support workout continuation, history and progress views. Records use a local database. Onboarding status, feature switches and supporting settings use local preference storage. The current app does not provide developer-operated cross-device synchronization.

You can capture progress photos or select them with the system photo picker and save them by date in the app. The app stores image copies, thumbnails, archive dates and creation times for history and photo posters. It does not require access to your entire photo library or automatically upload photos to the developer. The camera is used only when you choose to take a photo and grant permission.

2. Apple Health

After you choose to connect Apple Health and grant permission, the app reads only weight-related records, including values, measurement times, source names and record identifiers used for synchronization. These are stored on your device for weight records and trends. The current version does not write to Apple Health or read other health data types.

You can turn off automatic synchronization on app opening in the app's Apple Health settings, and revoke weight read access in system health permissions. Revoking access does not delete records previously imported into the app. Manage weight entries in the app or clear all business records to remove imported data. Deleting app records does not delete the originals in Apple Health. Health data is not used for advertising, marketing or tracking.

3. Clipboard and external meal analysis

When the app appears, returns to the foreground or receives a clipboard change notification, it may attempt to read clipboard text as permitted by the system to check for meal JSON containing a meal name, calories and protein. It offers the result for your review before adding a meal. Manual import also reads the clipboard. Clipboard text is not uploaded to the developer.

To reduce repeated suggestions, the app stores local fingerprints of handled meal content, handling times and clipboard change counters, up to 20 entries. Entries older than seven days are removed when this history is maintained. Fingerprints are not the original meal text. Clearing all business records does not reset these supporting preferences.

You can manage paste permission in system settings. Manual entry remains available if paste access is denied. Copying an analysis prompt, nutrition summary or JSON writes that content to the system clipboard. Subsequent use by other apps or system features depends on your actions and settings.

The current meal screen does not offer a photo estimation entry point. If you independently send food photos or other content to an external analysis tool, that tool's policies apply. This app does not automatically send photos to it. Review estimated nutrition values before saving imported results.

4. Data transfers you initiate

• Custom and AI training plans: Custom plans and notes are stored on your device. Copying an AI plan prompt writes the current plan, exercise catalog, format requirements and your instructions to the system clipboard. An external AI tool receives this content only if you paste or send it there yourself, and its policies apply. The app does not automatically send plans to an AI service. Imported replies or JSON files are parsed locally for your review, editing and confirmation. Exported or shared plans include plan content and notes; review them before sending.
• Record export: Select dates and record types to create JSON or CSV files and save or share them through the system interface. Selected content may include workouts, meals, weight and profile details. JSON profile exports use age at export rather than date of birth. Exports exclude photos and unfinished workout drafts. Review your selection before sharing.
• Photos, completion cards and photo posters: You can choose to share progress photos, workout data cards or photo posters, or grant permission to add completion images to Photos. Shared content may include your selected photos, dates and workout data. Review it before sending. Saving completion images uses add-only photo permission and does not require reading your entire photo library.
• Calendar: Confirm a workout event containing its name, time and summary in the system event editor. The current implementation does not request broad read access to existing calendar events. Events may synchronize according to the calendar service you select.
• Shortcuts: When you run the app's shortcut action, it can return meal entries, times, calories, protein and totals for a selected date. Later actions may save or send those records. Review workflows you configure.
• External link requests: The app can display a selected day's meal JSON. Only after you tap the return-data button does it attach the content to the displayed callback address and open that address. The destination may be another app or an HTTPS website and may receive those records. You can instead copy, share or close the screen.
• Live Activities: When enabled, the system can display the workout name, elapsed time, pause state, current exercise, weight, reps and next set number on the Lock Screen or Dynamic Island, with a button to record the next set. Disable this in app or system settings if desired, and consider what is visible on your Lock Screen.

Copies sent to another app, website, Photos, Calendar or external storage are governed by that service and your settings. Clearing this app's records does not remove those copies.

5. External links and support

Video tutorial links open movement searches on Bilibili or YouTube using exercise-related search terms. They do not attach your workout history, weight or profile. The app also links to a YouTube introduction video and GitHub feedback. Those services may process network requests and information you submit. Their privacy policies apply.

GitHub Issues are public and may require a GitHub account. Do not post dates of birth, health records, export files or other sensitive information in a public issue.

If you contact the developer by email or a feedback channel, the developer processes the contact details, description and attachments you provide to respond and investigate the issue, not for advertising or tracking. Share only what is needed. Support communications are retained for as long as needed to handle the request. Contact the email above to request access, correction or deletion. Information required by law may be retained. Public copies or copies held by external platforms may also require action through those platforms.

6. Retention, deletion and backups

Edit or delete supported individual entries, or use Settings → Data Management to clear workouts, meals, drafts or all business records. Clearing all business records removes custom training plans, profile, weight, imported health weight and sync state, and resets nutrition targets. It does not erase the system clipboard, every supporting preference, exported files or copies held by external services.

Progress photos can be deleted individually. Clearing all business records also removes app-local photo copies and thumbnails. Clearing only workout records keeps progress photos. Deleting app-local copies does not delete originals in Photos or copies you have already shared.

Local records are generally retained until you delete or clear them. Deleting the app, as distinct from offloading it while preserving documents and data, generally removes its local container. Historical copies may remain in device or computer backups. Backup, restore and Apple service processing depend on your system settings and Apple's policies. Local cleanup does not promise automatic deletion of backup copies.

The developer cannot remotely access your local database and therefore cannot retrieve or delete device records for you. Protect access to your device and files you share.

7. Intended use and policy changes

The current personal target estimator is intended for adults. The app is not designed for children. Fitness suggestions and nutrition estimates provide general recording and reference functions and do not replace medical services.

If a future version introduces network services, data collection or new permission purposes, this policy will be updated with explanations and appropriate authorization where needed.