Privacy policy

Your data, plainly.

Workout Pal works without an account. This page explains what stays on your iPhone, what leaves it when you turn something on, who can read it, and how to delete it.

Updated September 23, 2026.

Who makes Workout Pal

Workout Pal is developed by Static Dev. For privacy questions, email staticdevmail@gmail.com. This policy covers the iPhone app and this website.

“Workout Pal’s service” below means our own server at workout-pal.static-dev.com, which runs on Cloudflare Workers with a Cloudflare D1 database. The app talks to no other account server.

On your iPhone

Your workout history, saved workouts and plans, notes, body-weight entries, body measurements, settings and saved gym membership codes are stored on your iPhone. Logging needs no account and works offline. The journal is excluded from iCloud and device backups, so export a copy or turn on encrypted backup to protect against losing your phone. The app also keeps local copies of your journal on the phone: one a day for the last 14 days, and one before each restore or unit correction.

There are no advertising, analytics or tracking SDKs. Exercise images and animations are bundled with the app and load locally. The app doesn’t connect to Apple Health; you can choose to import body weight from a Health export file.

Imports

When you import a file, it’s read on your iPhone. The preview lets you choose whether to keep the original file with your data, which preserves information the app can’t show yet. A kept file can contain more than workouts or body weight, particularly a full Apple Health export, so keeping the original is off by default for Apple Health; without it, only the imported body-weight entries are saved. Kept files are included in your exports, and in encrypted backup and account sync if you use them.

If you import from the Hevy API, your iPhone sends the API key you enter directly to Hevy (api.hevyapp.com) to download your workouts. The key is held in memory for that import only; it isn’t saved, backed up or synced. Hevy’s own privacy policy applies to that request.

Accounts (optional)

An account adds sync across devices and Friends. It lives on Workout Pal’s service and signs in with a passkey: the service stores your passkey’s public key, never your device’s private key, and there is no password.

What an account stores

  • The name you enter when you sign up (1–40 characters).
  • Passkey public keys, and hashes of your sign-in sessions. The app keeps its session credential in the iPhone Keychain. Sessions last up to 30 days.
  • Once you sync: your workout history, saved workouts and plans, settings, notes, body-weight entries, body measurements, saved gym membership codes, any kept import files, and your time zone. The workout in progress is never synced.

Data travels over HTTPS and is stored in Cloudflare D1. Account sync is not end-to-end encrypted: the service can read your synced journal. For a copy only you can read, use encrypted backup.

Who can see it

You, from any device signed in to your account. Authorized administrators of Workout Pal’s service can also view and export synced workouts, plans, workout history and body-weight entries, and see each account’s name, sign-up date and last sync time. Those tools don’t show body measurements, gym membership codes, kept import files or anything from Friends.

The service keeps an activity log of sign-ins, sign-outs, pairing, account deletion and administrator actions: event name, account identifier, time and whether it succeeded. It holds no credentials, IP addresses or training content, keeps at most 5,000 events, and deletes events older than 90 days whenever the log is written or read.

Signing in on more devices

Pairing codes from Add another device and sign-in challenges expire after five minutes and work once. Expired records are removed during sign-in activity. Accounts don’t use browser cookies. Sign out ends this device’s session; Sign out everywhere ends every session and also cancels unused pairing codes and connected-tool tokens.

Friends (optional)

Friends needs an account. Nothing about your training reaches anyone until both of these are true: you and another person have both agreed to be friends, and you have turned sharing on.

Your friends profile

Using Friends creates a profile with a display name (your account name to start with, 1–40 characters), an optional @handle (3–20 lowercase letters, numbers or underscores) and a random eight-character friend code. Sharing starts off. You can change your name and handle, clear the handle, or get a new code at any time; an old code stops working at once.

How people find you

There are no public profiles, no directory and no search. Someone can only send you a request if they know your exact code or @handle; they then see your display name and handle, and you see theirs. Lookups are rate-limited per account so codes and handles can’t be guessed at scale. A request stays pending until you accept it, and declining deletes it. People with a pending request see none of your activity.

What friends see

When sharing is on, each workout you finish is posted as a summary: the workout name, date and start time, duration, number of completed sets, total volume, number of personal records, and, for up to 40 exercises, each exercise’s name, set count and best set. Only completed working sets count. Body weight, body measurements, notes, gym membership codes and your workout in progress are never posted, and the service discards a note even if one is sent. Past workouts you add later aren’t posted. Editing a shared workout updates its summary; deleting the workout deletes the post. A new friend can also see workouts you shared before you became friends.

Accepted friends also see the date of your latest shared workout and how many workouts you shared from the past seven days, which is how weekly standings work. Friends can cheer a post; everyone sees the number of cheers and whether they cheered themselves, not who else did.

Who can read it

Only you and your accepted friends. Shared summaries are stored on Workout Pal’s service and are not end-to-end encrypted. The administration tools don’t display friends, requests or posts, and Friends activity isn’t written to the activity log.

Limits

Up to 200 friends and pending requests per person. The service keeps your newest 2,000 shared workouts and deletes older ones automatically. Each summary is limited to 16 KB.

Stopping and deleting

  • Turning Share my workouts off stops new posts. Workouts you already shared stay visible to your friends until you delete them.
  • Delete all shared workouts deletes every post you’ve shared, and the cheers on them, from every feed. Your own history isn’t touched.
  • Removing a friend deletes the friendship and any cheers between you; you stop seeing each other’s posts immediately.
  • Deleting your account deletes your friends profile, friendships, requests, posts and cheers.

Encrypted backup (optional)

Cloud backup is off by default and doesn’t need an account. When you turn it on, your journal is encrypted on your iPhone with AES-GCM before it’s sent over HTTPS to Workout Pal’s service. The service stores the encrypted journal, an identifier derived by hashing the backup credential, a revision number and a timestamp. It can’t read the backup.

Your recovery key is stored in your iPhone’s Keychain. Anyone holding it can restore or delete the backup, so keep a separate secure copy; we can’t recover a lost key. Backup keeps one encrypted journal; it doesn’t merge changes across devices, and it’s separate from account sync.

Cloudflare processes network information such as your IP address to deliver and protect the service, including rate limiting. The service doesn’t store IP addresses in its database, and request logging is turned off.

Live training status (optional)

Sharing live status is off by default. It needs an account and a separate choice on each device, in Settings → Account & friends → Connected tools. While the app is open during a workout, it sends a status update about every 20 seconds: the workout name and start time, which exercise you’re on out of how many, and completed and total working sets. Workout Pal’s administrators can see this status; friends can’t. The complete workout is not uploaded.

A status disappears 70 seconds after its last update. Turning sharing off, finishing the workout, signing out or deleting the account removes it once the service is reached; if your phone is offline, it simply expires. Expired records are deleted on the next status update.

Connected tools (optional)

If you connect an MCP client, it can read your synced journal, including notes, kept import files and gym membership codes. Connect only a client you trust. Access uses a separate read-only token that expires after 30 days. Revoking it stops future requests but can’t delete copies the client already has.

What appears outside the app

You control notification permission, and the app never asks on launch. Reminders and rest alerts can appear on your lock screen, including a workout name or what’s next. Widgets can show your week’s workout count, a month of workout days with your week streak, and the name of your next or current workout. A Live Activity can show the current workout’s name, rest countdown, duration and completed sets, on your lock screen and, if you wear one, in your Apple Watch Smart Stack.

Exports, CSV files, plan files, PDFs, workout share cards and recap images are created on your iPhone and go only where you send them. Exported JSON and CSV files contain readable training data.

Retention and deletion

  • On your iPhone: data stays until you delete entries, reset the journal or delete the app. Keychain items such as your recovery key and sign-in can remain after the app is deleted.
  • Account: Delete account removes from Workout Pal’s service your synced journal, passkey records, sessions, pairing codes, connected-tool tokens, live status, friends profile, friendships, requests, shared workouts and cheers. Activity-log entries are deleted once they’re 90 days old. Your iPhone’s journal and any encrypted backup aren’t affected, and your passkey stays in your iCloud Keychain until you remove it.
  • Encrypted backup: kept until you tap Delete cloud backup. Turning backup off or deleting the app doesn’t delete it.
  • Exports: remove them from wherever you saved or shared them.

See the step-by-step deletion guide.

This website

This site uses no analytics, advertising, tracking cookies, scripts or forms. Styles, screenshots and fonts come from this site or your device; nothing loads from third parties. Cloudflare receives the network information needed to deliver and protect it. If you email us, your message passes through your email provider and ours.

Changes

We’ll update this policy when our data practices change. Any new processing that needs your choice, such as a future direct Apple Health connection, will be explained before you turn it on.