Training Logz
Training Logz helps you track workouts, body weight, strength ratios, and outdoor runs from your phone.
Email support@traininglogz.com. Questions, bug reports and privacy requests all go to the same address.
If something is not working as expected, include your device model, operating system version, and a short description of what happened.
Workout logs, body-weight entries, run summaries, route information and daily step counts are stored locally on your device. Logging workouts does not require an account, and logging a workout sends nothing to us.
Your app color, the “Tint the whole app” switch and, on iPhone, the App Icon that follows the color are kept on your phone, and Training Logz never sends them to us or to any other service; iOS changes the icon on the phone, to one of the icons built into the app. The color does show in what you choose to share: a flyover video draws the part of the route already flown, and the dot that marks the runner, in your color; and while “Tint the whole app” is on, a run card, a splits image, a flyover video and a hybrid card are drawn partly in shades of it.
The optional leaderboard, feed, cloud backup and coach, the barcode lookup, and the air quality and weather lookup, are the only features that send your data to us or to another service. All of them are off until you use them, and each is described below. Sharing a run, your hybrid card, your personal heatmap or your year in review is different: nothing leaves your phone until you choose where it goes, as described under Sharing. So is an export of your data, as described under Data Control. Separately, any map in the app, including the Run tab and a run being recorded, loads map images for the area on screen from Apple Maps on iPhone or Google Maps on Android. Those requests show the area being viewed, which follows you while you record a run, but carry no account or run details.
Our server records the network (IP) address each request comes from, including simply opening the leaderboard, so it can limit how often one address calls it. These records are not linked to your account and are not used for anything else; the server deletes them some time after they are ten minutes old.
Location is used while you are recording an outdoor run. That includes while your screen is off or you are in another app, because a run you cannot track to the end is not much use — your phone shows a location indicator the whole time, and recording stops the moment you save or discard the run. With the app open, it is also used when you ask for it: to center a map on where you are when you tap the center-on-me button or design a route, to open the Run tab's map where you are if you have already allowed location, and to mark which of your past runs pass near where you are when you pick one to race. It is never used in the background for anything but a run you are recording.
Health data access is optional and asked for separately. On iPhone, Training Logz reads workouts, routes, sleep, heart rate and daily step counts from Apple Health, as well as the steps taken during each run or walk once you have allowed step access, and never writes to it. The Apple Watch app reads heart rate, active energy and distance while it records a workout, and saves that workout to Apple Health. On Android, it reads exercise, distance, route, sleep and heart-rate records from Health Connect, and writes nothing back. Once heart rate has been allowed, the app also reads the heart rate Apple Health or Health Connect holds for each run's own stretch of time, without asking again: when the run is opened, when it is imported, and when the app comes back to the front within a day of a run recorded on the phone. Those readings are kept on the phone beside the run, one value every ten seconds, and are never put in cloud backup, a leaderboard time, a feed post, what the coach receives, a splits image or a recorded flyover video. A run card shows the run's average and maximum heart rate only if you add them to a card style of your own.
Training Logz does not sell personal information and does not use advertising trackers. Health and fitness data is never used for advertising, marketing, or data mining, and is never shared with third parties for those purposes.
A run's screen can show the weather, the humidity and the air quality while it was run.
Air quality and weather is off until you turn it on in App settings, or tap Turn on where a run offers to look up its air quality. While it is on, for each run with a route, the app sends our server one place, the middle of the route rounded to a grid about 5 km across, and the hours the run began and ended, rounded out to whole hours and never later than the moment it asks. Nothing else about the run or about you goes with them: not the route, its name, distance, time or heart rate, and no account. Our server asks OpenWeather about that place and those hours, so OpenWeather never receives your network address, and passes back the air quality and, for a run that has just ended, the weather. Our server keeps no record of who asked about which place or hours: it may hold OpenWeather's answer for that grid square and those hours for up to a day, and, as for every request it receives, it records the network address a request comes from, not linked to your account, only to limit how often one address can ask, and deletes that record some time after it is ten minutes old. The answer is kept on your phone with the run and goes in an export of your data, but never in cloud backup, a feed post, a leaderboard time or what the coach receives; a run card or flyover video in a style of your own shows it if you add it. The weather an Apple Watch records with an outdoor workout is read from Apple Health on your phone and needs none of this.
The air quality, and any weather the watch did not record, come from OpenWeather, whose credit the app shows beside them: under the run's figures, and on a run card or flyover video that shows any of them.
The leaderboard is optional and off by default. Turning it on is a separate choice from granting health access, and asks you to sign in with Apple or Google so your entry survives reinstalling the app.
While it is on, Training Logz uploads one entry per distance, with the display name you choose: the distance and your finish time, when the run was recorded and the calendar day it was on, which app or device recorded it, whether it was entered by hand, and the run's results; when it was recorded stays with the entry and is shown to nobody, and its day and its app are shown to others only while your switch to show them is on. Your chosen display name, your finish time and whether it was entered by hand are visible to everyone using the app. The day of the run and which app or device recorded it are shown to others only while you have “Show when I ran and which app recorded it” switched on for your entry: the day as a date, never a time of day, and the app only as a name from a fixed list (Apple Watch or Strava, for example) or as “another app”. The switch applies to the run your entry stands on, and tapping it changes your entry straight away. With it off, as it is unless you turn it on, both are kept with the entry and never sent to anyone else. Entries posted before this switch existed stay private unless their runner turns it on.
A posted time also carries its run's results, the way a feed post of that run would, but without its map or its hills. What others see of a posted time: your display name, the distance and your finish time, and whether it was entered by hand, which everyone sees; the run's moving time and pace, its pace along the run and how much of it was faster or slower than its own average, the pace of each mile and its fastest times over set distances, which anyone signed in can open unless one of you has blocked the other on the feed; and, only while your switch to show when you ran and which app recorded it is on, the calendar day of the run and which app or device recorded it -- never a time of day, the route, a map of it, its hills or your heart rate. Tapping a time opens its results for anyone signed in, unless one of you has blocked the other on the feed. A time posted before this carries none of them until its runner posts that run, or a faster one, again.
Nothing else is uploaded to the leaderboard. Your GPS routes, maps, heart rate, body weight, strength logs and other workouts are not part of an entry. The AI coach is separate and off by default; if you turn it on, it is sent a summary, and Coach below sets out exactly what that includes. Training Logz stores a one-way hash of the account identifier Apple or Google provides, and the display name you pick; it does not store your email address and never receives your password.
Leaderboard entries are held on Cloudflare infrastructure and encrypted in transit and at rest.
Display names are public, so keep personal details out of them. Training Logz may remove a name that is misleading or abusive.
Cloud backup is optional and off by default. It requires you to sign in with Apple or Google. When you turn it on and choose Back up now, Training Logz uploads a private copy of your saved runs and your workouts, and from an iPhone your daily step counts, so you can restore them after losing a phone or reinstalling the app.
A backed-up run may include its title, date, source, duration, distance, pace, notes, and GPS route points. If you previously imported that run from Apple Health or Health Connect, the saved run may contain fitness information derived from that source. Training Logz backs up the run stored in the app, not the complete underlying Apple Health or Health Connect record.
A run backed up from an iPhone also includes the number of steps taken during it, when Apple Health had a count for it. A run restored to an Android phone keeps that number, and it goes up again with the run; the Android app never reads steps itself.
A backed-up workout includes its date, the exercise names, and the sets you logged with their weights, reps and times. Exercise names and workout titles are yours to edit, so if you have renamed any of them the backup stores the names you chose.
From an iPhone, a backup also includes your daily step counts: the date and the number of steps for each day the app has imported from Apple Health — nothing about when in the day they were taken or which device counted them. The Android app does not read steps, and does not back up or restore daily step counts.
Your nutrition, sleep, body weight and the notes you write are not part of cloud backup. They stay on the device.
Backups are linked to that one-way hash of the account identifier supplied by Apple or Google, stored privately on Cloudflare infrastructure, and are not visible to other users. Cloudflare processes this data only to host the Training Logz service. Backup data is not used for advertising, marketing, profiling, or data brokerage.
Turning cloud backup off deletes your backed-up runs, workouts and step counts from the server. If deletion cannot be confirmed, the app keeps the setting on and tells you that deletion failed. Deleting your Training Logz account also deletes its cloud backup.
The coach is optional and off by default. If you turn it on, Training Logz sends a derived training summary to a coach service so it can return workout advice. With each question it sends the following, worded exactly as the Coach tab shows it:
If you read kilograms or kilometers, or the app is in Spanish, the instructions sent with each question tell the coach to answer that way; the numbers in the summary itself are not converted.
Raw Health records never leave your device. GPS routes, maps, the heart-rate readings your watch records, exact Health Connect or Apple Health records, account identifiers, email address, display name and any note you write are not sent to the coach. Heart rate reaches the coach only as the zone minutes, the maximum and the resting average described above — never the readings themselves and never when they were taken. The notes you attach to exercises in your plan are not sent either.
Your conversations with the coach stay on your phone, one each for the training coach, the nutrition guide and the recovery coach, until you clear them on the Coach tab; only the last few messages of the one you are in go with a question, and they are never sent to us or put in cloud backup.
The first version of the coach is advice-only. It cannot create a workout plan, change a saved plan, log a session, delete a session, or write data to Apple Health or Health Connect.
The coach runs on an AI provider you choose, using an API key you supply. Your key is stored in your device's secure keystore and is never sent to us. Requests go directly from your phone to that provider; they do not pass through our servers, and we do not receive, log or store any part of them.
On an iPhone or iPad that supports Apple Intelligence, you can choose Apple Intelligence instead, with no key: the coach then runs on the device itself, and the summary, your questions and its answers never leave it.
If you photograph a meal, or choose a photo of one, that image is sent to the same AI provider on the same key so it can estimate the nutrition. The photo goes straight from your phone to that provider. Training Logz does not keep a copy, does not upload it to our server, and does not have access to it.
The app asks for camera access only for this and for scanning barcodes, and only when you use them. It never opens the camera or reads your photo library on its own.
Once your photo reaches the provider you chose, it is handled under their privacy policy rather than ours. If that matters to you, read the policy of the provider whose key you are using before sending it a photograph of anything.
Scanning the barcode on a packet looks that number up in Open Food Facts, a public food database. The barcode is the only thing sent. It carries nothing about you — no account, no device identifier, no location — and the request is not tied to your Training Logz account in any way.
No photograph is sent or stored. The camera reads the number on your phone and only the number leaves it. This needs no AI key and no payment.
The feed is optional and you have to be signed in to see it. Nothing about your training appears there unless you post it.
A post contains a title and a color you picked from fixed lists, the date and the time of day it finished, when you posted it, and either a run's distance, time, moving time and pace, its pace along the run and how much of it was faster or slower than its own average, the pace of each mile and its fastest times over set distances, or how many sets you did of each exercise, without the exercises' names; and, only for a run and only when you switch it on for that post, a map of the middle of the route with everything within 500 meters of the start and of the finish left out, together with that stretch's climb, descent, grade-adjusted pace and the height along it. The app draws the paces and the sets as a picture on the post. Your display name is shown beside it. There is no comment box and no free text on a post — the only writing anywhere in the feed is the display name you choose. Posts made on or before 15 September 2026 may still hold a workout's focus, or a run's own title and the app or device that recorded it, on our server. Nobody else sees it; a moderator reviewing a report on one of those posts can.
A post never contains your exercise names, the weights you lifted, or where a run started or finished. Your recorded route is removed before a post leaves your phone and again on our server. If you switch on the map for one post, what goes instead is a simplified line of the middle of that run: everything within 500 meters of where it started and where it finished is left out on your phone before anything is sent, and that part is never in a post. The run's climb, descent, grade-adjusted pace and the height along it are told only for the part the map shows, because a height profile can give a route away too.
Cheers — which posts you liked — are stored so the count is right and so you can take one back. Reports and blocks are stored so we can act on them and so a block keeps working; neither is ever shown to anyone else, and a person you block is not told.
Reports are reviewed within 24 hours. Blocking is immediate and works in both directions. What is and is not allowed on the feed is set out in the Terms of Service.
Deleting a post removes it for everyone. Deleting your account removes your posts, your cheers, your reports and your blocks along with everything else.
You can share three things about a run, each made on your phone from the run's own screen:
Each one goes only where you send it. A run card can go to your share sheet, your photos or Instagram Stories. Splits can go to your share sheet or your photos. A flyover video goes to your share sheet, and from there anywhere it offers, your photos included. Training Logz never uploads any of them to our server.
From Progress you can also share a hybrid card: an image with the week it is for, your best mile, 5 km and 10 km times, this week's running distance and your weekly distance goal if you set one, up to four lifts you choose, by name, each as a multiple of your body weight if you have weighed in recently, and how this week split between lifting and running, counted in sessions and runs or in time. It never shows your body weight or the weight you lifted. Its times and this week's workouts can include runs and workouts imported from Apple Health or Health Connect. It goes only to your share sheet or your photos, and Training Logz never uploads it to our server.
With Training Logz Pro you can also share your personal heatmap from the Run tab: an image of the routes of the runs it shows, over the map or satellite view as you framed it (Apple's on iPhone, Google's on Android), with a band under it naming the time range and the kind of activity you chose. Unless you switch off "Hide where my runs start and finish", it leaves out every part of a route within 300 m of where any run on it started or finished, and more round those places, off-center by a random amount your phone keeps, so the middle of a gap is not where you set off. With "Show the numbers" on, it also shows how many activities the heatmap has, their total distance and how much different ground they cover. It never shows a run's date, name, time or pace. The heatmap is worked out on your phone, and the image goes only to your share sheet; Training Logz never uploads it to our server.
With Training Logz Pro you can also share your year in review from Progress: one of its cards as an image, or, on iPhone, a recording of the story playing. Depending on the card, it shows the year and, for that year, how many runs you did, their distance and time, how many workouts you logged and days you trained; your longest run, its distance and date, and a drawing of its route; your fastest mile, 5 km, 10 km and half marathon times, with their dates and whether each is your best ever; how far you ran, how many times you ran or how often you trained in each month, the day of the week and the time of day you ran or trained most, and your longest run of weeks that met your weekly target; the year's heatmap, its lines alone with no map under them, with how many runs it shows, their distance and how much different ground they cover; your lifting sessions, the volume you lifted, your heaviest set and its exercise, the exercise you trained most, by name, and in how many sessions, and how many personal records you set; and your hottest and coldest runs and the run with the cleanest air, with their temperature or air quality and their dates. The heatmap leaves out every part of a route within 300 m of where any run on it started or finished, and the route drawing every part within 300 m of where any of the year's routes started or finished; both leave out more round those places, off-center by the same random amount your phone keeps for your heatmap. A recording on iPhone also shows a few seconds of a 3D flyover over Apple's satellite map along part of one of your longest runs with a route, with that run's distance and date, never within 300 m of where any of the year's routes started or finished. It never shows your heart rate, your body weight, a run's name or the time a run began. Its numbers can include runs imported from Apple Health or Health Connect and workouts imported from Strong or Hevy. Your year in review is worked out on your phone, and a card or recording goes only to your share sheet; Training Logz never uploads it to our server.
You can change or revoke location and health permissions at any time in your phone settings. Logging a workout by hand does not depend on either of them.
In App settings, under Your data, you can export everything the app keeps for you, restore it from that export, or bring in a workout history from Strong or Hevy. Export my data builds one file on your phone with your training and health data in it: your workouts, runs and their routes, body weight, nutrition, the notes you write, and, where the app keeps them, heart rate, steps and sleep, with your plan, goals, settings, the first name you gave the app and conversations with the coach, and the time, distance and name of each run you deleted, so it stays deleted when the file is restored. It goes only where you send it. AI keys and sign-in details are never in it. Restoring an export and importing from Strong or Hevy read the file on your phone and send nothing anywhere.
Turning the leaderboard off removes your entries from it. Deleting your account removes them along with the account identifier behind them. Both are in the app, and support@traininglogz.com will do either for you on request.
Removing the app removes the Training Logz data held on that device, except, on iPhone and iPad, any AI provider key you saved for the coach. It does not remove leaderboard entries or cloud backups, which belong to your account rather than your phone. Turn those features off or delete your account first if you want their server copies removed. Anything Training Logz saved into Apple Health stays in Apple Health, where you can review and delete it yourself.
On iPhone and iPad, an AI provider key you saved stays in the device's Keychain after you delete the app, until you erase the device or install Training Logz again; a fresh install removes it before anything can use it. You can remove a saved key on the Coach tab at any time, with Pro or without it. Revoking a key with its provider stops it working at once, anywhere.
Last updated 13 October 2026. See also the Terms of Service.