Privacy Policy
FitBoost is a workout log app. This policy explains what information the app handles and where that information is kept.
Summary
- You can use the app without an account. We never ask you to sign up.
- Your workout and body records are stored on your device. If you turn on sync across devices, they are also stored in your own iCloud or Google Drive, where we cannot see them.
- The standard setup has no server. Only public courses, Garmin Connect linking and peer comparison, when you turn them on yourself, go through our servers; no other records are sent to our servers.
- We do not collect your name, email address or phone number.
- We collect usage statistics to see how the app is used. The contents of your workout records and advertising identifiers are not sent.
- While you use the app for free, Google AdMob ads appear, and the advertising identifier and device information may be sent to Google for them. Subscribing to PRO removes ads.
- Peer comparison sends anonymous summary values (age range, sex, bodyweight range, best estimated one-rep max per exercise) only if you turn it on.
- Run location is used only while a run is being measured, stays on your device and in your health app, and is never sent to our servers. Sending and receiving courses doesn't go through a server either.
- If you turn on Garmin Connect linking, runs measured on your Garmin watch and your sleep and heart rate records come to the app through our server (Supabase, Seoul). They stay on the server only until your device downloads them (30 days at most), and we never sell them or use them for ads or AI training.
Information the app handles
Workout and body records
This covers workout sessions, sets, weights, reps, routines, schedules, notes, body weight and body composition, and progress photos. This information is written only to your device's storage, and the app does not send it anywhere.
If you have device backup turned on, this information may be included in your iCloud Backup or Google automatic backup. Apple and Google handle those backups under their own policies, and we have no access to them.
Sync across devices (optional)
If you turn on sync across devices in settings, a copy of your records is kept in your own storage so that your devices signed in to the same account stay in step.
- iPhone and iPad: your iCloud private database (CloudKit)
- Android: a hidden, app-only folder in your Google Drive. When you turn it on, we ask only for access to that folder in your Google account.
Apple and Google keep this copy under their own policies. It does not pass through our servers, and we have no access to it. Photo and video files and your subscription status are not transferred. Sync is off by default. The on-device backup copy of your runs (time series such as route and heart rate) is not synced.
Send to trainer (optional)
The app creates a report (PDF) and a client file from the records in a period you choose, and sends them through an app you pick (a messenger, email and so on). The files go only to the person you send them to and do not pass through our servers. The receiving app stores those records only on the recipient's device.
Backup file (optional)
When you create a backup file in Transfer & backup in the menu, the app puts your workouts, routines, schedules, body records, photos and settings into a single file (.fitboost) and hands it to the place you pick (the Files app, a messenger, email and so on). The file also records when it was made, the app version and the device type (iOS or Android). It does not pass through our servers, and if you set a password it cannot be opened without that password. Your subscription status, health app connections and notification permission are not included. The on-device backup copy of your runs is included too. Copies for deleted records are left out.
Health data (optional)
Only if you allow it, the app exchanges workout records with Apple Health or Health Connect. If you decline, or turn it off later, the rest of the app keeps working as before. Health data never leaves your device. When you measure a run, time series such as the route (location, elevation and accuracy), distance and heart rate are written to the health app with that workout.
Run location and motion sensors (optional)
The app asks for location only when you measure an outdoor run with your phone. Location is used to record your route, distance and pace and to guide you along a course, and is received only from the start of a run until you finish it. So that measuring continues until that run ends even with the screen off or another app open, iPhone uses the background location mode and Android uses a location foreground service with an ongoing notification. The app does not ask for Always (background location) permission. Without location, you can still record time only or run indoors.
The motion sensors and barometer are used to measure steps, cadence and elevation. On Android, the physical activity permission is requested to read the step sensor.
If you allow it, measured time series such as your route and heart rate are written to the health app (Apple Health or Health Connect), and a backup copy is kept on the device for values the health app has no place for and to keep precision. This copy goes only into backup files and is not uploaded to iCloud or Google Drive by sync across devices. If you don't allow the health app, the same data is kept only in this copy. Your workout records keep a summary such as distance, time and average pace. Location and routes are never sent to our servers or to third parties.
If you choose to export a file from a run result, the route, times and elevation are put into a single GPX file and handed to the app you pick. Here, and when you send a course made from a route you ran, the areas around the start and finish (200 m by default plus a random 0–200 m) and your privacy zones are cut. Records and result maps on your own device are not cut. If you import an activity file (GPX or TCX) exported from another app or watch, the file you pick is read only on your device to create a run record and is not sent to our servers.
In builds that use maps, the map images for the area shown on screen are fetched from Google Maps to draw the base map, and that request reaches Google. Builds without maps draw only the route line, with no base map.
Sending and receiving courses (optional)
When you send a course by link, QR code or file, the course name and route line, plus the time at every 100 m if you choose, go to the app you pick. Nothing passes through our servers. Courses that come from a route someone ran, such as courses detected from repeated routes, made from a past run or a file, or received from others, are sent by link, QR code or file alike with a random length cut from around the start and finish and with your privacy zones removed, and an included record is counted again from the start of the trimmed line. Only courses you drew are sent as drawn. Dates, clock times, heart rate and device information are not included.
A course link (bbdyno.github.io/FitBoost-Site/course.html) carries the course after the # in the address. Browsers don't send the part after # to the server, so even though opening the page sends a request to GitHub Pages like any web page, the course itself is not in it. The course page decodes it only inside your browser and uses no usage statistics or ad scripts. A received course is saved only on the receiver's device, when they save it.
Public courses (optional)
Public courses open on November 2, 2026. Before then the feature was turned off, so no course was sent to a server.
If you choose "Share publicly" for a course, its line (with 400–600 m cut off near the start and finish), its name, its surface and terrain tags, and a hash of a random device secret used only for this feature are stored on Supabase servers in Seoul, and the line, name and tags are shown to all users. Other users can't see who posted it. Times, speed, heart rate, names and contact details are not sent. Public courses are deleted after 12 months and can be taken down in the app at any time; records of sharing and taking down are kept for 12 months. When you look for public courses, only an area of about 15 km around the place you chose is sent, and the server doesn't record it. See the Location-Based Service Terms for details.
Garmin Connect linking (optional)
The app exchanges records with Garmin Connect only if you choose "Link Garmin Connect" in Settings, sign in with your Garmin account and agree to share. Only the items you turn on in Garmin's consent screen are exchanged, and you can turn each one off in your Garmin Connect account settings. This feature is available from FitBoost 1.9.1.
What we receive from Garmin: runs measured on a Garmin device (start time, distance, duration, speed and pace, heart rate, cadence, power, elevation, the locations along the route you ran, and the device name), and, from the daily health summaries, sleep duration and sleep stages, overnight heart rate variability and resting heart rate. Received records are used for run records, statistics, the coach, share cards and recovery assessment.
What we send to Garmin: courses (name, route line, elevation, distance) and workouts (the steps, targets, and sets, reps and weights of a run prescription or strength routine) that you choose to "Send to Garmin". Courses and workouts you send are saved to your Garmin Connect account and moved to your watch, and from then on the Garmin Connect Privacy Policy applies. Before sending, the app explains this and asks for your consent.
What we keep on our server: Garmin sends records only to our server. The server is in the Seoul (South Korea) region and is operated by Supabase, Inc. (United States). It keeps only the following.
- Your Garmin user ID, the access and refresh tokens issued by Garmin, a hash of a random device secret used only for this feature, and the sharing items you turned on at Garmin
- Runs and health summaries your device hasn't downloaded yet. They are deleted as soon as your device downloads them, and after 30 days even if it doesn't.
Courses and workouts sent to Garmin are not stored on the server; they are only passed on to Garmin. Records downloaded to your device are stored on your device like your other workout records and follow the same rules for the health app, sync across devices and backup files.
We do not sell records received from Garmin or provide them to other companies. They are not sent to ads (AdMob) or usage statistics (Firebase), and they are not processed with AI or used for AI training. When the app shows records received from Garmin, it shows Garmin as their source.
Unlinking: When you tap "Unlink" in the app's settings, the server removes FitBoost's registration with Garmin and immediately deletes the connection information and any records not yet downloaded. If you disconnect FitBoost in your Garmin Connect account, the connection information and records not yet downloaded are deleted right away; if you turn off one sharing item, the records for that item not yet downloaded are deleted right away. Records already on your device can be viewed, edited and deleted in the app, and exported to a backup file.
Photos and camera (optional)
The app accesses your photo library or camera only when you add a progress photo or pick a background photo or photo sticker for a share card. The photos you choose are stored on your device, and we do not view them. When you save a design to Photos, iPhone uses add-only access and does not read your library, and Android puts it in a FitBoost album (Android 9 and earlier use storage write permission).
Photo adjustments in share cards and the editor (grayscale, blur, brightness, contrast and so on) and putting stickers behind people (cutting out the person in a photo so stickers go behind them) are processed only on your device. iPhone uses Apple's Vision feature built into the device, and Android uses the Google ML Kit person segmentation model included in the app. Photos and cutout results are not sent to our servers or to Google. On Android, ML Kit may send performance and usage metrics for this feature to Google, without the photo.
Share card images you make go only where you choose (an Instagram story, a messenger, your photo library and so on), and from there the receiving service's policies apply. Routes on run cards are drawn only from the line with the start and finish areas and your privacy zones cut out, with no base map, coordinates or clock time. Saved editor templates (my templates) stay on your device and in backup files and are not uploaded by sync across devices.
Movement assessment (optional)
The camera is used only when you run a movement assessment (mobility and fitness tests, jumps, bar speed, running form). Video and body joint positions are analyzed only on your device and are never sent to our servers or to Google. iPhone uses Apple's on-device Vision framework, and Android uses the Google ML Kit pose detection model bundled with the app. On Android, ML Kit may send performance and usage metrics for this feature to Google, without any video. No audio is recorded.
Measured values (reps, angles, times, heights, speeds and so on) and their interpretation are stored on your device like your other workout records, and are included in backup files and sync between your devices only if you turn those on. Measurement videos (when "Keep a video of the test" is on) and scene photos with faces blurred stay on this device only and are excluded from iCloud and Google backups, backup files and device sync. You can delete them at any time from the result or storage screen.
When a trainer measures a member, photos and videos are kept only with the member's consent, and age and sex are used only to choose reference values. Member report documents go only where the trainer chooses to send them.
Notifications (optional)
Rest timer and workout schedule notifications are generated directly on your device. We do not use a push server.
App settings and update notices
The app receives settings from Google's Firebase Remote Config that turn ads on or off, change how often and where they appear, and set which versions are asked to update. For this, the Firebase installation ID (a random identifier created each time the app is installed), the app version, the device type, and the language and time zone are sent to Google.
To check whether a new version is available, the app asks Google Play on Android, and Apple's app lookup (itunes.apple.com) on iPhone, for the latest version of this app. Your workout records and personal information are not sent.
Usage statistics
To understand which features are used and to improve the app, we collect usage statistics with Google's Firebase Analytics. We collect the following.
- App usage events: app launches, screen views, workout start and completion, exercise selection, use of weight recommendations, opening the purchase screen and subscription purchases, switching training mode, starting and finishing a run, setting a reference result, saving a course, opening the share screen, and in the share editor: opening it, choosing a layout, removing a sticker and exporting
- Values and categories attached to events: the number of exercises in a workout, workout duration (minutes), total number of workouts, the catalog number of the selected exercise, and the subscription product and plan type, the chosen training mode, the kind of run, the measuring device (phone or watch), whether the run followed a course, whether location was recorded, how the reference result was set, how the course was made, where sharing was opened, how the editor was entered, which layout was chosen, where it was exported (Instagram, Photos and so on), whether a photo was used (the photo itself is never sent), and the image size
- Device and app information: country, device type, operating system and app version
- App instance ID: a random identifier created anew each time the app is installed
We do not collect the following.
- The contents of your records, such as weights, reps, notes, body weight and body composition, and photos
- Your profile, such as nickname, height and body weight
- Advertising identifiers (IDFA, AAID) and the iOS identifier for vendors (IDFV)
- Run distance, time, pace and heart rate, location and routes, and course lines and names
Usage statistics are not linked to your name or contact details, and are not used to track you across other apps or websites. The statistics are processed on Google's servers.
Peer comparison (optional)
Only if you turn on "Compare with peers" in the app, FitBoost collects the following anonymously when you finish a workout: a random device number used only for this feature, your age range (5-year bands), sex, bodyweight range (5 kg bands), and your best estimated one-rep max over the last 90 days for each exercise. We do not collect your name, account, email, exact age or bodyweight, dated workout history, photos or location. The feature is off by default.
This information is used only to build distributions for people of the same age range, sex and bodyweight range, and a distribution is published only for groups of 50 or more people. Your rank is calculated on your device.
We keep only the latest values per device. They are deleted immediately when you tap "Delete sent data" in the app, and automatically after one year without new data; deleted values leave the distribution from the next daily update.
The server runs on Cloudflare, Inc. (United States) Workers, D1 and R2, and data is sent over encrypted connections (HTTPS). You can decline by leaving the feature off, or turn it off and delete your data at any time; only peer comparison is then unavailable.
Third-party services
| Service | Purpose | Information handled |
|---|---|---|
| Google AdMob | Showing ads to free users | Advertising identifier, device and app information, approximate location |
| Google Firebase Analytics | Usage statistics | App usage events, app instance ID, country, device and app version |
| Google Firebase Remote Config | Receiving settings for ads and update notices | Firebase installation ID, app version, device type, language and time zone |
| Apple App Store | Subscription payments and receipt verification | Transaction information (handled by Apple) |
| Google Play | Subscription payments and receipt verification | Transaction information (handled by Google) |
| Google ML Kit (Android) | Person segmentation for share card editing and pose detection for movement assessment (on device) | No photos or videos sent; feature performance and usage metrics |
| Supabase (Seoul region server) | Server for public courses and Garmin Connect linking | Public course lines, names and tags; Garmin user ID and tokens; hash of the device secret; Garmin records not yet downloaded |
| Garmin Connect | Receiving Garmin records; sending courses and workouts to Garmin | Garmin activities and health summaries; courses and workouts you send |
Ads
While you use FitBoost for free, ads from Google AdMob appear: banners and other ads on many screens, including the workout screen and the rest timer; ads mixed into lists; full-screen ads at natural breaks such as after you finish a workout; ads when you open the app; and rewarded ads that you choose to watch. We do not show full-screen ads in the middle of a workout, and we do not show ads on payment screens.
To show ads and measure their performance, the advertising identifier, device and app information, and an approximate location estimated from your IP address are sent to Google. Your workout and body records are not used for ads. On iPhone, the app does not ask for tracking permission and does not read the advertising identifier (IDFA); you see non-personalized ads. On Android, the advertising identifier (AAID) is sent to Google, and the app currently shows non-personalized ads. If we switch to personalized ads, we will update this document first. In the European Economic Area and the UK, you can give or change your ad consent in the consent dialog shown the first time in the app and in Ad privacy settings in the menu.
Subscribing to PRO or PRO+ removes all ads.
- Google advertising policy: policies.google.com/technologies/ads
- Android: Settings → Google → Ads
Payments
Subscription payments are processed through your Apple or Google account. We neither receive nor store your card number or any other payment method details.
If a server is connected
The only features that use our servers now are public courses, Garmin Connect linking and peer comparison, when you turn them on yourself; the information each one sends is described above. Features such as social features, live trainer connections and an AI coach are not in the current release. If we offer them in the future, we will update this policy to describe what information is sent to the server, explain it in the app in advance, and ask for your consent.
Retention and deletion
Your records are kept for as long as they remain on your device. When you delete the app, the data it created is deleted with it. You can delete individual records in the app at any time.
When you delete a run, its on-device backup copy is deleted too. You can view and delete routes and heart rate written to the health app in the health app.
Copies included in device backups must be managed in Apple's or Google's backup settings.
Turning off sync across devices does not delete the copies left in iCloud and Google Drive. You can delete FitBoost's hidden data on iPhone in Settings → [your name] → iCloud → Manage Storage, and on Android under Manage apps in Google Drive settings.
Records kept on the server for Garmin Connect linking are deleted as soon as your device downloads them, and after 30 days even if it doesn't. When you unlink, the connection information and any remaining records are deleted right away.
Usage statistics are deleted after a set period according to Google Analytics retention settings. When you delete the app, its app instance ID is no longer used, and a new ID is created if you reinstall.
Children
FitBoost is not directed at children under 14, and we do not knowingly collect personal information from children.
Your rights
Because your workout and body records are on your device, you can view, correct and delete them yourself in the app. In Transfer & backup in the menu, you can put all of your records into a single backup file to keep wherever you like or move to another device. The same applies to records received from Garmin.
You can withdraw Garmin Connect linking at any time with "Unlink" in the app's settings or in your Garmin Connect account settings. The connection information and records not yet downloaded are then deleted from the server.
Changes
If this policy changes, we will update this page and its last-updated date.
Contact
Please send any privacy questions to della.kimko@gmail.com.