Privacy Policy
This policy explains what Workout Buddy (“the app”, “we”) collects, why, where it lives, and how to delete it. If anything here is unclear, email support@work-out-buddy.com.
Who we are
Workout Buddy is a personal workout tracker. It is published by an individual developer based in the United States. We do not sell user data, share it with advertisers, or use it for cross-app tracking.
What we collect
We only collect what the app needs to work. Everything below is tied to your account and stored in our database (Supabase, hosted in the United States) unless noted.
Account & profile
- Email address (used to sign in and to recover your account)
- Display name (set by you, or pulled from your Apple/Google account on first sign-in)
- Authentication identifiers from Apple or Google when you use Sign in with Apple / Google
- Per-account preferences: weight unit, theme, accent color, rest timer settings
Profile photo (optional)
- If you choose a profile picture, the image you pick is uploaded to our storage (Supabase Storage, United States) and linked to your account so it shows on your other devices.
- This is the only reason the app asks for photo-library access, and only when you tap to change your picture. You can remove the photo any time from the Profile screen, which deletes it from storage.
Workout & fitness data you create in the app
- Bodyweight entries (weight + date) you log
- Workouts: programs, days, exercises, sets, reps, weights, completion status, and post-session feedback (recovery / pump / volume ratings)
- Custom exercises you create (name, muscle group)
- Session timestamps and duration
Nutrition (when available)
- Your nutrition phase, protein targets, food staples (names, protein amounts, and optional calories), and individual protein log entries are stored on your device. The full nutrition log is not synced to our account database.
- Nutrition summaries are sent to Buddy when you chat, and nutrition interaction events are sent to PostHog, as described below. Optional Apple Health writes are described under Apple Health.
Buddy, the AI coach (Anthropic)
- When you chat with Buddy, your messages and a snapshot of your training context — your programs, recent sessions, post-workout feedback, personal records, bodyweight, and display name — are sent to Anthropic (the maker of Claude) so Buddy can answer as your coach. We send only what's needed to respond.
- When nutrition is enabled, that context also includes your current day's protein target, logged and remaining grams, nutrition phase, and weekly protein adherence summary. It does not include your full nutrition log or food names unless you put them in a message.
- Anthropic processes these messages on our behalf to generate the reply and, under their commercial API terms, does not use them to train their models. We never use your chats for advertising.
- We store a per-month message count and a small cost figure for your account in our database to enforce fair-use limits. We do not sell or share your chats with anyone else.
Subscriptions (only if you subscribe)
- Workout Buddy may offer an optional auto-renewing subscription. All payments are handled by Apple — we never see or store your card or billing details.
- We use RevenueCat to tell us whether your subscription is active so we can unlock premium features. RevenueCat receives an anonymous identifier tied to your account and your purchase / renewal status, not your payment information.
Apple Health (iPhone and Apple Watch, opt-in)
- If you turn on “Sync with Apple Health” on the Profile screen, the app reads your bodyweight samples (
HKQuantityTypeIdentifierBodyMass) from the Health app and merges them into your bodyweight log. The most recent sample for each day is kept. - HealthKit-sourced entries are uploaded to your account in Supabase the same way manually-typed entries are, so your weight log stays in sync across your iOS devices.
- The app also reads your step count (
HKQuantityTypeIdentifierStepCount) to show your daily steps on the Profile screen and to tell you when you hit your step goal. Your step counts stay on your device — they are never uploaded to our database and never sent to Buddy or any other third party. (The step goal you set is a preference, and that number is saved to your account so it follows you across devices.) - The home-screen step widget does not use Apple Health. It counts your steps itself with Apple’s motion coprocessor (Core Motion), so the number on your home screen stays current even when the app is closed. That count never leaves your iPhone.
- On your Apple Watch. The Watch app reads four values to fill in its activity screen: step count, active energy (
HKQuantityTypeIdentifierActiveEnergyBurned), exercise minutes (HKQuantityTypeIdentifierAppleExerciseTime), and walking / running distance (HKQuantityTypeIdentifierDistanceWalkingRunning). All four are displayed on your wrist and never leave your Watch. - During a workout your Apple Watch tracks, the Watch app runs a real Apple workout session and reads your heart rate (
HKQuantityTypeIdentifierHeartRate) and active energy (HKQuantityTypeIdentifierActiveEnergyBurned) live so it can show them while you train. When that workout ends, three summary numbers — your average heart rate, your highest heart rate, and the active calories for that one workout — are sent to your iPhone and saved to your account with the workout, so they appear in your history on every device you sign in on. Individual heart-rate readings are never uploaded; only those three summaries are. - What we write. When you finish a workout that no Apple Watch tracked, the iPhone app writes that workout to Apple Health as a strength-training session, so it counts toward your Activity rings and appears in the Fitness app. For those, we write only the start time, the end time, and an internal id used to avoid saving the same workout twice — no heart rate, no calorie estimate, and nothing you did not log in the app. When your Apple Watch does track the workout, the Watch saves it to Apple Health itself using Apple’s standard workout builder, which stores the workout together with the heart-rate and active-energy samples your Watch measured during it. That is Apple’s normal behaviour for any Watch workout.
- Optional nutrition writes. When nutrition is available and you grant permission, the app can also save the protein you log as dietary protein (
HKQuantityTypeIdentifierDietaryProtein) and any positive calorie amount you enter as dietary energy consumed (HKQuantityTypeIdentifierDietaryEnergyConsumed). A named food staple can group those samples in a food correlation (HKCorrelationTypeIdentifierFood) with its food name. The app requests write permission for these nutrition types, not read permission. Editing or deleting a linked entry attempts to replace or remove the samples the app created; failures do not prevent local logging. - The complete list. The Health data types we read are: bodyweight, step count, heart rate, active energy, exercise minutes, walking / running distance, and workouts. We write strength-training workouts (including the Watch samples described above) and, with nutrition permission, dietary protein, dietary energy consumed, and food correlations. We request no other Health access.
- You can revoke access at any time in Settings → Privacy & Security → Health → Workout Buddy, on your iPhone and on your Apple Watch separately. Already-imported entries stay in your log unless you delete your account.
- Deleting your Workout Buddy account does not delete records already saved in Apple Health. You can manage those records in the Health app.
Diagnostics (Sentry)
- Crash reports and unhandled errors, including stack trace, device model, OS version, and app version
- A small sample of performance traces (20% in production)
- Your account ID and email are attached to crash reports so we can debug your specific issue
- Screenshots are not captured
Product analytics (PostHog)
- App lifecycle events (open, background, etc.) and a small set of in-app events used to improve the product
- Your account ID and email are attached so we can answer questions like “did this user hit the bug we fixed?”
- Nutrition, bodyweight, and step features send interaction events such as opening a card or using a logging control. The analytics boundary removes nutrition amounts, bodyweight, step counts and goals, workout counts, adherence values, food names, and workout or staple identifiers from these events.
- Hosted on PostHog Cloud (United States)
Stored only on your device
- Cached workouts, programs, and preferences (so the app works offline)
- Authentication tokens needed to keep you signed in
What we do not collect
- Location (precise or coarse)
- Your camera, microphone, or contacts (we only read a photo you explicitly pick for your profile picture — see above)
- Google Fit data
- Apple Health data outside the reads and writes described under Apple Health above; access requires your permission
- Browsing or search history outside the app
- Advertising identifiers (IDFA / GAID)
- Your payment card or billing details — Apple processes all purchases and we never receive them
How we use it
- Run the app: sign you in, sync your workouts across devices, render your history.
- Fix bugs: crash and error reports help us reproduce issues you hit.
- Improve the product: anonymous-ish usage patterns help us see which features are used.
We do not use your data for advertising, do not share it with data brokers, and do not link it with data from other companies’ apps or websites for tracking purposes.
Who we share it with
Data is processed by these service providers on our behalf:
| Provider | Purpose | Where |
|---|---|---|
| Supabase | Authentication, database, file storage | United States |
| Anthropic | Buddy AI coach (processes your chats) | United States |
| RevenueCat | Subscription status (if you subscribe) | United States |
| Sentry | Crash reporting | United States |
| PostHog | Product analytics | United States |
| Apple | Sign in with Apple; subscription billing; optional Apple Health integration | Per Apple’s policy |
| Sign in with Google (if used) | Per Google’s policy |
That’s the full list. We do not share data with anyone else.
How long we keep it
- Account & workout data: kept until you delete your account.
- Buddy chats: kept on your device, not stored on our servers; the per-month usage count resets each month.
- Crash reports: retained by Sentry per their default retention (typically 90 days).
- Analytics events: retained by PostHog per their default retention.
How to delete your data
Open the app → Profile → Delete Account, type DELETE to confirm. This:
- Deletes your Supabase user, which cascades and removes your profile, programs, sessions, sets, custom exercises, personal records, and bodyweight log in a single transaction.
- Deletes your profile photo from our storage in that same transaction.
- Signs you out on the device and wipes the app’s local copy of your data.
If you can’t access the app for any reason, email support@work-out-buddy.com from the address on your account and we will delete it manually.
To purge analytics or crash records tied to your old account, mention that in the email and we’ll forward a deletion request to Sentry / PostHog.
Children
You must be at least 13 years old to use Workout Buddy or create an account. The app is not directed at children under 13, we do not knowingly collect data from them, and we will delete any such account and its data as soon as we learn of it. If you believe a child under 13 has created an account, email support@work-out-buddy.com and we’ll remove it.
Workout Buddy is designed for adults. If you are between 13 and 17, use it only with a parent or guardian’s permission and after a physician has cleared you for the kind of training the app prescribes — see our Health & Safety Disclaimer.
Your rights
Depending on where you live (e.g., GDPR in the EU, CCPA in California), you may have the right to access, correct, export, or delete the data we hold about you. The in-app delete flow handles deletion. For access or export, email support@work-out-buddy.com and we’ll respond within 30 days.
Security
- All traffic between the app and our backend uses HTTPS / TLS.
- Supabase enforces row-level security so one account can never read or modify another account’s data.
- Authentication tokens are kept in the app’s own sandboxed on-device storage, protected by your device’s OS-level encryption. Other apps cannot read them.
No system is perfectly secure. If you discover a vulnerability, please report it to support@work-out-buddy.com before disclosing it publicly.
Changes to this policy
If this policy changes, we will update the “Last updated” date at the top and, for material changes, prompt you in the app on next launch.
Contact: questions, deletion requests, or privacy concerns — support@work-out-buddy.com.