Most health apps are built around the assumption that your data lives on their servers. For peptide, TRT, and GLP-1 users, that assumption deserves a harder look.
This guide covers what peptide tracking apps actually do with your health data, what to ask before you download, and why the architecture of your tracking tool matters more than its privacy policy.
Tracking your steps or calories is low-stakes data. The worst that happens if your step count ends up in an analytics platform is targeted shoe ads.
Tracking peptides, TRT protocols, or GLP-1 dosing is different. You're logging compound names, doses, injection frequency, and cycle lengths — a detailed picture of a health protocol that often involves compounds not FDA-approved for human use, prescription hormones, or off-label medications.
This data, stored on a cloud server, belongs to whoever controls that server. It can be shared, sold, subpoenaed, or exposed in a breach. Most users do not think about this when they enter their first BPC-157 dose into a health app.
Fitness aggregate. No clinical implications.
Prescription medication. Off-label common. Dose history is medical record.
Controlled substance adjacent. Insurance implications. Off-label compounds.
Research chemicals. Regulatory status uncertain. FDA review ongoing.
Most health apps default to cloud architecture because it enables sync across devices, account recovery, and backend analytics. Those are real benefits. They come with a real trade-off.
The trade-off is real. Cloud sync is convenient. For step counts and workout logs, the trade-off is reasonable. For detailed peptide protocols, TRT dosing history, and GLP-1 records — data that intersects with controlled substances, prescription medications, and legally-gray compounds — on-device storage is the conservative choice.
Before you enter your first dose, ask these questions. An app that cannot answer them clearly is using an architecture you don't fully understand.
Good answer
On your device. We have no server-side copy of your health data.
Watch out for
Securely in the cloud. / We use enterprise-grade encryption.
Encryption describes how data is protected in transit or at rest. It does not describe where it lives. Encrypted cloud storage is still cloud storage.
Good answer
No account required. Download and use immediately.
Watch out for
Sign up to get started. / Required for backup and sync.
An email requirement creates a persistent identity tied to your health data. It also means someone has a record of who is using the app.
Good answer
No. Our architecture makes this impossible — we hold no data.
Watch out for
We may share aggregated, anonymized data with partners. / See our privacy policy.
Aggregated and anonymized data is routinely de-anonymized. If the answer redirects to a privacy policy without a direct answer, read the policy.
Good answer
Your data is deleted with the app. It was only ever on your device.
Watch out for
We retain data for 30/60/90 days after account deletion. / Contact support to delete your data.
Data retention after deletion is standard cloud app practice. Your health logs may persist on servers for months after you stop using the app.
Good answer
Yes. Export as CSV or PDF at any time, on demand.
Watch out for
Export available for Pro users. / Contact support for a data export.
Your health data should be portable. If export requires a support request or a paid tier, the app is making it difficult to leave.
Protocol was built around a specific architectural decision: health protocol data — doses, compounds, injection history — should never leave the device it was entered on.
Where is my data stored?
SQLite on-device. No server receives your health data. Ever.
Account or email required?
None. Download and use without creating any account.
Third-party data sharing?
Structurally impossible — no data exists on our servers to share.
Data after deletion?
Gone with the app. Nothing persists externally.
Data export?
CSV or PDF, on demand, any time. Your data, portable.
Analytics SDKs?
No health data analytics transmitted. Your protocol stays private.
The architecture is the privacy policy.
A privacy policy is a commitment. Architecture is a fact. Protocol's on-device storage is not a policy that could be changed in next month's update — it is the fundamental design of the system. There are no servers to send your data to. That isn't a feature. It's the structure.
Unique to Protocol
The only health tracking app with a built-in disguise.
Stealth Mode lets you change Protocol's home screen icon to anything — a weather app icon, a blank square, a generic utility icon. Nothing on your home screen identifies it as a health tracking app.
Combine that with Face ID or Touch ID as the only way to open the app, and your peptide protocol, TRT history, GLP-1 logs, and lab results are behind two layers of deniability: the icon no one recognizes, and the biometric no one else can pass.
Stealth Mode does not affect data storage or functionality. It is an additional privacy layer on top of Protocol's on-device architecture.