JST Fitness — Consumer Health Data Privacy Policy

Last updated: 17 October 2026

What changed on 17 October 2026. This is the launch edition of this policy, written for someone using JST Fitness for the first time and describing the app as it is today. It names JST Fitness LLC as the company responsible for your consumer health data; says that you need an account to use the app and that cloud sync stays optional; says that the server logs our host keeps on its own schedule could link the exercise clips your phone streams to your account; says that deleting your account cannot recall words our AI tools have already read; and says how to appeal if we refuse a request, and that we answer an appeal within 45 days. The change log that closed this page is no longer published; it is kept word for word and sent on request. Earlier versions are kept on file; email [email protected] for a copy of any of them.

This document is the Consumer Health Data Privacy Policy required by Washington State's My Health My Data Act. It is a separate document from our general Privacy Policy — linked at the foot of this page — which still applies to everything else the app does: accounts, error reports, feedback and the rest.

It covers consumer health data: the health-related information you type into JST Fitness. If you are a Washington or Nevada resident, this page is written for you, but the practices it describes are the same for everyone who uses the app, wherever they live.

What consumer health data we collect, and why

Almost everything in this list is data you type in yourself or pick from a list in the app, and nobody else sends us health data about you. Three things are read from elsewhere on your phone, and only once you agree to them: your step count, and weigh-ins recorded by a smart scale — both read from Android's Health Connect with your permission, each asked for separately, each off until you switch it on, and each described below — and, for one outdoor cardio set at a time, your phone's location from its GPS, once you have agreed on the route screen the app shows at your first START on an outdoor set with Track route on, and only while that set has Track route on, from which the app works out that set's distance ("Where you are: only while you record a route" below). A food's nutrition figures can also come with the food rather than from your typing — from a barcode scan, the community list, the app's own restaurant catalogue, or, for some everyday foods in the app's own catalogue, USDA FoodData Central — or be read from its nutrition label by your phone's camera, or from the calorie figure a restaurant menu prints, for you to check before you add it, as "Where it comes from" below sets out. What the app works out for itself — the figures at the bottom of this list and in the paragraph after it, and a GPS distance — is named here too, because working something out from what you typed, or from what your phone measured, still counts as collecting it.

The app also works out training figures from what you log — an estimated one-rep max, the personal records worked out from your logged sets, progress charts, your weekly training volume per muscle group, which areas of the body you have and have not trained recently, how often and for how long you trained over a stretch of time and how much you lifted in it, how many different lifts you trained, and how that compares with the stretch before, how many of its weeks or months you trained in and your longest run of them in a row, and how many days you trained in a week or a month against a target you set, and which months reached it. When you finish a workout, its summary can also show an estimate of the calories that workout burned, worked out from its type, how long it lasted and your body weight; and beside your step count, if you switch that on, the app shows the distance and calories your steps imply, from your height and your body weight, and, if you turn on Add calories from steps, adds part of those calories to a day's calorie target. These are derived from what you entered; Washington's My Health My Data Act counts data that is inferred or derived as consumer health data just as much as data you typed, which is why they are named here.

If you leave the weekly report switched on, the app also writes itself a small weekly summary — averages and totals for the week just ended, including your weight and your calories — so one week's report can be compared with the next. Your steps and the days you sat appear in the report on screen, but they are read fresh from their own records each time and are never copied into the stored summary. The app keeps at most your 56 most recent weekly summaries — a little over a year, so that the yearly summary described next can be built from them; it lives only on your device, is included in the backup file you can export, and is deleted with everything else when you delete your account or when a different account signs in on this device. Switching the weekly report off in Preferences stops new summaries being written.

If you choose to share an image — your weekly report, your training report, a single workout from your history, or one of your saved routines — the card you share carries training figures only. For a workout: its name and date, how long it lasted, how many sets you logged, the distance of a run, walk, ride, row or swim (typed in, or measured by GPS when you tracked the route — never the route itself), and its exercises, each with the sets and reps, seconds, or time and distance you logged and the pace worked out from them — never the weight you lifted, a weight you carried, or the lifts you hold a record on. For a routine: its name, how many exercises and sets it plans — or, for a circuit, how many rounds — and its exercises, each with its planned sets and reps, seconds or minutes — never a planned weight. On every picture, the names you gave your routines and exercises are printed as you typed them. For a week: its dates, a one-line headline (which may name one of your goals as you named it, your average steps a day, how many records you set or how many days you showed up), which days of that week you showed up, how many workouts and active days you had, your step total, how many records you set, and how many badges you earned with up to three of them by name; it is one of the two pictures that can carry a weight — the total weight you lifted that week, up to three of the records you set, each with its weight and reps, and the badges you earned by lifting a stated weight or total (such as "Three-Plate Bench" or "Half-Million Club"). Before you share it, the app lists every part with what it would put on the picture: those three start unticked each time the list opens and go on the picture only if you tick them, the rest start ticked unless you unticked them earlier while the app was open, and anything you untick stays off. For your training report: the window's dates, a one-line headline (how many records you set, or how many times you trained and how often), how many times you trained in each week of the window (each month, over a long stretch), how many sessions, how many a week, your total training time, how many records you set, and your most-trained lifts with how many sessions each; when you started training partway through the window, it names the day you started, from which those figures count. It is the other picture that can carry a weight — the total weight you lifted in the window, and up to three of the records you set, each with the day you set it, its weight and its reps. Before you share it, the app lists every part with what it would put on the picture: those two start unticked each time the list opens and go on the picture only if you tick them, the rest start ticked unless you unticked them earlier while the app was open, and anything you untick stays off. Never your body weight, your calories or your meditation. The image is made on your phone and goes only where you send it through Android's own share sheet.

Once a calendar year ends, the app also writes itself one summary of that year — built from those weekly summaries and from your workout, weight and achievement records — so you can look back at a year after its week-by-week detail has gone. There is one per year and it is never recomputed. Like the weekly summaries, it lives only on your device, goes into the same backup file, is never uploaded, and is deleted with everything else when you delete your account or when a different account signs in on this device.

Each item is collected for the purpose written beside it. None of it is used for advertising, profiling, scoring, or any purpose other than showing you your own data inside the app you put it into. Two things we do are not "showing you your own data", and rather than let this sentence quietly stop being true, both are named here.

The first is that we count sign-ins by country on an internal page, from the address your sign-in already carries. It is described in full under "Where you are: only while you record a route" below, and it touches nothing on the list above.

The second does touch the list, so it is worth saying plainly. On the same internal page we count how many accounts have synced recently — in the last 7, 30 and 90 days — and how much room everything synced takes together. Those two figures are worked out from data you already chose to sync; they are totals across accounts and never a row about one person, no third party receives them, and nothing extra is recorded to produce them. They cover only accounts that have given consent to sync: if you have switched sync off, or never switched it on, you are not counted in them.

One count on that page is not gated on your sync consent, and saying why is fairer than letting "only accounts that have given consent" carry a weight it does not. The page counts how many foods have been shared into the community list, and how many of those are hidden. A shared entry carries no account id — only a keyed hash of the account that shared it — and we could match that hash to a consent record if we kept a map from one to the other. We deliberately do not keep one: that map is the very link the sharing feature is built to avoid. So the count is not gated, on purpose, and it rests on our legitimate interest in knowing how the shared list is being used rather than on the consent you gave by switching sharing on for a food — that consent is about publishing your entry, not about being counted. This is available as a basis precisely because the fact that a food was shared is not health data about anybody. Switching sharing off, or deleting your account, cuts the link between you and the entry either way.

Each figure is worked out fresh, from whatever a consenting account holds at the moment the page is drawn — so an entry you logged long ago is part of the total you are counted in, in the same way as one you logged this morning. One chart groups accounts by the day each last synced, so its bars carry dates: the date on a bar is the day somebody last synced, not the day we counted. Nothing new is kept to make any of this possible.

Where it comes from

Mostly, you type it in. Every category above comes from you entering it in the app — except two things Android's Health Connect passes to the app after you grant the matching permission, each a separate permission and each off until you switch it on: your step count, which never leaves your phone, and the weigh-ins your smart scale recorded, which join your weight log and sync with it. A cardio set's distance can also come from your phone's own GPS, in the Android app, for an outdoor set with Track route on — every such set once you agree to it on the route screen, unless you switch it off, and a cardio exercise you made yourself only once you switch it on: the app reads your location from START to DONE on that set, works the distance out on your phone, and keeps the distance and, on your phone only, a drawing of the route with its first and last 200 m left off ("Where you are: only while you record a route" below). The nutrition figures attached to a scanned barcode come from the public Open Food Facts database. If you have the app read a food's nutrition label with your phone's camera, the figures it fills in come from that label, read on your phone, for you to check before you add the food; the picture is never kept. If you have the app read a restaurant menu, the dishes it finds in the app's own restaurant catalogue are that catalogue's rows (below), and a dish the catalogue has no match for, or holds at a figure far from the one the menu printed, can be opened as a food of your own, filled with the dish's name, the restaurant's name and only the calorie figure the menu printed beside it, read on your phone, for you to check before you add it. The picture is never kept, and nothing read from the menu is kept unless you pick or open one of its dishes, which is then kept like a food you searched for or typed. A food you pick from the community list comes with the figures the person who shared it entered from its label — its calories and macros, and its fibre and sugars if they entered them. A restaurant food you pick from the app's own catalogue comes with the calories and macros the catalogue holds for it and, where the app has them, the fibre, sugars and sodium its chain publishes; they are built into the app, so picking one fetches nothing and tells the chain nothing. An everyday food you pick from the app's own catalogue — one with no restaurant or brand, such as a banana or a hard-boiled egg — comes with the calories and macros the catalogue holds for it and, where the app has them, the fibre, sugars and sodium that USDA FoodData Central, the United States Department of Agriculture's public food database, gives for it; for those foods the calories and macros are FoodData Central's too. They are built into the app as well, so picking one fetches nothing and tells the Department nothing. If you import a recipe from a web page, its name, number of servings and ingredient list come from that page, and the food and amount on each line are the app's own match against its catalogue or your foods — nothing from the page is kept unless you save the recipe.

If you bring back a spreadsheet this app exported (Profile → Backup & Restore → Import from Spreadsheet), the workouts, weigh-ins, measurements and foods it adds come from that file, read on your phone, and join your logs in the categories above. A workout in it that names an exercise the app does not know adds that exercise to your own, under the name the file gives it, unless you match it to one of the app's on the import screen; and if one of its weigh-ins is newer than any you have, your current weight follows it, as it does when you log one. We do not buy health data, no third party sends it to us unasked, and nothing is inferred from what you do outside the app.

The rest the app works out for itself, from numbers you already gave it. Washington's My Health My Data Act counts what is derived exactly like what you typed, so those figures are named in the list above rather than left implied: the BMI, BMR and TDEE maths behind your calorie and macro targets; the check on whether your height and weight put you below a BMI of 18.5, and the same check of a weight goal's target; the energy-balance estimate on the Weight tab, and the month in which your weight trend would reach a weight goal you set; the training figures built from the workouts you logged — an estimated one-rep max, the personal records worked out from your logged sets, progress charts, your weekly volume per muscle group, which areas you have not trained lately, how often and for how long you trained over a stretch of time and how much you lifted in it, how many different lifts you trained, and how that compares with the stretch before, how many of its weeks or months you trained in and your longest run of them in a row, and how many days you trained in a week or a month against a target you set, and which months reached it; the estimate of the calories a finished workout burned, from its type, how long it lasted and your body weight; the distance and calories your step count implies, from your height and your body weight, and, if you turn on Add calories from steps, the part of those calories added to a day's calorie target; when a fast you started on the fasting timer ends, and how long is left of it, from the hours you chose and when you tapped Start; the day's total of the fibre, sugars and sodium of the foods you logged as eaten, shown in the day's breakdown with how many of those foods each comes from, and not while Hide calories is on; the achievements and XP you earn from what you record; and, if you leave the weekly report switched on, the weekly summary itself. Every one of them is arithmetic on what you entered or, for the step figures, on the step count Health Connect passes to the app. None of it is a measurement, and none of it is a diagnosis.

Who we share it with

Nobody, in the ordinary sense of the word. No consumer health data is disclosed to advertisers, data brokers, analytics companies, insurers, employers or anyone else.

One thing that is worth saying plainly before the list, because it happens whether or not you sync: the exercise demonstration clips are streamed from our hosting. Playing one — in the library, during a workout, or through a follow-along circuit, which fetches a clip per station — carries your IP address to that host, the way any video on the internet does. We build no record of which clips you play, and the clips are the same for everyone: nothing about you is sent in order to fetch one. Those requests appear in routine server logs, which our host keeps on its own schedule, not ours. Those logs also hold the app's signed-in requests, which carry your account's id, so while they are kept they could link the clips fetched from your connection to your account; we never use them to work out who watched what.

The only company that holds the consumer health data you record in the app is the one that stores it for us. Two others see a single, narrow thing when you choose to use them, and they are listed next. The last ones listed can receive words you typed into a message to us, and only then:

One more thing belongs here, because it is the only place in the app where something you typed can be seen by another person, and because "share" is exactly the word the Act uses. If you add a food to the food list yourself, you can switch that food to shared, and it then appears in every other user's food list marked "Community". What appears is the product — its name, brand, serving, barcode and the calorie, macro, fibre and sugar figures you entered (not a fibre or sugar figure above the shared list's own limit, nor its sodium or a drink's alcohol, which stay in your own foods). It is the same for everyone who sees it, it says nothing about you, and it is not connected to your food log: not whether you ate it, not when, not how much. Nobody is shown who shared it; there is no name, profile or "shared by" line anywhere in the app. We keep, privately, a scrambled reference to the account that shared each entry so that reports can be acted on; it is never shown to anyone and it is cut when the account is deleted or sharing is switched off. So what other users receive is information about a food, not consumer health data about you. Even so, the switch is off unless you turn it on, food by food, the app tells you beside it what will be shown before you do, and we treat turning it on as your specific authorization for that one food. Nothing is shared for a food you never switched on, and your food log itself is never shared with anyone.

Nothing on the list above is collected in order to be passed to anyone else. Supabase holds it because it runs the database the app stores it in, and it holds it on our instructions. Open Food Facts receives a barcode number and your IP address, and only when you choose to scan a food's barcode. A recipe website receives the address of the page you chose to import, your IP address and your phone's browser identifying line, and only when you import from it. Anthropic receives the words of a feedback message you chose to send, or a crash report's error message, and only when we work on it. Cloudflare and Google receive an email you chose to send us, and only then. Nobody else receives any of it. The one sharing switch in the app is the one on a food you added yourself, described above; it shares that product's label facts with other users and nothing about you, and it is off unless you turn it on.

Google receives each Google sign-in and, if you set no photo of your own, each load of your Google account picture, as it does from any app or site that uses them, under its own privacy policy; neither carries consumer health data. Apart from that, nobody — not us, and no other company through the app or our website — collects information about what you do over time across other apps or websites.

We do not sell your consumer health data

No consumer health data is sold — not for a price, and not for anything else of value, under any of the broader definitions of "sale" that privacy laws use. There is no authorization on file permitting it, because we have never asked for one. If that ever changed, the law would require a separate, specific authorization that you would have to sign for that one purpose: it cannot be folded into anything you have already agreed to, and nothing you have agreed to so far permits it. The app has no advertising, no ad identifiers, no advertising or analytics software and no data brokers anywhere in it. The only usage figures we keep are the whole-app counts described under "What consumer health data we collect, and why", and the only outside software that reports on itself is Google's — its barcode scanner, and the on-device text reader that reads a nutrition label or a restaurant menu — each reporting to Google on itself, in a report that names this app and the phone, and nothing you log, scan or have read (the general Privacy Policy, "Barcode scanning and the camera", lists what they send).

Where you are: only while you record a route

JST Fitness reads where you are only between START and DONE on an outdoor cardio set with Track route on, including while the screen is off or you are in another app, and at no other time; while it records, the app shows a notification card if notifications for JST Fitness are on. It asks Android for your precise location while you are using the app, and never for "all the time" (background) location. The first time your account presses START on an outdoor set with Track route on, it shows a screen saying what is read, what for, where it goes and how to stop, before anything is read, and it records on your phone which wording you agreed to and when; that agreement is the consent this law asks for before collection. The screen says that once you agree, Track route is on for every outdoor set, and that on a cardio exercise you made yourself it starts off until you switch it on under its stopwatch; switch it off under the stopwatch, before START, and that exercise records no route until you switch it back on, and tap Not now on the screen — or answer no to Android's location question — and it stays off on every set until you switch it on. The app cannot tell a treadmill or an indoor bike from the road, so switch it off under the stopwatch for an exercise you do indoors. The app remembers those choices on your phone only. While a set records, the app also draws the route under the stopwatch as you go, on your phone and only on your screen: nothing is drawn until you are 200 m from where the set started, no part within 200 m of that place is drawn after, and the drawing is never stored, synced, sent or shared. Recording stops at DONE, from the card's Stop route button, two minutes after you leave that set for another one or for Quick Log, when you turn Track route off in Profile → Preferences, or by itself after 4 hours. The distance is saved with the set and syncs like a distance you type. The location points stay on your phone, are never sent to us or anyone, are not in your backup file, and are deleted once the set is logged, started over or discarded, at sign-out, and in any case no more than a day after recording stopped — except after a Force stop in Android's settings, which stops the app's own clean-up too; they then go the next time you open the app. One location is kept a little longer: where the drawing of the workout's first saved route begins (its first kept point, never where that set started), so that the drawings of the workout's later sets can be placed beside it. It stays in a private file of its own on your phone until you save or discard the workout or sign out, and never more than a day after that route's recording stopped (after a Force stop, until you next open the app); no drawing keeps it. You can stop at any time: press DONE, or Stop route on the card, to stop a route that is recording; switch Track route off under the stopwatch, before START, and that exercise records none until you switch it back on; turn Track route off in Profile → Preferences, and no set records a route until you turn it back on and agree on the screen again; or remove JST Fitness's location permission in Android Settings → Apps → JST Fitness → Permissions, and the app shows its screen again the next time you press START on an outdoor set with Track route on, where Not now keeps Track route off on every set; the rest of the app keeps working, and you can type a distance instead. Routes already saved stay on this phone until you delete them.

The route you see afterwards stays on your phone. When you press DONE, the app keeps a simplified drawing of the route, in a file on your phone: the line you went along, measured in metres from its own first point, with every part of it within 200 m of where the set started or finished left off — wherever the route passes those places, not only at its two ends. A route that never gets more than 200 m from both ends keeps no drawing, only its distance; the distance and the splits still count the whole route. The file holds no latitude or longitude: it places the drawing in metres from where the workout's first drawing begins, so one exercise's sets are drawn each in its place. The drawing is never uploaded or synced and never sent to us or anyone. It is in your backup file, as on screen, as a drawing in metres with no latitude or longitude in it; keep that file somewhere private. A saved route cannot be edited; you can delete it on its own or with its workout, and correct the distance it shows. Routes are only on your phone, and on any phone you restore your backup file onto: we cannot see or delete them, so delete them in the app, or uninstall. Signing out keeps them; deleting your account in the app, or a different account signing in on this phone, removes them.

The app does not use a geofence around any location, and specifically does not use one around a healthcare facility, pharmacy, clinic or any other place, for any purpose whatsoever. Your location is never sold or used for advertising.

One thing sits close enough to location that it belongs here rather than in a footnote. When you sign in, the sign-in carries your IP address, the way every request over the internet does, and our sign-in provider records it against your session. We look at those addresses in exactly one place — our internal support page, which the two people who run the app can open ("Who is responsible" below) — and we count two things there, both only ever by country.

The first is how many sign-ins came from each country, so we can see where the app is being used. The second is how many accounts on a trial or a paid plan last signed in from each country, so we can see where the people actually using it are. The second means that, for the moment the page is drawn, an account is matched to the country its last sign-in came from.

Both counts are worked out as that page is drawn and nothing is written down — no city, no coordinates, no map pin, and no stored record of where any account signed in from. Neither is ever attached to your weight, your food log, your workouts or anything else on the list above, neither is used to work out where you live, and neither goes anywhere beyond that page. An address of this kind is nowhere near the precision this law reserves the word "precise" for, and we do not make it more precise.

Nothing syncs unless you ask it to

You need an account to use JST Fitness, but cloud sync is separate and stays off until you agree to it. Until then there is nothing to sync: none of the data listed above is uploaded, and it stays in local storage on your device.

A few things still leave the phone without sync, and each is described elsewhere on this page rather than buried here. Playing a demonstration clip fetches it from our hosting, which carries your IP address the way any video on the internet does — that is the "Who we share it with" section above. Scanning a food barcode, or importing a recipe from a web page, sends a request to that service or website, described in the same section. And if you send feedback with the "include usage" box ticked, the counts the form prints for you before you send go with the message; your level is one of them, and your level is partly earned from what you log. None of them happens on its own, and none sends your logs. The general Privacy Policy covers the rest of what the app sends, including crash reports.

When you create your account, the app asks you for explicit consent before it syncs anything, and records which wording you agreed to and when. You can stop the sync at any time at Profile → Preferences → "Sync my data to the cloud", which stops your data being synced and then removes your synced copy from our servers unless you choose to keep it (the next paragraph). Crash reports, feedback you send and a food you chose to share are not part of the sync and do not stop with it; each is described on this page or in the general Privacy Policy.

Switching sync off removes your copy from our servers, unless you keep it. When you switch sync off, the app asks what to do with the consumer health data you synced, and leads with removing it. "Remove my copy" removes all of it from our servers, and keeps only your consent record, which holds no health data: it shows which wording you agreed to and when, that you withdrew it, and which versions of our Terms and Privacy Policy you accepted. That record is how we can show all of that, and how your other devices learn to stop syncing too. "Keep my copy on the server" leaves your copy where it is. Removing it does not delete your account or anything on your phone: before anything is removed, the app first syncs your copy down to your phone, the same way it does when you sign in. If the removal cannot finish — the app cannot reach our servers, or cannot check that your phone has all of your copy, say — the app tells you, and your copy stays where it is; it also stays if the app closes before you answer. Either way, while sync is off you can remove it later with "Remove my copy from our server", under the same switch. Another device of yours that still has sync on stops when it next connects, and anything it sends before then stays on our servers. Keep every device you use JST Fitness on up to date: one still running an older version of the app can bring back something you deleted or corrected on another, until it is updated.

How to see, correct or delete your consumer health data

You have the right to know what consumer health data we hold about you, to be told whether any of it is shared or sold and who else has held it, to have it deleted, and to withdraw the consent you gave for it to be collected or shared. To use any of them, use the app as below, or simply email the address at the bottom of this page and ask. Requests are answered within 30 days, and using any of these rights costs you nothing and changes nothing about how the app works for you. Here is how each one works:

If we ever refuse a request, we will tell you why, and you can appeal by replying to that email. We answer an appeal within 45 days. If the appeal is denied you may complain to the Washington State Attorney General at www.atg.wa.gov/file-complaint or, if you live in Nevada, to the Nevada Attorney General at ag.nv.gov.

What the app cannot correct for you

Who is responsible

JST Fitness is run by JST Fitness LLC, a Florida limited liability company, which is responsible for what happens to your consumer health data. It was founded by two people, its founder and a co-founder, who run it, and its founder is the person to write to about it:

Tristan Allard Email: [email protected]

His co-founder helps run the app and can see our internal support page: account email addresses, the feedback messages and crash reports we receive (a feedback message can mention your health), and sign-in records. That page does not open the consumer health data you record and sync — your weight, measurements, food or workouts. The general Privacy Policy lists everything the page shows, and how we protect your data.

If you used JST Fitness before launch

JST Fitness was tested by a small group before it launched, and a few things from that time can still be true of a tester's consumer health data. If any of these is yours, email us and we will help you correct or remove it:

Contact

Questions about this document, or requests about your consumer health data:

[email protected]

Changes to this document

The "Last updated" date at the top is the day this version took effect. Whenever we change what this document says about the consumer health data we collect, where it comes from, why, who receives it, how long we keep it, or your rights over it and how you use them, that date moves and the note at the top of this page says in a few lines what changed. When the change matters — something new leaves your phone, someone new receives it, it is kept longer or used for a new purpose, or your rights change — the app also asks you to agree to the updated Privacy Policy before you carry on. We will not start sending a new kind of consumer health data off your phone, or use or share what we hold for a new purpose, until we have told you in the app and, where the law asks, you have agreed; you can always switch sync off or delete your account instead. Data you gave us before a change is never used or shared in a new way unless you have agreed to it. Small corrections — a typo, a clearer sentence, a fixed link — do not move the date. Earlier versions are kept on file; email [email protected] for a copy. The general Privacy Policy, linked at the foot of this page, describes the same practices in more detail, and the two are kept in step.