Where your peptide tracking data actually lives

Where tracking data lives, in short#

Your tracking data lives in one of two places: on your phone, or on a server run by the app's developer. Everything else about peptide tracking privacy follows from that choice. A protocol log is a long record of entries, dates, vials and how you felt, so it is worth knowing which of the two you are using before you start filling it in.

This article covers the difference between on-device and account-based storage, what App Store privacy labels do and do not tell you, what happens to Apple Health data, and a short list of questions to ask any tracking app. It is about records, not about what anyone should take.

On-device storage versus an account in the cloud#

What each model means#

With on-device storage, the log sits in the app's own storage on your phone, protected by the operating system. There is no login, because there is no server holding a copy that needs one.

With an account model, the app copies your log to a server tied to a login. You can open it on a second phone or a laptop, and the developer's systems hold a version of everything you entered.

The trade-off#

Neither model is wrong. Each one trades something different.

• On-device: nothing sits on a server to be breached, and there is no account to lose access to. The cost is that a lost or broken phone can take the log with it unless you have a backup you control.
• Cloud account: switching devices is easy and a backup is built in. The cost is that your log exists on someone else's system, under that company's policies and security.

Which matters more depends on how you use the log and how much you mind a copy living elsewhere. One entry is low stakes. A year of entries is a detailed record, and that's what you're protecting.

What on-device storage changes#

OptimizedTracker takes the first approach. Its App Store listing says "Everything stays on your device, protected by iOS device encryption" and "No account, no login, no cloud sync." Those are the developer's own statements, so read them as claims about how the app is built.

In practice that means a few concrete things:

• There is no account to create, so there is no email address or password attached to your log.
• Apple Health imports stay on the device too.
• The only sync the listing mentions is optional: you can push upcoming entries to your calendar.

The flip side comes with the design. With no cloud sync, the copy on your phone is the only copy. If you care about a record that survives a lost phone, plan for that yourself, for example with an encrypted device backup. The same logic applies to any record you want to trust later, as covered in how to keep a peptide log you can actually trust.

What privacy labels tell you, and what they don't#

Every app on the App Store carries a privacy label. Read it, but know where it comes from. Apple's App Privacy Details page says developers answer the questions in App Store Connect and are responsible for keeping their answers accurate and up to date. The listing itself notes that the label has not been verified by Apple.

The same Apple page makes a useful distinction. In its words, "Data that is processed only on device is not 'collected' and does not need to be disclosed in your answers. If you derive anything from that data and send it off device, the resulting data should be considered separately." To Apple, "collect" means transmitting data off the device so the developer or its partners can access it for longer than it takes to serve a request.

So an on-device log and a label with a few entries can both be true at once. OptimizedTracker's label lists a small set of items under "Data Not Linked to You": analytics (purchase history, a device identifier, product interaction) and app functionality (purchase history, a user identifier, crash and performance data). Optional crash reports can be turned off in Settings.

Here is the honest reading. "Stays on your device" describes where your log lives. It does not mean an app sends nothing at all, and the label is where the difference shows up. Check both, and remember that neither is an audit.

What happens to Apple Health data#

If you import from Apple Health, it helps to know how Apple itself handles that data, because it is separate from whatever the tracking app does.

Apple's Platform Security guide describes the main HealthKit data as stored under the Data Protection class "Protected Unless Open," with access cut off 10 minutes after the device locks. Apps do not get blanket access. They are granted separate read and write permission for each type of health data, and you can review or revoke those permissions in Settings > Health > Data Access & Devices.

Two more points from the same guide:

• Health data can be stored in iCloud. End-to-end encryption for it requires iOS 12 or later and two-factor authentication. Without that, it is encrypted in storage and in transit but not end to end.
• If you back up through Finder or iTunes, health data is included only when the backup is encrypted.

Those are Apple's settings, not a tracking app's. If you use Health as one source in your log, the Apple Health timeline piece covers how the two fit together.

Questions to ask any tracking app#

You can put these to any app, including this one, before you commit a year of entries to it.

1. Do I need an account, and what does it contain?
2. Where is the log stored: on my phone, on a server, or both?
3. What leaves the device, and why? Check the privacy label and the policy.
4. Can I export my data in a format I can read without the app?
5. What happens if I lose or replace my phone?
6. Is there a backup, and who controls it?

If you are weighing specific apps, for storage use the questions above and the app's own listing and policy, since those are the sources that can answer them.

The takeaway#

Know where your log lives, and know what leaves the device. Read privacy labels as the developer's description, check them against what an app's listing and policy say, and keep a backup you control if the log matters to you. A record you can trust is one whose location, format and copies you understand. For a longer view of what a well-kept record looks like, see the case for tracking less, more consistently.