Your workout history is designed to stay in your file and on your device.

The normal workout workflow is designed around local browser storage and exportable CSV files.

• Workout history, sessions, sets, templates, and app-state exports stay in the browser and CSV workflow unless you explicitly export or share them.
• Emergency recovery snapshots, app settings, and session state are stored locally to support offline and resume flows.
• Clients using a branded PT file do not need an account for the import flow itself.

Hosted account data is focused on account, entitlement, and PT profile workflows rather than ordinary workout logging.

• Account and authentication records.
• Plan and entitlement metadata for Free, Pro, and PT access.
• PT branding fields, PT public profile fields, and signed PT asset storage paths.
• PT starter-file metadata and private starter-file storage when that feature is used.
• Billing event records and PT export entitlement records.

Card entry and checkout are handled through Stripe-hosted payment flows.

• GymTracker does not process raw card details directly in this repo.
• Stripe handles hosted checkout and billing portal flows.
• Billing records needed to operate paid plans may still be stored by the service and payment providers.

The customer site and app are hosted as static web properties, and normal web requests can create standard operational logs.

• Cloudflare Pages serves the static site and app deployments.
• GitHub is used for repository hosting and deployment workflows for the codebase itself.
• The current reviewed build did not include ad-tech SDKs, analytics SDKs, or obvious third-party tracking scripts.

We aim to keep only the data needed to operate the service, support billing, and maintain PT-facing features.

• Local workout data remains on your device until you export, overwrite, or remove it.
• Account metadata, PT profile data, and billing records may be retained while the account is active and for reasonable operational, support, fraud, or legal reasons afterward.
• PT starter files stay available until replaced, removed, or deleted through service-side handling.
• Payment records may be retained by payment providers according to their own obligations.

The current reviewed build uses storage that appears tied to core product behaviour rather than marketing tracking.

• Local storage and session storage are used for app settings, recovery, account session persistence, and paid-session handling.
• A service worker is used for app delivery and offline-related behaviour.
• Because the reviewed build appears to use only strictly necessary storage for the requested service, a consent banner is not expected to be required unless non-essential trackers or similar tools are added later.

If you need help with billing, account questions, or a privacy request, use the contact route below.

• Email: support@gymtracker.app
• Please include the email address linked to your account if your request relates to account, billing, or PT profile records.
• If your issue is product how-to rather than privacy, the help hub is usually the fastest first stop.