Privacy Policy

Effective and last updated October 23, 2026.

Appstronomy LLC provides REPS Pro. This policy covers our apps, website, account services, and support. It explains the information we process when you use those services, including optional features you choose to enable.

For privacy questions or to exercise your rights, email [email protected]. Appstronomy LLC is responsible for the processing described here.

Workout records, accounts, and sync

REPS Pro stores your workout library on your device. It can contain workouts, routines, exercises, sets, repetitions, weights, effort, notes, training locations, settings, profile details, and personal media. An identifier created for each REPS Pro user distinguishes their records, including when several local users share an installation. Selecting a local user is not a sign-in or proof of permission to use someone else's information.

When you use an account or a connected feature such as synchronization, server backup, or sharing, we process the information needed to provide that feature. This can include your account identifier, email address, sign-in provider identifiers, profile information you supply, settings, workout records, synchronization changes, and access permissions. We use these records to authenticate access, keep your data available across supported devices, resolve updates, and provide the features you request. Local use and App Store subscription recovery do not require a REPS Pro server account.

Your private workout records do not become public merely because you synchronize them, select a gym, or buy Premium. Sharing occurs through the recipients, permissions, or publishing action you choose. A recipient can retain a copy you send outside REPS Pro, even after you remove your own copy or revoke further access.

Personal recordings, photos, and backups

Personal recordings are stored in private app-managed storage on your device. Importing through Apple's Photos picker creates a copy in REPS Pro. Capturing or importing media uses the camera, microphone, or photo access needed for the action, subject to the permissions you grant. We do not upload personal recording files as part of cloud sync or promise that those files are available on another device.

You can export an independent copy to Photos or another destination. A backup contains a data file and, if you choose to include personal media, a companion media archive. The destination you choose, such as iCloud Drive or another file provider, handles that copy under its own terms. Restoring the data file without its media can leave a recording unavailable until the matching media is restored.

Deleting a recording removes it and its uses from your REPS Pro account records. Cleanup of app-managed files can finish later if the device cannot complete it immediately. Original Photos items, independent exports, and backups you have saved elsewhere remain under your control. Eligible tester session recordings can capture visible personal media, as explained below. See Workout data and backups.

Optional Apple Health integration

If you connect REPS Pro to Apple Health, Apple's permission controls determine the health and fitness categories the app can read or write. We use the permitted information to provide the health and workout features you request. Each installation associates Apple Health with one local REPS Pro user, so selecting another local user does not transfer that association or authorize access to another person's Health data.

You can change permissions in Apple's Health or device settings. Revoking access stops further access through that permission; it does not automatically remove information already saved in REPS Pro or Apple Health. We do not use data obtained from Apple Health for advertising, marketing, or data brokerage, and do not send those Health records to PostHog or Sentry. The separate analytics described below include limited facts about app use and workouts entered in REPS Pro.

Product analytics with PostHog

We use PostHog to understand how people use REPS Pro, evaluate features and markets, improve the product, and investigate support issues. Events describe app installation, updates, opening and backgrounding, navigation and selected actions, workout creation and completion, exercise and routine changes, and starting a support request.

Events can include duration, set and exercise counts, completion and plan-adoption states, target-muscle codes, and catalog exercise or routine names. Technical context includes app version and build, device model, operating system, display size, weight unit, locale, time zone, and network type. Ordinary analytics events exclude the actual weights and repetitions you enter, personal note text, and custom workout and exercise names. We do not send your full workout library to PostHog.

PostHog links app events through your REPS Pro user identifier. An installation identifier can be used when that identifier is unavailable. These identifiers make the information linked to a user even when we do not send a name or email address. App product analytics are enabled as part of the service and have no general in-app opt-out switch. Where applicable law requires consent or gives you a right to object, those requirements and rights apply. Installing the app does not waive them.

We retain product analytics for seven years to study long-term product use, subject to valid deletion requests and legal requirements.

Tester session recordings

With the tester's consent, eligible TestFlight and positively identified Ad Hoc builds use PostHog session replay to record what appears on screen. Developers can also enable replay for an explicitly selected development session. App Store builds never run session replay. Replay remains off when the installation cannot be confirmed as eligible.

These recordings can show notes, photos, custom names, search text, weights, repetitions, and other visible user content. They are linked to the app analytics identity and help us reproduce problems and improve the app. Do not enter another person's private information into a recorded testing session without their permission. We retain tester recordings for 30 days. Tester recording is separate from ordinary app analytics and from personal workout videos you create.

Crash and reliability diagnostics with Sentry

We use Sentry for crashes, selected handled errors, diagnostic log messages, and Release Health session reports. Reliability information can include application termination and resource-use summaries supplied by Apple's diagnostic services. We use it to find failures, measure release stability, and resolve support issues.

Reports can include the REPS Pro user identifier when available, Sentry installation and session identifiers, device and operating-system details, app version and build, memory and storage information, foreground state, and technical context about the operation that failed. We exclude personal names, email addresses, personal notes, and workout values such as weights, repetitions, and effort. Sentry is configured to prevent storage of IP addresses. Sentry session replay, performance tracing, and profiling are disabled.

Share Diagnostics is on by default and can be turned off in app Settings for that installation. Turning it off stops collection and transmission of new Sentry diagnostics during normal operation, including Release Health sessions. It does not turn off PostHog analytics or recall diagnostics already stored or being sent. We retain Sentry diagnostic events for 30 days.

Subscriptions and purchase information

Apple processes App Store payments. RevenueCat provides subscription management, receipt validation, restores, and Premium entitlement information. Purchase processing includes a commerce identifier, App Store transaction and receipt information, purchased products, purchase and renewal dates, subscription status and expiry, trial or offer status, refunds, and relevant storefront, locale, price, and currency information. RevenueCat's purchase and subscription-management screens can also process the interactions needed to present and manage an offer.

We use this information to provide and restore paid access, answer purchase questions, prevent purchase abuse, and understand subscription performance. RevenueCat's commerce identifier is separate from the local REPS Pro user identifier. Restoring a subscription does not merge workout histories. We do not provide RevenueCat with your workout library or Apple Health records, and do not connect its customer records to PostHog or Sentry through vendor integrations. Selected purchase failures can be reported through the Sentry diagnostic rules above.

We do not receive your full payment card details. Apple retains its own billing records. Purchase and entitlement records are kept as needed to operate and restore subscriptions, comply with financial and legal obligations, and resolve disputes. Cancelling a subscription or deleting the app does not automatically erase those records.

IP addresses, gym locations, and public contributions

Our infrastructure and providers receive IP addresses and request information when they deliver a page, catalog item, video service, or telemetry request. Hosting and security logs can retain connection information to operate and protect the service.

For PostHog analytics, we discard raw IP addresses and retain only country, region, and city derived from the connection. We exclude additional IP-derived latitude, longitude, and postal-code fields from stored analytics. IP-derived coordinates do not come from the phone's GPS. These controls do not prevent the network processing needed to deliver a request or the separate security logging described here.

Separately, if you choose Use my location when adding a training location, the app requests location permission when needed. It uses the device coordinates supplied by iOS to search for nearby gyms through Apple's MapKit service. This device location may be precise, depending on your permissions and the location iOS supplies. You can enter a location name and optional address manually instead, without granting location access.

When you save a gym result, the app saves a training-location selection. Saved location records can include the gym's name, address, coordinates, and Apple Maps identifier. These saved gym details are separate from the device location used to center the search. A private training location remains your account data. When a selected location matches a public gym, the service can maintain public gym information obtained from the mapping provider. That public directory does not expose your workout history or identify you as a visitor.

If you choose to contribute equipment information or confirm or dispute an equipment entry, we process that contribution to maintain the gym's shared equipment information and confirmation counts. The public copy does not link back to your private training records. Do not put personal information into a public equipment contribution.

Website analytics, cookies, and external video

Our public website uses PostHog for selected page views, navigation, calls to action, and download intent, together with page and action categories and allowed campaign labels. It uses a browser identifier held in the current tab's session storage, or in memory if that storage is unavailable. Public-site analytics use no analytics cookies and do not identify a visitor as an app user. Outgoing events exclude full URLs, query strings, fragments, raw referrers, entered text, and arbitrary person properties. Entry-page or referrer information can remain locally in tab storage.

Website session replay and automatic interaction capture are disabled. Website analytics respect detected Do Not Track and Global Privacy Control signals. These browser signals do not disable app analytics or essential processing needed to serve a page. Account services can use essential cookies for sign-in, session security, and preferences.

If you open an external reference or play an embedded YouTube video, that provider receives connection and playback information such as your IP address, device or browser information, the requested video, and interactions with its player. Embedded content uses Apple's WebKit and can use cookies or other web storage under the provider's control. REPS Pro uses YouTube API Services through a Cloudflare video-eligibility lookup, which sends the recognized video identifier and ordinary request information before eligible embedded playback. YouTube can serve advertisements in its player and process the associated interactions. It does not send your private workout library. We do not download or independently host YouTube streams or integrate your YouTube account.

External sites and embedded providers apply their own terms, privacy policies, and choices, including YouTube's terms and Google's privacy policy. Saving a link does not make us responsible for the destination's data practices.

Who receives information

We use service providers for the purposes described in this policy:

• Cloudflare delivers and protects website, catalog, media, and video-eligibility services.
• DigitalOcean hosts our website origin and account infrastructure.
• PostHog, Sentry, and RevenueCat process the analytics, diagnostics, and commerce information described above.
• Google Workspace handles support email. We receive your address, message, and attachments when you contact us. We use them to respond and investigate. An analytics event about starting a support request does not contain the email's contents.
• Apple provides App Store and TestFlight distribution, billing, Apple Health permissions, MapKit and location services, and any Apple file service you choose.

Authorized personnel and providers can access information as needed to operate, secure, and support the service. We can disclose information to comply with law, respond to a valid legal process, protect people's safety or rights, investigate misuse, or carry out a business transfer subject to applicable privacy protections. We also disclose information when you direct us to share it.

We do not sell personal information, provide it to data brokers, or use it for cross-company advertising tracking. External content providers process their own player and website interactions under their policies.

Retention, security, and international processing

We keep account and synchronized records while needed to provide your service, and remove or de-identify them when no longer needed, subject to your requests and applicable obligations. Support correspondence and operational logs are kept for the time needed to resolve requests, maintain security, meet legal requirements, and handle disputes. Analytics, tester replay, and Sentry events follow the periods stated above. Information retained for a legal obligation is restricted to that purpose.

We use safeguards appropriate to the information, including access controls and protected network connections. No storage or transmission method is completely secure. Providers can process data outside your country, where privacy laws may differ. Where applicable law requires transfer safeguards, we use the required contractual or other lawful protections. Contact us for information about safeguards relevant to your data.

Copies in independently saved backups, recipients' exports, Apple's records, and providers' recovery systems can have different lifetimes. Deletion does not promise immediate removal from every backup; retained recovery copies remain protected and are removed through their retention cycle.

Your choices and privacy rights

You control optional device permissions, the information you enter, your sharing actions, and where you save exports. You can disconnect Apple Health, change location and media permissions in device settings, and turn off Share Diagnostics. Deleting the app removes its local storage through the operating system; it does not cancel a subscription or erase synchronized records, telemetry, email, or independently saved copies.

Depending on applicable law, you can request access, a copy or portability of your information, correction, deletion, restriction, or object to particular processing. You can withdraw consent where we rely on it without affecting earlier lawful processing, and complain to the privacy regulator responsible for your location. We do not discriminate against you for exercising a privacy right. We do not use your information to make solely automated decisions that produce legal or similarly significant effects.

We process information to provide the service and purchases you request, meet legal obligations, and pursue legitimate interests such as security, reliability, support, and product improvement where that basis is available. We rely on consent when required, including optional permissions and tester recordings. These grounds depend on the processing and applicable law; a general acceptance of terms does not replace a required consent.

Send requests to [email protected]. Tell us which service and records are involved. We may need enough information to locate records and verify your authority, including when you act for another person. Do not send passwords, verification codes, or your whole workout library in the initial message. We respond under applicable deadlines and explain any lawful limits, such as required purchase-record retention or copies outside our control.

Children and policy changes

REPS Pro is a general fitness product and is not directed to children. If you believe a child has supplied personal information without legally required authorization, contact us so we can investigate and remove it as required.

We update this page and its date when our practices materially change, and provide additional notice or seek consent when required. For help, visit Support.