Privacy Policy

Last updated: October 29, 2026

941 Reps ("the App") is a workout log for iPhone, iPad, Mac, Apple Watch, and Apple TV, developed by 941 Apps, LLC. This policy covers both the App and this website. The short version: your training data is yours. Your log lives on your devices and in your own iCloud — not on our servers. Cloud AI planning sends training context when you request a plan; iCloud sync, coaching, diagnostics and tools you connect have separate data flows, each described below.

What the App stores

941 Reps records the workout data you enter: exercises, sets, reps, weight, RPE, rest times, personal records, and your lifter profile (goals, experience, equipment, and any body metrics or training constraints you type in). That data is stored on your devices and synced between them through your personal iCloud private database (CloudKit).

We have no accounts — there is nothing to sign up for.
Diagnostics are anonymous, limited, on by default, and yours to switch off. From version 1.6.3 the App sends diagnostic and feature-use events from the first launch, including workout-completion events and selected effort ratings, and, on iPhone and iPad, if one of our App Store ads brought you to Reps, which ad, as described below. On iPhone, iPad and Mac the last screen of setup says so; Apple TV has no setup, and its Profile switch describes what is sent. The switch turns it off at any time. Versions 1.6.0 through 1.6.2 asked first and sent nothing until you agreed.
We keep no copy of your complete workout log. Our planning service receives training context when you request hosted AI planning; diagnostics separately include the limited usage values described below.

iCloud sync

Sync uses Apple's CloudKit in your private database, which is tied to your Apple Account and protected by Apple's security model. Apple's handling of that data is governed by Apple's Privacy Policy. Turning off iCloud for 941 Reps keeps your log on-device only.

Coaching (Reps Coach)

Reps Coach is a separate app for coaches and personal trainers. A coach invites you by the email address or phone number of your Apple Account; nothing happens until you open that invite in Reps on your iPhone. From then on your coach reads what you log and plans days on your calendar, and you can message each other, send your movement screen and, if you turn it on in Settings, share your progress pictures. All of it moves through CloudKit sharing between your two Apple Accounts: the shared space belongs to your coach's iCloud account, only the two of you can read it, and nothing passes through a server of ours. Leave the coach in Settings (or your coach takes you off their roster) and the sharing stops; what was already shared stays with your coach, as with anything you send a person. We have no account for coaches either, and Reps Coach collects nothing.

Apple Health stays on its device

With your permission, Reps reads your recent workouts from Apple Health on your iPhone or iPad to attach them to your training log and inform planning. Health-derived measurements (heart rate, calories) are kept only on the device that read them — they are never written to iCloud and never stored by us. When you attach a Health workout to a session, the descriptive facts you can see (activity, duration, date) become part of your own log entry and sync like anything else you logged. Reps never writes anything to Apple Health except the workouts you explicitly save there.

Progress Pics

From version 1.6.0, Reps can take progress photos of you (front, side and back) on your iPhone. They are the most personal thing the App holds, so here is exactly where they go.

Encrypted on your iPhone. Photos are stored encrypted on the device, and the vault opens with Face ID, Touch ID or your passcode.
Synced only through your own iCloud, if you choose. With Sync with iCloud on (offered when you first open Progress Pics, changeable in its settings), the photos, their thumbnails, pose and capture details, any note you type, the body-landmark points used for framing and your mask edits are stored in your private iCloud database, protected by Apple's encryption. That is how they reach your iPad or a new iPhone signed into the same iCloud account. They never go to our servers; we have no server for this feature and cannot see a photo.
Not in your Photos library. The App never writes a progress photo to your Photos library on its own. If you share one through the system share sheet, the copy goes where you send it, under that destination's terms.
No health metrics. Progress Pics does not calculate body weight, body fat or body measurements, and its records have no fields for them. What you type in a note is yours to decide.
Apple TV, only when you turn it on. Show on Apple TV, a switch in Progress Pics settings on your iPhone (off by default), lets an Apple TV signed into the same iCloud account download your photos from your private iCloud database and keep encrypted local copies for viewing. The TV only reads: it takes no photos and never changes or deletes the iCloud originals. Anyone holding that TV's remote can reveal them by holding Select. Turning the switch off revokes viewing as soon as the TV receives the new setting, and the TV clears its local copies.
Erasing is yours. Erase all progress photos, in Progress Pics settings, deletes the vault from that iPhone and requests deletion from iCloud once you type ERASE to confirm; if iCloud cannot be reached, the App keeps retrying the iCloud part until it is done. Turning Sync with iCloud off stops that device from syncing; copies already in iCloud stay until you erase.

AI planning (Reps Pro)

Reps can author workouts and programs with Claude, Anthropic's AI model. This happens only when you make a planning request, and only the context needed to author that plan is sent: your request, your lifter profile (including constraints, injuries, and body metrics you entered), recent workout history and working weights, and descriptive summaries of recent activity (type, intensity level, duration, dates — never heart-rate or calorie measurements).

With a Reps Pro subscription, the request goes to our planning service, which adds the coaching instructions and forwards it to Anthropic. Our service processes requests in memory and stores none of your data; its logs record operational events only (authorization results, request counts) — never your training data or prompts.
Subscription checks verify your App Store purchase cryptographically. We see an anonymous App Store transaction identifier — never your Apple ID, name, or payment details.
Anthropic processes the request under its commercial terms: API inputs are not used to train its models. Our planning service does not retain request content; Anthropic's own retention and deletion policies apply separately to what it receives.
With your own API key (Anthropic or OpenAI), requests go directly from your device to the provider you chose, under that provider's terms. We are never in the path and cannot see them.
Planning context is used solely to generate your plan — never for advertising, profiling, or sale. Ever.

The local CLI and MCP integration

On the Mac, an optional local command-line tool and MCP server can read your training history and propose sessions. These run entirely on your machine. Nothing about this integration transmits your data to us or to any third party; what an AI assistant you connect does with the data it reads is governed by that assistant's own privacy terms and your configuration of it.

Anonymous app diagnostics

On by default, said plainly, with a switch. From version 1.6.3, diagnostics are on from the first launch, as they were before 1.6.0 and as in our other apps. On iPhone, iPad and Mac the last screen of first-run setup says so in one line (Apple TV has no setup; its Profile switch describes what is sent), and the switch described at the end of this section turns them off at any time; turning them off also asks us to delete what that installation sent. Versions 1.6.0 through 1.6.2 asked first and sent nothing until you agreed. A switch you set in any version, on or off, stands. For this anonymous, first-party data we rely on our legitimate interest in keeping the App working and understanding how it is used (GDPR Article 6(1)(f)); the switch is how you object.

To keep the App reliable and to understand which features earn their place, it can send us a small amount of anonymous diagnostic and usage data: crash, hang and performance reports from Apple's MetricKit (performance reports on iPhone and iPad only), and counts of feature use (for example, "a workout was completed", "the paywall was shown", the effort rating chosen for a set). These events can include selected effort ratings, but do not include your complete workout log or progress photos — no names, no account, no health data. Apple TV sends feature-use events only; it does not send MetricKit crash or hang reports.

Each event carries coarse facts: app version and build, OS version, device family (like "iPhone" or "Watch"), the App's language, how the build was installed (App Store, TestFlight or Xcode), a random install identifier the App generates once, stores locally and includes in diagnostic events (it is tied to no account or device serial, it is not an advertising identifier, and a reinstall creates a new one), and a session number that resets after thirty quiet minutes. The identifier lets us count installs and see how a feature is used across launches; it does not identify you, and we make no attempt to link it to a person. Our server adds the country, region and city that Cloudflare derives at its edge from the connection — we never read or store the IP address itself, and no coordinates or postal codes are kept.

Which ad an install came from. On iPhone and iPad, the App asks Apple, through Apple's AdServices framework, whether the install followed one of our App Store ads (a tap on it, or seeing it shortly before downloading). From Apple's answer the App keeps only the numbers identifying the campaign, ad group and keyword, the campaign's country or region, and the download type Apple reports (download or redownload) — no name, no Apple Account, no device identifier, no time of the tap or view. That stays on your device. While diagnostics are on (from version 1.6.3; in 1.6.1 and 1.6.2 only after a yes to wording that named this; in 1.6.0 never as its own event, though after a yes the purchase or trial event carried the campaign and keyword identifiers) the App sends the campaign, ad group and keyword identifiers and the download type to us: once as its own event with the install identifier above (again under a new identifier if you turn diagnostics off and on), and on the event that records a Reps Pro purchase or trial start. We use it to see which of our own ads bring people who go on to use the App, comparing it only with our own Apple Ads campaign reports. We do not link it with data about you from other companies' apps or websites, never share it, and Reps does not track you across apps or websites.

Everything is processed on our own infrastructure (Cloudflare), used solely to fix crashes, improve the App and measure our own App Store ads as described above, and is never shared or sold. We prune active usage records after 90 days. Raw-event archives may remain beyond 90 days until an opt-out deletion request is processed; archive cleanup runs separately and may not be immediate. Aggregate counts may remain.

To turn diagnostics off, or back on: on iPhone, iPad and Mac, use Profile → Settings → Share Anonymous Diagnostics; on Apple TV, open Profile → Anonymous Diagnostics and choose Off. Turning diagnostics off discards unsent events, resets the installation identifier and requests deletion of that installation's stored usage records from active records and archives. A deletion request that fails offline retries when Reps next starts.

Third parties

Third parties that process data for Reps (Apple for iCloud sync, Cloudflare and our hosting providers for the services described here, Anthropic for Reps Pro planning) are required to provide the same or equivalent protection described in this policy and required by Apple's App Review Guidelines.

What this website collects

This site is a static marketing page. It sets no tracking cookies and runs no third-party analytics. Standard web server request logs (IP address, user agent, requested path) are kept briefly for security and abuse prevention, then discarded.

Short links on this site and in our social profiles (for example 941reps.com/ig) forward to the App Store. Each forward records the time, the link used, the country, region and city Cloudflare derives at its edge, the device class (iPhone, Mac, other) and the referring site. No IP address, cookie or identifier is stored, and the counts are only ever read in aggregate.

Children's privacy

941 Reps has no accounts and does not knowingly collect personal information from children.

Changes

If this policy changes, the new version will be posted here with an updated date. Material changes will be called out in the App's release notes.

Contact

Questions about privacy: blake@941apps.com