Privacy

Effective November 2, 2026

FitNessie is a lifting log for iPhone and Apple Watch, made by the company named in our Terms of Service ("we"). This policy covers the app, its server and fitnessie.app. It lists everything we store, where, why, and how to delete it. Washington and Nevada residents: our Consumer Health Data Privacy Policy covers the same data in the terms those laws use.

Your account

You use FitNessie with an account. You sign in with an emailed sign-in link, with Google or with Apple. Our server stores:

• Your email address (from what you type, or from Google or Apple), whether it's verified, and a name if Google or Apple supplies one.
• Your sessions: a session token for each signed-in browser, iPhone and Apple Watch, with its expiry, and the IP address and device description it was created from.
• Your sign-in provider link: your Google or Apple account id, and the tokens that provider returned at sign-in.
• Short-lived sign-in records: sign-in link codes, and the codes the app uses to sign in. They expire and are removed.
• Do-not-email list: if mail to an address bounces, we keep a keyed one-way hash of that address (not the address) so we stop sending to it.
• Audit log: a record of account events such as an account being created or deleted. It identifies you by a keyed one-way hash of your email address, not the address. Entries are kept 365 days.

Sign-in emails are sent through Amazon SES from notify.fitnessie.app.

What our server stores

• Routines: names, notes, order, and each exercise's planned sets, weights, reps and rest.
• Workouts: exercise names, sets and their types (warm-up, drop, failure, AMRAP), weights, reps, distances and durations, the side and equipment where you set them, effort (RPE or RIR) if you log it, rest times, notes, when each workout started and ended, and your bodyweight at the time (for bodyweight and assisted exercises). A per-set index of the same data powers exercise history and PRs.
• Exercises you create: each one's name, primary muscle, equipment and how its sets are measured, so it shows up like a library exercise on all your devices. Custom exercise names may be reviewed in aggregate, as counts with no one identified, to decide what to add to the exercise library; when the library adds one, yours switches to it with your history.
• Machine styles: the style you pick for a machine movement (selectorised, plate-loaded, cable or Smith), and the gym it applies to if you set one.
• Bodyweight and body measurements you log in the app: the value, its kind (bodyweight, body fat, waist and other circumferences) and when it was measured.
• Imports: a Strong or Hevy CSV you import is kept only until it's parsed, then deleted. Each import keeps a record of its status, its counts and which workouts it created, so you can revert it.
• Push tokens: each device's Apple push token, its platform (iPhone or Watch), the app's bundle id and push environment, and when the last push went through or why it failed. They're used only for silent pushes that bring a routine change to your phone and watch.
• Sync acknowledgments: when a routine change reached a device: which device (iPhone or Watch), how it arrived (push, poll, from the other device, or on opening the app), the routine id, timestamps and the delay. They're used only to measure whether sync is reliable.
• AI connector state: whether you turned the connector on and when, and a SHA-256 hash of the connector's token. The token itself is never stored.
• AI assistant grants: when an assistant connects through sign-in (OAuth), the authorization server keeps its registration, the grant you approved, and the codes and tokens issued, until they expire or you revoke them. We also keep a consent record for each connection: which assistant, what it may read and write, the wording you were shown, and when you allowed and withdrew it.

We don't collect your phone number, location, contacts or an advertising identifier.

The launch waitlist

If you join the waitlist on a program page of fitnessie.app, we keep your email address, when you signed up, which program page you used and which version of the consent line you saw. We use it for one thing: a single email when FitNessie is on the App Store, sent from notify.fitnessie.app. After that email goes out, the list is deleted. Signing up sends you nothing now, and the address is never shared or used for anything else. To be removed before then, email support@fitnessie.app from that address and we'll delete it and confirm.

To limit abuse, the form counts sign-ups per connection for an hour using a one-way hash of your IP address and the hour; the IP address itself is never stored.

Purchases

FitNessie Pro is bought through Apple. Apple handles payment; we never see your card or Apple ID. Our server stores, for each purchase, its Apple transaction id, product, type, environment (production or sandbox), ownership type, expiry, grace period, renewal and trial status, refund or revocation date, and the account it belongs to. It also keeps a log of every App Store Server Notification Apple sends us about it, including the decoded transaction and renewal details. Deleting your account deletes your purchase rows, but not the notification log: those rows stay, no longer linked to your account, so we can answer a billing dispute. We have not set a deletion date for them. Deleting your data doesn't cancel a subscription: cancel it in your Apple ID's Subscriptions settings.

Server logs and error reports

Our server writes one log line per request (what was requested and how it went), plus error lines. Logs are shipped to an Amazon S3 bucket, where they expire after 30 days. Server errors, and errors on the sign-in pages, are also reported to Sentry. Before anything leaves our server or your browser, we strip cookies, request bodies, authorization headers, token-like query values and IP addresses from those reports. Cloudflare, which sits in front of fitnessie.app, sees the IP address and request of each visit as it passes traffic through.

Apple Health

With your permission, FitNessie:

• saves each finished workout to Apple Health;
• on Apple Watch, reads heart rate and active energy during a workout to show them live and attach them to that Health workout;
• saves the bodyweight, body fat and waist measurements you log in FitNessie to Health, and reads those types from Health (a smart scale's readings, say) to show them next to yours.

Data read from Apple Health stays on your devices. It is never sent to our server, never used for advertising or marketing, and never shared or sold.

Claude and ChatGPT

FitNessie can connect to an AI assistant: Claude, by Anthropic, or ChatGPT, by OpenAI. The connector is off until you turn it on in the app (Settings › Claude & ChatGPT) and agree to what it can do. Once it's on, the assistant you connect can:

• read your routines, workouts, exercise history and measurements;
• create, update and delete routines, log, update and delete workouts, and log measurements.

What the assistant reads is then handled under that provider's privacy policy (Anthropic, OpenAI). Turning the connector off in the app invalidates its token on our server at once; the assistant can't read or write anything after that.

Community programs

With a FitNessie account you can publish a program to the community library. What you publish is public, on fitnessie.app and in the app: your handle, and the program's name, summary, description, tags, and each day's exercises, sets, reps and progression rules. Your weights, notes and workout history are never published. We also keep, with your account, the programs you star (how many stars a program has is public; who starred it isn't), reports you file, and authors you block. You can unpublish a program at any time unless it's under review, and deleting your account deletes all of it.

Who else sees it

We don't sell your data and don't share it for advertising. These companies handle it for us or at your direction:

• Amazon Web Services: our server and its Postgres database run on an Amazon EC2 server in the US (us-east-1); backups and logs are in Amazon S3; sign-in emails go through Amazon SES.
• Cloudflare: serves fitnessie.app and passes traffic to our server.
• Sentry: receives scrubbed error reports (see above).
• Google and Apple: if you sign in with them, they tell us your email address and, if they supply it, your name. Apple also delivers the push notifications for routine sync and sends us purchase notifications. The website loads its fonts from Google Fonts, so your browser contacts Google when you open it.
• The AI assistant you connect, as described above.

FitNessie has no ads, no analytics SDKs, no trackers and no pixels. fitnessie.app sets no cookies until you sign in; signing in on the web sets the session cookie that keeps you signed in.

How long we keep it

Your account and training data stay until you delete them. After you delete, copies remain in our backups: a full database backup every 6 hours and a copy of the core tables every 5 minutes, kept in Amazon S3 for 30 days, then expired. Other retention:

• Audit log entries: 365 days.
• Server logs in S3: 30 days.
• Expired sign-in and authorization records: removed within the hour.
• Apple purchase notifications and the do-not-email hashes: no deletion date has been set.

Your choices and rights

• Export: Settings › Export gives you everything as a CSV or JSON file.
• Correct: edit any routine, workout or measurement in the app.
• Delete: delete single workouts in History, or Settings › Delete all my data, which permanently deletes your account and everything in it on our server at once: your sign-in and sessions, routines, workouts, measurements, custom exercises, machine styles, imports, push tokens, sync acknowledgments, the connector, assistant grants and consent records, purchase rows, and anything you published or starred in the community. There's no undo. What remains is described under Purchases and How long we keep it. Workouts already saved to Apple Health stay there; delete them in the Health app.
• Withdraw consent: turn the AI connector off in Settings, and Health access off in the Health app or iOS Settings.

You can also email support@fitnessie.app for any of these. We respond within 45 days.

Children

FitNessie isn't directed at children under 13, and we don't knowingly collect their data.

Security

Data travels over encrypted connections (HTTPS). Each account's training data is isolated to that account in the database with row-level security. If a breach ever exposes your data, we'll tell you without unreasonable delay and within 60 days.

Changes and contact

If this policy changes, the new version is posted here with a new effective date. Questions go to legal@fitnessie.app.