Health tracking apps are a privacy nightmare.

If you download a popular habit tracker, weight loss app, or period tracker today, there is a very high probability that your data is being sent to a remote server, analyzed, and often shared with third-party data brokers or advertising networks.

When it comes to tracking steps or water intake, some people are willing to make that trade-off for convenience. But when it comes to tracking complex, personal health protocols—specifically peptide cycles—that trade-off is unacceptable.

This is the story of why we built Peptide Planner & Tracker, and why we chose a “local-first” architecture.

The Problem with Cloud-Based Trackers

Before building our own tool, we looked for existing solutions to track multi-peptide cycles. We found generic habit trackers and complex medical logging apps, but they all shared the same fundamental flaw: they required an account, and they synced data to the cloud.

When you sync health data to a server you don’t control, you are trusting the company behind that server with your most sensitive information. You are trusting that their security is flawless, that their privacy policy won’t change when they get acquired, and that they won’t comply with broad data requests.

For the privacy-paranoid biohacker or longevity enthusiast, “trust us” is not a valid security model.

The Local-First Solution

We decided that the only way to build a tracker we would actually use was to remove the server entirely.

Peptide Planner & Tracker is built as a “local-first” application. When you open the app, it runs entirely within your browser (or as a Trusted Web Activity on Android). When you log a dose, that data is saved directly to your device’s hard drive using a web standard called IndexedDB.

What this means for you:

1. Zero Analytics: We don’t know how many people use the app, what compounds they track, or how often they open it. We have zero visibility into your usage.
2. No Accounts: There is no login screen, no email verification, and no password to forget. You open the app, and you are immediately in your private database.
3. True Ownership: Because the data only exists on your device, you are the sole owner. If you want to back it up, you export a JSON file. If you want to delete it, you clear your browser data, and it is gone forever.

The Trade-offs of Local-First

Building a local-first app isn’t without its challenges. The primary trade-off is that we cannot recover your data if you lose your device.

In a traditional cloud app, if you drop your phone in a lake, you just log in on a new phone and your data is there. With Peptide Planner & Tracker, if you haven’t manually exported a backup of your JSON file, your data sinks with the phone.

We believe this is a feature, not a bug. The friction of manual backups is the price of absolute privacy.

A Tool, Not a Service

Ultimately, we view Peptide Planner & Tracker as a digital equivalent of a physical leather-bound journal.

When you write in a physical journal, the pen manufacturer doesn’t get a copy of your words. The journal doesn’t analyze your entries to show you targeted ads. It is simply a tool that facilitates your personal record-keeping.

We built Peptide Planner & Tracker to be exactly that: a fast, complex, highly capable tool that lives on your device, serves only you, and keeps its mouth shut.