peptracks is built so that your health records can't be tied to you — because we never learn who you are in the first place.
We don't claim one blanket shield over everything — that's rarely true when a company says it. Here's exactly what protects each kind of data you create, in plain terms.
When you log an adverse event or a benefit and choose not to share it, the description is encrypted on your device before it's ever sent to us. We store it only as ciphertext. The key is derived from your private key and never leaves your phone — so even if our servers were breached, those notes would be unreadable. We cannot decrypt them. Neither can anyone who takes our data.
If you choose to share an observation with the community, that description is stored unencrypted — that's the whole point, so others can read and learn from it. Shared notes, and replies to them, are public: anyone can read them on peptracks.com without an account, and they may appear in search engines. It's attributed only to an optional handle you pick, never to an email or a real identity. You decide, note by note, what's private and what's shared.
Your doses, cycles, and timeline power the aggregate patterns the whole collective learns from, so our servers need to be able to read this data to analyze it. It's encrypted at rest like everything else — but what really protects you is that it isn't connected to any person. Records with no name attached can't be traced back to you, which is exactly why we can study them safely and why you can trust what they tell you.
The real test of a privacy claim isn't what a company intends. It's what it's physically able to hand over when pressured. Here's ours.
Shared community notes are the one exception — those are public by the author's choice, attributed to a handle, never to an identity.
Beyond the identity wall, standard protections apply to all of your data — the ordinary, unglamorous engineering you'd want underneath any health app.
Every connection between your app and our servers uses current TLS encryption, so nothing travels across the network in the clear.
Our database is fully encrypted on disk. On top of that, your private notes are encrypted a second time, client-side, to a key only you hold — so we can't read them even though we hold them.
These aren't promises we're asking you to trust. They're consequences of how the app is built.
Read your private notes. They're encrypted to a key we never see.
Identify you. No name, email, or password is attached to your records.
Sell or trade your data. No ad networks, no vendor relationships, ever.
Reset your account. Only your 12-word recovery phrase can — keep it safe.
Contact you unasked. Email is optional, stored separately, and never linked to your logs.
Hand over "a person's" data. There are no people in our database — only anonymous keys.
You can optionally add an email to hear about new features. It's stored under a random ID, in its own place, and is never connected to your protocols, doses, or notes. Share nothing and the app works exactly the same.
We built peptracks so we can't betray your trust, not just so we won't. That's the difference, and it's the whole point.
Get started — it's free