Download
Back to home
Legal

Privacy Policy

Last updated: November 4, 2026

1. Who we are

PeptideLab is a mobile app for tracking peptides, hormones, and supplements. This Privacy Policy explains what information we collect, how we use it, and the choices you have. It covers both the PeptideLab app (the “App”) and our website at peptidelabapp.com(the “Site,” together the “Service”).

The Service is operated by PeptideLab (“PeptideLab,” “we,” “us”). PeptideLab is a personal tracking tool, not a medical device or an electronic health record, and it does not provide medical advice. You decide what to record and what to do with it.

We’ve written this in plain English on purpose. This is the binding document — more detailed than the privacy summary you see inside the app. Specifics may change as the app evolves; when they do, we update the “Last updated” date at the top of this page. If you prefer the architecture explained without legal scaffolding, see How your data works.

2. Information we collect

Information you provide

  • On the Site: when you join the launch waitlist or otherwise submit your email address, we collect that email address and the timestamp of your submission, and use it to send you the updates you asked for.
  • Web setup (optional): you can set up your protocols on the Site before you install the App. Until you sign in, your answers stay in your browser. When you sign in with an email code or with Google, your answers are saved to your PeptideLab account, and any change you make after that is saved there too. They are the compounds, doses, schedules, and start dates you enter; the doses you have already taken; your vials and pens; your time zone; and, only if you give them, your birth year, biological sex, hormone-therapy status, weight, an invite code, how you heard about us, and where you kept track before (an app’s name, or notes) and whether you want an email when you can bring that history over. When you sign in to the App with the same account, the App shows you the setup to review and then builds it on your device. If you ask for it, we email you a summary of your setup, and one reminder the next day if you tick that box. If you ask to hear about bringing your history over, we email you once when that is ready. The Site’s analytics count which steps of the setup you complete. They never receive what you entered.
  • Account: the App does not require a sign-up to work. When you first launch it and accept the consent screen, the App creates an anonymous account for you — a randomly generated identifier with no email, name, or contact details attached. It exists so your backup, subscription, and settings have something to belong to. If you later add an email address (or sign in with Apple or Google), the data under your anonymous account carries over to that account. We use the email address you provide to sign you in.
  • Optional profile: you may choose to add a display name, username, avatar, hormone-therapy status, height, focus areas, experience level, and a free-text “medications” field. All of this is optional and you control it.
  • Biological sex and age: you may provide your biological sex and date of birth during setup — including before you create an account. We use them to personalize the App. Your date of birth is stored to year precision. They are saved on your device and, with cloud backup on, in your account’s backup. When you use an AI-assisted feature they can be part of what is sent to answer you (see “AI-assisted features” below). They are not sent to our analytics provider.
  • What you log (health data): the compounds, doses, injection or application sites, side effects, outcomes, body measurements, and notes you record, and your Lab Assistant conversations. This is stored on your device first (see How your data works for the local-first model). If you leave cloud backup on — it is on by default, including for anonymous accounts — this data is also backed up to our cloud under your account identifier so you can restore it on a new device. You can turn cloud backup off at any time in Settings → Privacy & Data.
  • Period tracker (optional): if you use it, your period dates and flow, symptoms and moods, discharge, sex (whether it happened, protection, and orgasm), ovulation and pregnancy test results, breast self-check notes, birth control method and its dates, pregnancy dates, your cycle settings and reminders, and notes. It is stored on your device first and, with cloud backup on, backed up to your account like everything else you log. You can delete all of it at any time in the tracker’s settings.

Information we collect automatically (analytics and diagnostics)

We collect analytics and diagnostics only after you accept the first-launch consent screen. Nothing is collected for analytics before you consent, and you can turn it off at any time in Settings → Privacy & Data (“App analytics & diagnostics”). When it is on, we collect:

  • How you use the App: the screens and features you open, roughly how long the App is open on each, the main actions you take (for example saving a change or signing in) and whether they worked, app open and close, subscription-flow events, and events such as “dose logged” or “outcome logged.” These are recorded as categories, for example a compound class or route of administration, never the specific compound name, the dose value, or anything you typed.
  • Technical problems: when something you tried fails, or the App freezes or closes unexpectedly, the kind of problem (for example a network error) and the part of the App it happened in. Not the text of error messages.
  • Profile attributes: a few App settings, such as your theme, units, experience level, the focus areas you chose, and whether you have a subscription, attached to your analytics profile — including before you create an account. If you later create an account, your pre-account analytics activity merges into it. Your biological sex, date of birth, and age are not among them.
  • Device and app context:device model, operating system version, app version, language, time zone, a device key (a scrambled form of the identifier your phone gives our App; in a browser, a random code saved in that browser), and an approximate location (a coarse region derived from your IP address — not precise GPS location), used for security, abuse prevention, and product analytics such as understanding usage by region. We use the device key to tell our own test devices apart from real use, and we keep a list of the devices that have used your account (each one’s model, system and app version, and when it was first and last seen) so we can help when you report a problem. Nothing is added to that list while analytics is turned off, and it is deleted with your account.

This information is linked to your account identifier (a random code, which an anonymous account has too), so we can look into a problem you report to us. It is not anonymous. We do not record your screen.

The period tracker is kept out of analytics and diagnostics. What you log in it, and the fact that you use it, are not sent to our analytics provider.

The Site uses cookies and local storage for things like your theme preference and basic security, and Google Analytics, which sets its own cookies to count visits and which pages and setup steps are used. We do not use third-party advertising cookies and we do not track you across other sites.

Information from Apple Health and Health Connect

Your phone’s health store is Apple Health on iOS and Health Connect on Android. If — and only if — you connect it and grant permission, the App reads (read-only) the metric types you allow: sleep, heart-rate variability, resting heart rate, weight, height, body fat, lean body mass, blood glucose, blood pressure, body temperature, oxygen saturation, VO2 max, steps, exercise sessions, and active energy, and, if you use the period tracker, your period and flow records, basal body temperature, ovulation test results and cervical mucus. You choose which of these to grant, and a metric you decline is simply never read.

We store these as snapshots next to your dose logs so you can see them in context. If you allow it, Lab Assistant can also use them to answer your questions (see “AI-assisted features” below). We never write to either health store, and you can revoke access at any time — in the iOS Health app or Settings, in the Health Connect app on Android, or in the App’s own Settings. See Section 6 for the specific commitments that apply to this data.

Information from connected wearable services (optional)

You can optionally connect wearable accounts directly — currently Oura, Fitbit, Withings, WHOOP, and Garmin. If — and only if — you authorize a connection on that provider’s own consent page, the App reads a limited set of daily metrics from the provider’s API (for example heart-rate variability, resting heart rate, sleep duration, weight, body composition, and blood pressure, depending on the device) and stores them on your device alongside the rest of your tracking data. If you allow it, Lab Assistant can also use them to answer your questions (see “AI-assisted features” below).

The sign-in with the provider runs through our website, so the App never contains a secret credential. To keep the connection working, our server keeps the sign-in keys the provider issues (never your password for that service), stored encrypted, and renews them when they expire. The connection belongs to your account: a phone signed in to the same account uses it without connecting again. Disconnecting the provider in the App (More → Integrations) removes the keys from our server for all your devices, and deleting your account removes them too. You can also revoke PeptideLab’s access in the provider’s own account settings.

Garmin works differently from the others. Instead of the App fetching your data, Garmin sends your daily summaries to our server each time your Garmin device syncs, even when the App is closed: for example sleep, heart-rate variability, resting heart rate, VO2 max, skin temperature, weight, body composition and blood pressure, depending on your devices. Our server keeps them in your account, and the App reads them from there, so a new phone has your Garmin data without connecting again. We keep the daily figures only; the minute-by-minute samples Garmin includes are discarded when they arrive. Disconnecting Garmin in the App tells Garmin to stop sending. What already arrived stays in your account, like your other synced readings, until you delete your account. Removing PeptideLab in Garmin Connect also stops the deliveries. If you allow Lab Assistant to use your readings, it can use your Garmin data too, and its answers say when they were derived in part from Garmin data.

FreeStyle Libre (optional)

You can connect a FreeStyle Libre sensor through Abbott’s LibreLinkUp. Your LibreLinkUp email and password stay on your phone and go only to Abbott. While Cloud backup is on, our server also keeps a sign-in key from Abbott (never your password), stored encrypted, so it can save your glucose readings to your backup every couple of hours even when the app is closed. Disconnecting the sensor, turning Cloud backup off, or signing out removes it.

Information from purchases

Subscriptions are handled by Apple’s App Store and by RevenueCat, our subscription-management provider. We receive your transaction and subscription status (for example, whether a subscription is active). We do not receive your payment card details.

A subscription bought on the web is paid through Stripe, the payment processor RevenueCat uses. We keep the email address used for that payment with your account, so that support can find your subscription when you write from that address. It can differ from your account’s email: with Apple Pay it may be an Apple Hide My Email address.

AI-assisted features (optional)

The App includes several optional AI-assisted features. They are off until you choose to use them, and the rest of the App works without them. When you use one, PeptideLab sends the relevant information to our third-party AI provider, Anthropic, to produce the result you asked for. These are the features that share data, and what each one sends:

  • Lab Assistant— your question, together with relevant information from your data in the App, including your lab results. If you allow it, Lab Assistant also sends readings from Apple Health or Health Connect and from connected devices (such as heart rate, HRV, sleep, weight, blood pressure and glucose) with your question, so it can answer using them. You can turn this off in Settings → Privacy & Data.
  • Reading a lab report — the pages of the report you ask us to read. Where your device supports it, the App first shows you an on-device preview with detected identity fields (name, date of birth, address, phone) blacked out, and only that redacted copy is sent; the original file never leaves your device.
  • Bloodwork insights — the marker names and values from the report you are viewing, with related context from your App data.
  • Food and meal logging — the food description you type, or the meal photo you choose, so it can be estimated into nutrition values.
  • Live Chat — the messages you type to us in Live Chat, without your name or email, so we can point you to a help guide that answers your question and suggest a reply to the person answering you. A person on our team sends every reply.

If you never use these features, this sharing does not occur. Your data is not sent to Anthropic for any other purpose, and none of it is sent in the background.

Anthropic processes API data according to its own applicable commercial / API terms and data-retention settings. We do not use your tracking data or your Lab Assistant conversations to train PeptideLab’s own machine-learning models.

Your Lab Assistant conversations are saved in the App. With cloud backup on, they are also backed up to your account like the rest of your data, so they appear on your other devices. Deleting a conversation removes it from your device and from the backup.

3. How we use information

We use the information above to operate, maintain, secure, improve, and develop new features for the Service. In practice that includes:

  • Providing the App’s features and saving the data you log.
  • Backing up and restoring your data when you have cloud backup enabled.
  • Personalizing the App, and understanding how features are used — and who finds PeptideLab useful — so we can fix problems and build new ones (using the consent-gated analytics described above).
  • Finding and fixing technical problems, investigating problems you report to us, and making the App easier to use, with the consent-gated analytics and diagnostics described above.
  • Managing your subscription and account, and responding to your support requests.
  • Keeping the Service secure, preventing abuse, and meeting our legal obligations.
  • Producing de-identified, aggregate statistics. Where we ever surface community or aggregate insights, that data is de-identified.

We do not sell your personal data. We do not track you across other companies’ apps or websites for advertising, and we do not use an advertising identifier (Apple’s IDFA or Android’s advertising ID). We do measure our own ads, with your permission: see “Meta” in Section 5.

4. Legal bases (EU / UK / Switzerland)

If you are in the EEA, the UK, or Switzerland, we process your personal data under the following legal bases:

  • Contract: to provide the account, backup, and subscription features you ask for.
  • Consent: for analytics and diagnostics (which you turn on at the first-launch consent screen and can turn off at any time in Settings), for Apple Health access, and when you choose to use an optional AI-assisted feature. Health data is a special category of data, and we process it only with your explicit consent. You can withdraw consent at any time.
  • Legitimate interests: to secure the Service, prevent abuse, and improve and develop the product — balanced against your rights.
  • Legal obligation: to comply with applicable law.

5. How we share information

We share information only in the limited circumstances below.

  • Service providers (processors) who run the Service on our behalf, under agreements that limit them to that purpose:
    • Supabase — database, authentication, and cloud storage hosting (your account and, if enabled, your backed-up data).
    • PostHog — consent-based product analytics and diagnostics, used to improve the App and investigate technical problems (the events and profile attributes described above).
    • RevenueCat — subscription management.
    • Meta (Facebook)— measuring our own advertising, only while App analytics & diagnostics is on. The App tells Meta that it was installed and opened, and RevenueCat tells Meta when a free trial starts and when a subscription begins or renews, with a random identifier Meta’s software creates on your phone, so we can see which of our ads lead to installs and subscriptions. Meta receives no health data, nothing you log, no name or email, and no advertising identifier. Turning the setting off stops it.
    • Anthropic— AI processing for the optional AI-assisted features, and only when you use one (see “AI-assisted features” in Section 2).
    • Slack— where our team reads and answers Live Chat, with your name and email so we know who we’re talking to.
    • Google — Google Analytics on the Site, which counts visits and the setup steps completed, never what you entered.
    • Apple — App Store payments and HealthKit.
  • Legal requirements: when we believe in good faith that disclosure is required by law, legal process, or to protect rights, property, or safety.
  • Business transfers: in connection with a merger, acquisition, financing, or sale of assets, in which case any successor remains bound by this Policy.
  • With your direction: for anything else you ask us to do.

We do not sell your personal data, and we do not share it for cross-app or cross-site advertising.

6. Apple Health and Health Connect

Data from your phone’s health store — Apple Health on iOS, Health Connect on Android — gets specific, stronger commitments:

  • Access is read-only — we never write to Apple Health or Health Connect.
  • We read only the metric types you grant, and only those listed in Section 2. Declining one means it is never read.
  • We use it only to show it alongside your own logs and, if you allow it, to let Lab Assistant answer your questions with it. We never use it for advertising or marketing.
  • We never sell it and never share it with third parties, except the service providers above that we use to run the Service, such as our AI provider when you allow Lab Assistant to read it.
  • You can revoke access at any time: in the iOS Health app or Settings, in the Health Connect app on Android, or in the App’s own Settings.

7. Data retention

We keep your account and backed-up data for as long as your account is active. If you turn cloud backup off, we stop syncing new data; your most recent backup stays stored so that an accidental toggle never destroys anything. To remove the server copy entirely, delete your account in the app (or email us). If you delete your account, we delete your associated data. Deletions are processed within a reasonable period, after which residual copies may persist briefly in routine operational backups. Waitlist and other contact emails are kept until you unsubscribe or they’re no longer needed. We may retain limited records longer where required for legal, tax, security, or fraud-prevention purposes.

Anonymous accounts follow the same rules, with two housekeeping additions: an anonymous account that has never backed up any data is deleted after about 30 days, and an anonymous account whose backup shows no activity for about 180 days may be deleted together with its backed-up data. Adding an email address to your account exempts it from this anonymous-account cleanup.

Analytics eventsare kept by our analytics provider for up to 12 months. Turning analytics and diagnostics off stops new collection; it does not delete what was already sent. If you delete your account, we also delete your analytics profile and its events. To do that we keep your account’s identifier, and nothing else about it, until our analytics provider confirms the deletion: usually right away, and at most a few weeks if their service is unavailable. You can ask us to delete them sooner (see Section 8).

A web setup is kept with your account, including after the App has built it, so the same setup is never built twice. It is deleted when you delete your account.

8. Your choices and rights

You control your data in the App, under Settings → Privacy & Data, where you can:

  • Turn analytics and diagnostics off.
  • Disable cloud backup.
  • Export your data.
  • Delete individual protocols.
  • Delete everything in the period tracker (from its own settings).
  • Delete your account and its data.

Depending on where you live, you may also have rights to access, correct, delete, port, or restrict the use of your personal data, and to object to certain processing. To exercise these rights, email us at support@peptidelabapp.com. We’ll respond within the time required by applicable law.

EEA / UK / Switzerland (GDPR): in addition to the rights above, you may withdraw consent at any time and lodge a complaint with your local data protection authority.

California (CCPA/CPRA): you may request the categories and specific pieces of personal information we have collected, request deletion or correction, and limit the use of sensitive personal information. We do not sell or share personal information for cross-context behavioral advertising.

9. Security

We use industry-standard safeguards, including encryption in transit (TLS) and at rest, scoped access controls, and access scoped to your account. No system is perfectly secure, so we can’t guarantee absolute security. If you think your account has been compromised, contact us at support@peptidelabapp.com.

10. Children

PeptideLab is for adults. The Service is intended for people aged 18 and over, and we do not knowingly collect personal information from anyone under that age. If we learn we have, we will delete it.

11. International transfers

We and our service providers may process your information in countries other than where you live, including the United States. Where required, we rely on appropriate safeguards (such as Standard Contractual Clauses) for these transfers. This Service is governed by the laws of the State of Delaware, United States.

12. Changes to this Policy

We may update this Policy as the Service evolves. When we make material changes, we’ll update the “Last updated” date above and, where appropriate, notify you in the app or by email. Please check the date at the top for the current version.

13. Contact

Questions about this Policy or your data, or to exercise your rights — email support@peptidelabapp.com.