Consumer Health Data Privacy Policy

Overview

This Consumer Health Data Privacy Policy explains how the Peptrak developer handles consumer health data for Peptrak: GLP-1/Peptide Tracker.

Peptrak is local-first. Protocol records, HealthKit imports, dose logs, side effects, measurements, notes, reminders, exports, and backups are stored on your device by default.

The Peptrak developer does not receive on-device consumer health data by default unless you choose to export, share, restore, or send that information through Apple system tools, support, or another destination you control.

Consumer Health Data

Consumer health data means personal information that identifies or can reasonably be linked to your past, present, or future physical or mental health status.

For Peptrak, this may include protocol names, selected compounds, dose schedules, dose logs, skipped-dose decisions, sites, side-effect records, symptoms, severity, onset, duration, notes, weight, blood glucose, resting heart rate, height, biological sex, date of birth or age, goals, reminders, vial or supply details, pharmacy text, lot text, cost text, exports, and backup files.

Some of this information may be entered by you, some may be imported from Apple Health with your permission, and some may be created by the app as part of local tracking, reminders, estimates, exports, backups, or restore flows.

Sources

Peptrak collects or processes consumer health data from information you enter in the app, Apple Health data you permit the app to read, local app actions you take, local reminder settings, local exports or backups you create, backup files you choose to restore, and support communications you choose to send.

Peptrak does not receive consumer health data from Apple Health unless you grant permission and the app reads supported data types.

Purposes

Peptrak processes consumer health data to provide the features you request, including protocol logging, dose history, skipped-dose records, local reminders, side-effect logs, measurements, goals, trends, estimated peptide-level displays, compound tracking, vial or supply records, exports, backups, restore, deletion, and support.

Peptrak may also process limited support records to respond to your requests and limited legal records to comply with law, enforce terms, protect rights, or maintain app security.

Processing

On-device consumer health data is processed locally by the app and stored in the app's on-device database unless you choose to export, share, back up, restore, delete, or send it.

Exports and backups are written to temporary app files and passed to the native share or save sheet so you choose the destination.

Estimated levels, trends, side-effect patterns, adherence displays, and reminders are generated from local records and are not medical advice, diagnosis, treatment, prescribing, dosing guidance, lab measurements, or emergency support.

Disclosures

Peptrak does not sell consumer health data.

Peptrak does not use or disclose your on-device protocol logs, HealthKit data, dose logs, side effects, measurements, notes, exports, or backups to target ads.

Consumer health data may be disclosed when you choose to export, share, save, restore, or send records; when Apple platform services process HealthKit permissions, local notifications, or file sharing; when a support provider processes information you send; or when disclosure is required by law, legal process, or safety and security needs.

Third Parties and Affiliates

Apple may process HealthKit permissions, Apple Health data access, local notifications, App Store purchases, device-level privacy settings, Apple Search Ads or App Store advertising information, and system share or save destinations according to Apple's terms and privacy policies.

RevenueCat may process purchase identifiers, app user identifiers, product identifiers, subscription status, entitlement status, management URLs, and related transaction information to manage Pro access.

Vercel may process website hosting and aggregate website analytics information. Website analytics do not access on-device app health records.

No third party is permitted by Peptrak to collect on-device consumer health data over time and across different apps, websites, or online services through the Peptrak iPhone app.

Sale and Advertising

Peptrak does not sell consumer health data. Peptrak will not sell consumer health data unless it first provides legally required disclosures and obtains any separate authorization required by applicable law.

Peptrak may advertise through external platforms, including Apple Search Ads or similar campaign tools. Those platforms may process campaign, impression, click, account, device, region, or conversion information, but Peptrak does not provide on-device consumer health records to those platforms for ad targeting.

Review, Correct, and Delete

You can review, correct, export, and delete most consumer health data directly in the app through logging, editing, export, backup, restore, and delete controls.

Deleting local app data deletes the app's local copy on that device. It does not delete exported files, backups, copies saved to other services, Apple purchase records, RevenueCat entitlement records, support emails, or records held by a destination you selected.

For consumer health data controlled by the Peptrak developer outside your device, send a request to support@braign.io.

Your Rights

Depending on your location, you may have rights to confirm whether Peptrak collects, shares, or sells consumer health data about you; access consumer health data; request deletion; request correction; withdraw consent; request a list of third parties or affiliates with whom consumer health data was shared; or appeal a denied request.

To exercise rights for information controlled outside your device, contact support@braign.io. If your request is denied and applicable law gives you an appeal right, reply with Appeal in the subject line and explain what you want reviewed.

Changes

Peptrak may update this Consumer Health Data Privacy Policy as the app changes. Material changes should be posted before the affected feature is released where required.

The effective date of this policy is the last updated date shown on this page.