Saved on this device only
Your score history
Every card you have saved from a calculator, kept in this browser. Nothing here was uploaded, there is no account, and no one else — including us — can read it.
A transfer code from another device
Nothing added yetThis link carries saved tests from another device. They travelled inside the link itself — they were never uploaded, and no server saw them. Add them to the history on this device?
The code could not be read. It may have been cut short when the link was copied, or scanned before the other screen finished drawing. Show the code again on the first device and re-scan it.
History is not available in this browser
Storage blockedThis page keeps your saved cards in your browser’s own database (IndexedDB). This browser will not give the site a database — usually a private or incognito window, a browser set to block site data, or a managed device profile.
The calculators all work normally; only saving does not. In an ordinary window, the Save to history button appears under every result.
Nothing logged yet
How this worksScore a test on any calculator, then press Save to history under the result. From then on this page shows every card you have saved: the total, whether it passed, how each event moved since the last time, and the trend across the year.
It exists because a PT test is not one number — it is the same five or six events measured again every six months, and the useful question is never “what did I score” but “what moved, and which event is closest to failing.”
A record of a service member’s fitness results is exactly the kind of file that should not sit on somebody else’s server. So there is no server. There is no account, no sign-up and no email field, and nothing on this page is ever sent anywhere. The cost of that decision is that your history lives on this one device — which is why the backup file in section 05 matters.
Summary
Trend
Total over timeOne figure per branch, plotted at the date each card was saved. The broken rule is the pass line the engine used for that test, not a number typed onto this page.
Per-event movement
Your latest card against the one before it, event by event. Every point below is produced by re-scoring the saved card through the same engine the calculator uses — no figure on this page is stored, transcribed or estimated.
The log
Newest firstYour data
Backup, restore, deleteThis is the part that matters. iOS Safari deletes a site’s stored data after 7 days without a visit, and PT tests are roughly six months apart — so a history kept only in the browser can be gone by the time you next need it. Two things prevent that: add the site to your Home Screen, and keep a backup file.
- iPhoneSafari → the Share button → Add to Home Screen. A home-screen web app is exempt from the 7-day rule, and opening it from the icon counts as a visit.
- AndroidChrome → the menu → Install app or Add to Home screen.
- BackupExport the file below after every test. It is the only copy that survives a wiped browser, a new phone, or seven days away.
Getting your history onto another device
Two ways, no accountThere is no login here to carry your history between phones, so it travels the way any other file of yours does — through storage you already own, or straight from one screen to the other. Both routes keep the rule this site is built on: your scores are never uploaded to us, and we never hold a copy.
- Your own cloudExport the backup, and when the Share sheet appears choose Save to Files → iCloud Drive on iPhone, or Save to Drive on Android. The file is then on every device signed in to that account. Open it here with Import a backup and your history is there. This is the closest thing to sync, and it runs on your account, which you can already recover if you lose the phone.
- Phone to phonePress Show transfer code below and point the other phone’s camera at it — the ordinary camera app, no scanner to install. Your scores are carried in the link itself, so they cross between the two screens as light and never travel over a network at all. Good for one code’s worth of tests; past that, use the file.
Point the other phone’s camera at this and open the link it offers. That phone will ask before adding anything. The code holds your saved scores, so treat it like the scores themselves — anyone who photographs it can read them.
Delete every saved test on this device? This cannot be undone, and there is no copy anywhere else. Export a backup first if you might want it.
A plain JSON file named mfc-history-YYYY-MM-DD.json, written by your browser to wherever you send it. It never touches a server. Importing it on another device merges by record, so importing the same file twice adds nothing the second time and never duplicates a test — and neither does scanning the same transfer code twice.
No account, no login, no email field, no server — and nothing that syncs through one. Your saved cards are written to this browser’s own database and read back by this page. Moving them to another device puts them in a file you control or a code you hold up; neither route sends them to us. This URL loads no session-replay script, so nothing renders your saved scores to anyone but you. The privacy policy states the same thing in full.
- Stored in
- IndexedDB · database mfc
- What is stored
- The result permalink, its date and its total
- Transmitted
- Nothing, ever
- Scoring
- /assets/js/mfc-engine.js
- A row is a link, not a score sheet — the permalink the calculator wrote.
- Points are re-derived from it by the engine, never stored or transcribed.
- Pass lines come back with the score — none is typed onto this page.
Saving is always an explicit action — a result is never written to this log on its own. Report an error.