Your data, in plain language.

Scope and contact

This policy covers the Iron Progression mobile app and this website. The Android app's package identifier is com.ironprogression.app. For questions or requests, email [email protected].

Training records stay local

The app stores your profile, exercise records, workout history, sets, reps, load, effort ratings, duration, distance, programs, preferences, body weight, and measurements locally on your device. These records support workout planning, progression, and Reports. Core workout logging does not require a network connection.

Local-first does not mean the app never connects to the internet. App updates, diagnostics in configured builds, external services you open, and files you choose to share are described below.

Progress photos and device permissions

When you add a progress photo, the app copies the selected or captured image into app storage and saves its record locally. Camera or photo access supports that action. Notification permission supports rest-timer reminders. File selection and sharing are used for backup import and export.

You can review or revoke permissions in your device settings. Declining a permission can prevent the associated feature from working. Deleting an app-managed photo does not delete an original in your photo library or a copy you shared elsewhere.

JSON backups and external copies

Data Backup exports a JSON file of database records. It includes progress-photo metadata and file references, but not the photo image files. Keep images separately if you need them after reinstalling or changing devices. Importing a compatible backup replaces local records rather than merging histories.

You choose where to save or share an export. A JSON backup is readable data, not an encrypted archive; anyone with access to the file may be able to read its contents. Local recovery copies and previously exported files can retain earlier records. Device or cloud backups, where enabled and supported, are also subject to the settings and practices of their providers.

Build-dependent diagnostics and Sentry

Crash reporting is an optional build integration. Builds configured with Sentry can send crash and error details, diagnostic breadcrumbs, session information, and app, operating-system, device, and update metadata to help diagnose failures. Open Privacy Policy in the app's Settings to see whether crash reporting is enabled in that build.

The Sentry configuration disables default personal-information collection and excludes console breadcrumbs. Error details can still contain context from a failing operation, and transmission involves network information such as an IP address. Deleting local app records does not delete diagnostics already sent. See Sentry's privacy policy for its practices.

Expo updates and external services

The app connects to Expo services to check for and download updates. Those requests can involve network and app or update metadata. See Expo's privacy policy.

If you open an exercise technique search, a store listing, or another external link, or share a file with another service, that service receives the information involved in the request or file. Its own privacy policy applies. An external search or update request is separate from storing your workout history locally.

Website visits and server logs

The website host and signup service process requests to deliver pages, accept signups, troubleshoot errors, and protect the service. The site does not use advertising trackers, analytics cookies, or routine page-access logs. The signup service temporarily uses process-specific, pseudonymous client identifiers in memory to limit abuse; it does not save IP addresses in signup records. Operational error logs and hosting providers can still process request metadata, such as IP addresses, paths, and timestamps. These records are separate from the mobile app's local training database.

iOS launch emails and support messages

The iOS notification form asks for an email address. The signup record also includes its platform category, source page, signup time, and the time of its iOS notification request. We use it to send iOS launch information and manage the list. Signup is not necessary to use the available Android app.

If you previously submitted training context through an earlier form, the stored record may also include your tracker, training style, platform, or written feedback. Those details are not needed for the current email-only signup.

If you email support, we receive your email address, message, and any attachments you choose to send. Share only what is needed to explain the issue. Website hosting and email services process information needed to provide their services.

Retention, deletion, and your choices

Local records remain until you delete or replace them, or remove the app and its data. Use the workout and body-progress screens to delete records where supported. Removing the app or clearing its storage can erase records and app-managed photos; export what you need first. Photo-file cleanup can fail and may require another attempt.

Original photos, exported backups, device backups, recovery copies, and diagnostics already transmitted are separate copies. Manage them with the device or service that holds them. We cannot retrieve or erase records held only on your device through an email request.

To stop launch emails or request access, correction, or removal of website signup or support information, email us from the relevant address. We may need enough information to verify and locate the record. Signup and support records are kept to manage the list or request; retention can differ for operational logs and service backups. Depending on where you live, you may have additional privacy rights, including contacting your local data-protection authority.

Policy changes

We may update this notice as the app or website changes. The date above identifies the current version. Contact us if a disclosure does not match the behavior you observe.