Privacy Policy

Effective and last updated October 23, 2026.

Appstronomy LLC makes REPS Pro. This policy covers the current iPhone app, the public REPS Pro website, and voluntary support correspondence. REPS Pro is being prepared for release. Check Download for public availability. Purchasing and cloud features described as planned are not services already available.

For privacy questions or requests, email [email protected], the existing app feedback contact. Say whether your request concerns an app build, website visit, tester recording, or support conversation.

Your workout library

The current iPhone app stores workout records, routines, notes, settings, and personal media on your device. It does not currently upload that library as structured records to a REPS Pro cloud account. This website does not provide automatic cloud sync or a server backup of your phone's library.

A backup or export goes where you choose to save or send it. Your chosen file provider or recipient handles that copy. See Workout data and backups.

Some workout-related information leaves the device through analytics and eligible tester recordings, as described below. Local storage does not make those transmissions anonymous.

App analytics with PostHog

REPS Pro uses PostHog to understand product use and improve the app. Events describe creating, starting, resuming, and finishing workouts, selected exercise and routine changes, and starting a support request. App lifecycle events record installation, updates, opening, and backgrounding.

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.

The app generates a REPS Pro user identifier on your phone. PostHog uses it to link events to that local user. An installation identifier can be used when the user identifier is unavailable. The data are linked through those identifiers, even without a name, email address, or sign-in.

App product analytics are on in configured distributed builds. There is currently no in-app switch to turn off PostHog analytics. Unknown installation classifications do not capture events. Tests and previews do not send external analytics. Product analytics retention is seven years under the current policy and last verified plan entitlement.

Tester session recordings

Eligible TestFlight builds can use PostHog session replay to record screenshots of what appears on screen. Recordings can show workout photos, notes, custom names, search text, weights, repetitions, and other visible user content. They are linked to the app analytics identity and help investigate tester problems. Replay retention is 30 days under the current policy and last verified plan entitlement.

App Store builds never run replay. The app also refuses replay for Ad Hoc and unrecognized installations. Developers can explicitly enable it for a local development session. Eligibility alone does not mean recording is running; the recording pipeline must also be enabled. Avoid entering content in a tester build that you do not want the testing team to see.

Crash diagnostics with Sentry

Configured distributed builds use Sentry for crash reports, selected handled errors, and selected diagnostic messages. Share Diagnostics defaults on and can be turned off in Settings. The preference applies to that installation. Reports can include the REPS Pro user identifier when attribution is available, plus device, operating-system, app-version, memory, storage, and foreground-state information.

The integration filters out personal names, email addresses, personal notes, and workout values such as weights, repetitions, and effort. Sentry replay, tracing, profiling, app-hang tracking, and automatic and manual session reporting are disabled. Release Health is not currently enabled. Ordinary development builds, tests, and previews do not send Sentry diagnostics.

Turning off Share Diagnostics stops new Sentry diagnostics during normal app operation. It does not turn off PostHog analytics or recall information already queued, sent, or stored.

The last vendor check, on October 6, 2026, verified Sentry's setting to prevent IP-address storage. Sentry still receives the network connection. A first real stored mobile event has not yet been verified against that setting. The chosen free plan retains new events for 30 days; events received during the earlier trial can retain their original 90-day period. We have not independently reverified the plan after the trial. The classification of some technical diagnostic context as performance data is still under review.

IP addresses and location

Loading website or catalog content, or sending telemetry, exposes your IP address and request information to the receiving service. PostHog derives geography from the connection, including country, region, and city.

Our intended PostHog configuration discards raw IP addresses and keeps only country, region, and city. The last verified readback, on October 6, 2026, showed that IP discarding was off in both projects. Stored test events included raw IP addresses and additional derived fields, including latitude, longitude, and postal code. Their removal has not been verified. Treat those fields as potentially retained with analytics until we confirm otherwise. IP-derived coordinates do not come from the phone's GPS.

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 on your device. 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.

Website visits

The public website supports PostHog analytics only when configured for the deployed site. When enabled, it sends selected page views, navigation, calls to action, and download intent, with a public page category, action category, and allowed campaign labels such as source, medium, and campaign.

Website analytics use a PostHog-generated browser identifier stored for the current tab in session storage, or temporarily in memory if storage is unavailable. They use no analytics cookies and do not identify the visitor as an app user. The outgoing filter excludes full URLs, query strings, fragments, raw referrers, entered text, and arbitrary person properties. The library may keep entry-page or referrer information locally in tab storage.

Website replay and automatic interaction capture are disabled. Website analytics do not run when the site detects Do Not Track or Global Privacy Control. These signals do not disable app analytics or the network processing needed to serve a page. Public static pages do not require sign-in. A separately offered REPS Pro web application can use essential session cookies and process account information you submit there; this publication does not launch phone-to-server sync.

Providers and support messages

We use providers to operate REPS Pro. Their own privacy information explains their services:

• Cloudflare provides website delivery and security, and catalog and media delivery infrastructure. It processes network and request information, including IP addresses, to deliver and protect that content.
• DigitalOcean hosts the website origin and server infrastructure. Hosting and security logs can contain IP addresses, request paths, timestamps, browser information, and errors.
• PostHog handles the analytics and eligible tester recordings described above. Sentry handles the diagnostics described above.
• Google Workspace handles our support email. If you email us, we receive your address, message, and any attachments you choose to send. We use them to reply, investigate the request, and maintain the conversation. Starting an in-app support request records that action in analytics; it does not send your email's contents to PostHog.
• Apple operates App Store and TestFlight distribution and any Apple subscription billing. Apple's location and MapKit services support the optional nearby-gym search described above. A backup you save to iCloud uses the Apple service you select.

RevenueCat is planned for subscription management but is not yet integrated into the current mobile app. When introduced, it is expected to handle purchase and entitlement information and a commerce identifier separate from the local REPS Pro user identifier. We will update this policy for the actual integration. See RevenueCat's privacy information.

We do not use these data for cross-company advertising tracking or share them with data brokers. Providers can process information outside your country. We do not promise that all processing stays in one country.

Retention, choices, and privacy requests

The analytics, replay, and diagnostic periods above describe their current policy and available verification. Support correspondence and infrastructure logs do not yet have a verified fixed retention period published here. Copies in exports, email, and provider backups can have different lifetimes. No statement here promises immediate removal from every backup.

You choose what to send in a support message and where to save an export. You can turn off Sentry diagnostics in app Settings and use the website browser signals described above. The current app has no PostHog analytics opt-out. Deleting the app removes its local storage through the operating system; it does not request deletion of telemetry, separately saved backups, or email correspondence.

For an access, correction, or deletion request, email the privacy contact above. Include the app version and build and the kind of information involved. We may need enough information to locate the relevant records and verify your request. Do not send passwords, verification codes, or your whole workout library in the initial message. We will explain the available process and any applicable limits. We do not currently offer a self-service mechanism that erases every provider's records. Rights and exceptions depend on applicable law.

Changes

We will update this page and its date when the policy changes. New purchasing, account, cloud, or data-collection features require updated disclosures based on the offered build. Review this page before using a new build, especially a tester build. For questions, use Support.