Where your data lives

Everything you enter stays on your device and, if you're signed in to iCloud, syncs through your private iCloud database — the same place your other app data lives. There is no BioHack Track server, no account to create, and no analytics tracking your inputs. If you're not signed in to iCloud, your data is simply kept locally on this device.

Backup & moving to a new phone

With iCloud sync on, your data restores automatically when you sign in to the same Apple ID on a new device. For an extra belt-and-suspenders backup, use Settings → Export All Data (Backup) to save a full JSON file you can keep anywhere.

Exporting your data

Settings → Data Export offers CSV files for dose logs, lab results, and weight/check-ins (open them in Excel or Numbers), plus the full JSON backup and the Doctor/Financial PDFs. The dose and check-in CSVs can also be re-imported into BioHack Track.

Importing from another app

Settings → Import from Another App reads CSV/JSON exports (including common formats from other trackers), mapping columns to doses, labs, and check-ins, with duplicate detection so you don't double-up. It also reads smart-scale exports (Withings, Renpho, Eufy, and similar) — it matches columns by name and converts kg to your units automatically, so muscle mass, body water, visceral/subcutaneous fat, BMR, and the rest land in your Daily Check-Ins.

What's recorded vs. what's recalculated

Worth understanding once, because it explains a lot of the app's behaviour and one trap.

Recorded — fixed the moment you log it, and never rewritten:

• The dose amount, unit, date, time, route and injection site
• How much came off which vial
• Which vial it was drawn from
• Everything you typed: notes, side effects, check-ins, labs, photos

So editing a protocol changes what happens from now on. It never reaches back and rewrites your history. That's why you can safely change a dose, switch vials, or rename a compound without corrupting past entries.

Recalculated — worked out fresh every time you look at it:

• Cost per dose, which comes from the linked vial's *current* price and amount
• The syringe draw for a given dose
• The In Your System curve, from your logged doses and each compound's half-life
• Adherence, streaks, goal progress and every chart

These are live on purpose — fix a vial's price and every figure that depends on it corrects itself, with no need to re-enter anything.

The one place to be careful. Because cost is recalculated, *editing an existing vial's amount or price also changes what your past doses appear to have cost.* That's correct when you're fixing a typo, and wrong when you've actually moved to a different vial. When the vial genuinely changed, add a new inventory item rather than editing the old one — see *Switching to a different vial size mid-protocol* under Inventory.

When the app warns you before a change

Most edits only affect what happens next. A few reach backwards into records you already have, and those are the ones the app stops to tell you about — with the number of records involved, so you can judge it.

You'll see a warning when you:

• Change a vial's amount or price while doses are logged against it. A dose's cost isn't stored — it's worked out from its vial — so editing those re-values every past dose from that vial. Right when you're fixing a typo; wrong when it's really a different vial (add that as a new item instead).
• Switch currency with prices on file. The app never converts, so amounts simply re-read in the new currency at the same number.
• Change a protocol's frequency, times or start date with doses logged. Adherence and the Missed list are worked out by comparing what you logged against how often the protocol says to dose — so changing the schedule re-scores days that already happened.
• Point a protocol at a different vial, when that changes your syringe draw.

Deliberately quiet. Some things recalculate history on purpose and don't warn, because that's the whole reason you'd edit them: correcting a compound's half-life fixes its past levels curve, and fixing your height or date of birth corrects past BMI and biological age. Those were wrong before; now they're right.

Never warned, because nothing happens. Changing a protocol's dose amount doesn't touch doses you've already logged — each one keeps the amount you actually took.

What deleting actually removes

Deleting behaves differently depending on what you delete, and some of it can't be undone.

• A protocol — this also deletes every dose ever logged under it. Not just the schedule: the history goes too, and with it that compound's adherence record and its line on the In Your System chart. The app warns you before it happens. If you only want it to stop, pause it instead — pausing records the gap so those days aren't counted against your adherence, and everything is still there when you resume.
• A vial — your doses survive, but each one is detached from it and permanently loses its cost basis, so it drops out of your spend figures. Certificates of analysis attached to that vial go with it. Prefer leaving an empty vial listed; it costs nothing and keeps your financial history whole.
• A logged dose — removes it from history, adherence and the levels chart, then asks whether to put the amount back on the vial. Choose *Restore to Vial* if that vial is still in use, or *No, Vial Is Finished* if it's long gone — that way deleting an old mistake doesn't inflate your current stock.
• A household profile — removes that person's data. The Owner's data is untouched.

The pattern: pause or mark finished rather than delete. Almost nothing in the app is harmed by leaving it in place, and two of the four deletions above destroy history you can't get back.

Importing a .zip (any import)

Anywhere you can import a file, you can hand the app a .zip instead — labs, dose logs, check-ins, scale exports. Many services only offer a "download everything" button that produces an archive, so BioHack Track opens it and reads every file inside in one pass. No unzipping first.

The app also identifies files by their actual contents, not their name, so a CSV saved with the wrong extension (or a report that's really a PDF) still imports.

Duplicate detection applies across the whole archive, so re-importing a download you've already brought in adds nothing.