Privacy policy

Plain-language summary

Protocols GLP1+Peptide Tracker ("Protocols", the "App") is a personal logbook for supplement, peptide, GLP-1 and hormone wellness protocols and the activities around them. It is not a medical device and does not give medical advice.

• You enter your records; we store them for you. Protocols, items, dose and activity records, vials, check-ins, weight, bloodwork, side effects and injection sites are saved on your device and, when you are signed in, synced to your account so another device can restore them.
• Two categories are never uploaded to us: progress photos and your meal log (the foods you log and any meal plans you save). They stay on your phone (and in your own device backup).
• Nothing goes to an AI provider unless you say so. Helix (the assistant) and the meal scanner send data to OpenAI (through our server) only after you tap Allow in the App, and you can turn that off in Settings at any time. Helix looks up facts from your records only when you also switch Include my records on, and only what a question needs. Requests are sent with storage disabled and we do not keep them. Weights imported from Apple Health are never sent to OpenAI.
• Food search sends only your search words. When you search the food database, our server sends the words you typed (or a food's database id) to USDA FoodData Central, a U.S. government database, and nothing about you.
• No advertising, no analytics SDKs, no session replay, no crash-reporting service. Nothing in the App tracks you across other apps or websites.
• We do not sell your personal information or health data, and we do not share it for advertising. We do not use your data to train AI models.
• Reminders are local. They are scheduled on your phone by the operating system and never depend on our server.
• You can export everything and delete your account from inside the App, with or without an active subscription. Deletion removes your account and every synced record from our server and removes the copy on your device, including progress photos.

This summary is for convenience; the full policy below controls.

1. Who we are

Protocols is owned and operated by Kale Wayne Rogers ("we", "us", "our"), an individual doing business as Protocols, located in California, United States. We are the data controller for personal information processed under this policy. Contact: support@getprotocols.app, or Settings → Support → Report a problem or ask a question in the App.

This policy covers the Protocols iOS app, the website at https://getprotocols.app (marketing pages and these legal pages), and support communications with us. It is incorporated into our Terms of Service.

2. Medical disclaimer

Protocols provides tracking, organisation and general education only. It is not a healthcare provider, medical device, pharmacy or telehealth service, and it does not provide medical advice, diagnosis, treatment, prescriptions or dosing instructions. Everything the App shows — calculations, estimates, reminders, tips, research library entries, assistant replies and meal-scan estimates — is informational. Consult a qualified healthcare professional before any health-related decision.

3. Key terms

Personal information is information that identifies or could reasonably be linked to you or your household. Health data is information about your body, health or wellness that you enter, import, scan or generate in Protocols: protocols and the items in them, dose and activity records, vials, check-ins, weight and body composition, bloodwork, side effects, injection sites, meals, progress photos and notes. Consumer health data is health data protected by state laws such as Washington's My Health My Data Act and Nevada SB 370. Service provider / processor is a company that processes information on our instructions to provide the App.

4. Information we collect

4.1 Account information

When you create an account we collect your email address, first and last name, and a password (stored by our authentication provider as a salted hash; we never see it). If you use Sign in with Apple, we receive the identifier Apple assigns to you for our app, the name and email you choose to share (which may be Apple's private relay address), and a token we store so we can revoke Apple's link to your account when you delete it.

4.2 Onboarding and settings

The welcome steps ask for your first and last name and, optionally (each can be skipped), what brings you to the App, your height and current weight with their units (used to start the Progress chart), and how experienced you are (which sets how much the App explains). The answers are held on the device until your account exists and then become part of your settings (the weight becomes your first check-in). Settings such as theme, units, reminder preferences, whether protocol names appear in reminders and exports, the Daily Tip launch preference and your AI-sharing choice are stored with your account.

4.3 Records you enter

The core of the App. Depending on what you use:

4.4 Apple Health (optional)

Apple Health is used only after you connect it in Settings → Apple Health and grant permission in iOS. The App then reads weight, body fat percentage, lean body mass, waist circumference and sleep for the last 30 days and lists the readings on that screen. A reading is saved only when you choose it: tapping Use on a weight reading stores that weight in your check-in for that date, marked as coming from Apple Health. Once saved, an imported weight is part of your check-in and syncs to your account like a value you type. The other readings are shown on the screen and are not saved or uploaded. If you tick Also save this weight to Apple Health when logging a weight, the App writes that entry to Apple Health.

Estimated VO₂ max. Where your device provides the underlying fitness data, the App computes an estimated VO₂ max on your phone from your Apple Health readings and shows it as an informational estimate. The calculation runs on your device; the estimate is stored with your records like anything else you log.

Apple Health data is not sent to the AI provider. A weight imported from Apple Health is left out of the optional records summary described in Section 4.5; only weights you typed count towards it. We never read data types you did not authorise, never use Apple Health data for advertising, marketing or data mining, and never sell it or disclose it to third parties other than our hosting provider, which stores your synced check-ins for you. You can revoke access in the Health app at any time.

4.5 Helix (the assistant) and meal scanner (optional, consent required)

The first time you ask Helix a question or scan a meal photo, the App shows what will be sent and asks you to allow it. Until you tap Allow and continue, nothing is sent and the App falls back to a few fixed on-device answers and manual meal entry.

If you allow it:

• Helix. Your question, with up to the last twenty turns of the same conversation, is sent from the App to our server (a Supabase Edge Function) and from there to OpenAI to write the answer. You control which health data Helix sees: nothing from your records is sent unless you switch on Include my records on the Ask Helix screen, and even then Helix can ask the App only for the facts a question needs. The lookups run on your phone, over your own record only, and send back only compact facts: today's items (left, completed, skipped); your protocols and their items with schedule, route and the amount you entered; completion counts and percentages over up to 90 days; the recorded entries for one item over up to 60 days; activity sessions over up to 90 days; check-in counts, your typed weights and average mood, energy, focus and sleep scores over up to 90 days; lab results you entered with the reference range you typed; and daily meal totals and item names over up to 14 days. Weights imported from Apple Health are never included. You can leave item names out, in which case only the category is sent. Helix can also read the Research Library, which is public content bundled with the App. Helix cannot change anything in your account. The conversation is kept on your phone only (the last thirty turns) and is never stored on our server.
• Meal scanner. The photo you choose is resized to at most 1024 pixels, re-encoded as JPEG with location and camera metadata removed, and sent, together with the optional short note you can type about the meal, through our server to OpenAI, which returns a list of likely foods with typical nutrients per 100 g. The App then does the portion arithmetic itself. Every name, amount and nutrient is editable, and you can remove or add foods; nothing is saved to your device-only meal log until you tap Save meal. The result is an estimate and can be wrong.

We send requests to OpenAI with storage disabled (store: false). We do not keep your questions, the facts Helix looks up, or the photos on our server. For each call we log only your user ID, the kind of call (question or meal photo), the model name, token counts, estimated cost, whether the call succeeded and a timestamp, for quota enforcement and cost monitoring; this log is deleted with your account. We do not use your data to train AI models. What OpenAI itself does with data sent through its API — including any short retention for abuse monitoring — is governed by OpenAI's own terms and privacy policy (https://openai.com/policies), not by this policy; store: false is a setting on our request, and we cannot promise "zero retention" on their side.

You can turn sharing off at any time with Share with Helix in Settings → Privacy; the switch is off until you allow it. Turning it off stops anything further from being sent until you allow it again. The model is configurable on our server; at the time of writing it is OpenAI gpt-5.6-luna.

4.5a Food database search

When you add a food to a meal by searching, the App sends the words you typed to our server, which sends them, with our own access key, to USDA FoodData Central, a public database run by the U.S. Department of Agriculture, and returns the matching foods with their nutrients per 100 g and the serving sizes the database states. Choosing a food sends its database id the same way. Scanning a packaged food’s barcode reads the code with the camera on your phone (no picture is taken, kept or sent) and sends the number the same way. Nothing about you is sent: no account, name, email, device, records or meal history. We keep a count of searches per account for the daily limit, never the words. The food you log is saved to your device-only meal log with the nutrient values as logged, together with the database id and the serving you chose; it is never looked up again.

4.6 Subscription information

Purchases in the App are processed by the Apple App Store, and subscription state is read through RevenueCat. We receive plan, status (trial, active, cancelled, expired, grace period, refunded), period dates, store product identifier and store transaction identifiers. We never receive your card number. Your RevenueCat customer identifier is your Protocols user ID. We also store the billing events RevenueCat sends our server (they carry those identifiers) so that a repeated or out-of-order event is handled once; they are deleted with your account. The App keeps a copy of your current subscription status on your device so that it still opens when you are offline, until the paid period in that copy ends.

We may from time to time grant complimentary access to an account (for example for testing or support). A complimentary access record holds only your user ID, the access period and a note about why it was granted.

4.7 Referral codes and offer codes

Your account has a referral code. If you enter a friend's code, we record which code you entered, when, and whether the referral later qualified. When a referral qualifies, we record a free-month reward for each of you and assign each reward one App Store offer code from a batch we obtained from Apple. We store the code, the Apple offer it belongs to, when it was assigned to you, when it expires, and, when Apple reports that you redeemed it, when that happened. Redeeming a code is a transaction between you and Apple under Apple's terms. This information contains no health data, is visible only to you (your own rows) and to us, and is unlinked from you when you delete your account.

4.8 Shared protocol cards

Share My Protocol makes an image on your device from one protocol. It contains only what you choose on the preview screen: the protocol's name, the names of the items you leave ticked, a one-line schedule for each, amounts only if you switch Include amounts & doses on, your referral code, and a fixed disclaimer. You can also choose one of your own photos, or take one, as the card's background: that photo is used on your device to make the image, is not uploaded to us or kept by the App, and the location and camera details stored in the original photo file are not copied into the card. It never includes your notes, history, weight, labs, side effects, photos, supply, name or email. The image is not uploaded to us. Once you share it, whoever you send it to, and any app or social network you post it on, can see and keep what is on it, including the names of medications you chose to show; we cannot recall it.

4.9 Feature requests

If you suggest a feature, we store its title, description and category with your account, and we store which requests you upvote. What you write in a feature request is shown to everyone who uses the App, without your name, email address or any other account detail; please do not put personal or health information in it. Your votes are shown only as part of a count. You can remove your own request while it is still marked Submitted. If you delete your account, your votes are deleted and any requests you submitted stay on the list with nothing linking them to you; email us if you want one removed.

4.10 Support messages

If you contact us through Settings → Support or by email, we collect what you write and your account email, plus a line the App adds with its version and release channel and your operating system and its version, so we can reproduce issues. Please include only the health details needed to answer your question. Support conversations are visible only to you and to our support staff.

4.11 Device and technical information

Notifications. Reminders are scheduled on your device from your own records and do not pass through our server. A reminder shows the name of the item and of its protocol (you can switch names off in Settings → Reminders) and never an amount, a note or your supply. If you allow notifications, the App also stores a push address for your device (a token issued by Apple, with the platform and App version) with your account, so that we can later send you service notifications such as news about a feature you voted for. We do not send any today. It is not used for advertising or tracking, it is switched off when you sign out, and it is deleted with your account.

Motion. The supply screen reads the phone's tilt so the liquid drawn in a vial settles naturally as you move the phone. Nothing is recorded or transmitted.

Device identifier. The App stores a random device identifier it generates itself (not Apple's IDFA or IDFV) to record which device last wrote a synced record. Our server functions log the function name, a request identifier and an error message when something fails; they never log health content, questions or photos. Our hosting provider records network metadata such as IP address for routing, rate limiting and abuse prevention under its own terms.

4.12 What we do not collect

No location, contacts, calendar (the App can generate a calendar file for you to import, but does not read your calendar), browsing history, advertising identifiers, analytics events, crash reports, screen recordings or biometric data. The App contains no analytics, attribution, advertising, session-replay or crash-reporting SDK.

5. How we use information

We use information to:

• operate the App: create and authenticate your account, store and sync your records, schedule reminders on your device, show your history and charts;
• provide features you request: Helix, the meal scanner, food database search, exports and PDF summaries, Apple Health import, shared protocol cards, the referral programme;
• manage your subscription and check entitlement to paid features;
• answer support requests;
• keep the service secure, enforce quotas, prevent fraud and abuse, and debug failures;
• meet legal obligations and enforce our Terms.

We do not use your health data for advertising, marketing or profiling, do not sell it, and do not use it to train AI models.

Reviews and testimonials. If you post a public review or send us a testimonial, we may quote it in marketing with the name or initials you attached to it. We never use your private records, photos or messages in marketing. Email support@getprotocols.app to withdraw a testimonial.

6. Health data and consumer health data

Categories we collect are listed in Sections 4.3, 4.4 and 4.5 and come directly from you, from Apple Health if you connect it, or are computed by the App from what you logged or imported (adherence, run-out forecasts, estimated levels, estimated VO₂ max).

We share health data only with the service providers in Section 8 that need it to deliver a feature you used: our hosting provider stores it; OpenAI receives what you consent to send. We do not sell consumer health data, do not share it for targeted advertising, and do not process it for any purpose other than those in Section 5. If that ever changes we will update this policy first and obtain any consent or authorisation the law requires.

Washington and Nevada residents: our Consumer Health Data Privacy Policy is this Section 6 together with Sections 4, 8, 12 and 13, published at https://getprotocols.app/privacy#health-data.

7. Where information is stored and how it is protected

• On your device. Records are stored in the App's private sandbox. On iOS the App's files are protected with NSFileProtectionComplete, so they are encrypted whenever the device is locked. Your session token is encrypted with a key held in the iOS Keychain. Progress photos are stored in the App's document directory and never uploaded. Records and photos are included in your device backup (iCloud) under the device's own encryption so a restore does not lose them.
• On our server. Synced records are stored in a Supabase Postgres database in the United States, encrypted at rest and in transit. Every user-owned table is protected by row-level security so that only the authenticated user ID that owns a row can read or write it; our server functions derive identity from your verified session token and never from anything the App claims. Progress photos and meals are never stored on the server.
• What we cannot promise. The App is not end-to-end encrypted (we must be able to read synced rows to sync them), is not "on-device only" when you are signed in, and no system is perfectly secure. We are not HIPAA compliant and do not claim to be.

8. Who we share information with

We share information only as described here. Each provider is bound by its own terms and, where it acts for us, by a data-processing agreement.

We may also disclose information: to comply with law, a subpoena or a lawful request; to protect the rights, safety or property of users, Protocols or the public; to a successor in a merger, acquisition, financing or sale of assets, subject to this policy and any notice or consent the law requires; and with your direction (for example when you export a file and share it).

We do not share information with advertisers, data brokers or analytics companies, and we have no advertising partners. If we ever add a way to subscribe on our website, we will update this policy and name the payment processor before it goes live.

9. Your choices and controls

• AI sharing: Settings → Privacy → Share with Helix (off until you allow it); Include my records on the Ask Helix screen decides whether Helix may look up facts from your records (off each time you open the screen).
• Reminders and their content: Settings → Reminders; Protocol names in reminders decides whether the lock screen shows the item or only "Time for your dose".
• Protocol names in exports: Settings → Exports.
• Apple Health: Settings → Apple Health, and the Health app's Sources page.
• Camera and photos: asked only when you first use Photos, Meals or a card background; the App uses the system picker and never enumerates your library.
• Notifications: iOS Settings → Notifications → Protocols.
• Daily Tip on launch: Settings → Tracking.
• Export: Settings → Exports (CSV, PDF summary, calendar .ics, full JSON backup, which is not encrypted). Also reachable as Export my records on the subscription screen when you have no active subscription.
• Remove records from this device: Settings → Support → Remove records from this device. Frees this phone only; your account keeps every record and they come back on the next sync. Progress photos and the meal log are left untouched, because they exist only on the phone.
• Delete all records everywhere: Settings → Support → Delete all records everywhere (typed confirmation). Every record is deleted from your account and, on their next sync, from every device signed in to it. Your account, subscription and preferences stay, and so do progress photos and the meal log (delete them on their own screens).
• Delete account: Settings → Delete account, or Delete account on the subscription screen when you have no active subscription (Section 12).

10. Retention

11. Children

Protocols is for adults 18 and over. We do not knowingly collect information from anyone under 18. If you believe a minor has an account, email support@getprotocols.app and we will delete it.

12. Account deletion

You can delete your account from inside the App at any time: Settings → Delete account. You do not need to email us, and you do not need an active subscription — the subscription screen has its own Delete account link. When you confirm, our server does the following, in this order:

1. any subscription we bill directly (none exists at the time of writing) is cancelled first; if that fails, deletion stops there, before anything has been removed, and the App asks you to try again;
2. we ask RevenueCat to erase your customer record and, if you used Sign in with Apple, ask Apple to revoke the token linking your Apple ID to Protocols. A failure at either company is recorded and does not stop your deletion; we complete that step afterwards;
3. your synced protocols, items, dose and activity records, vials, check-ins, bloodwork, side effects and profile (settings) are purged from our database;
4. your assistant usage log and the stored RevenueCat billing events for your user ID are deleted;
5. your sign-in is deleted, which revokes all sessions and removes your subscription rows, referral rows, push addresses, votes and stored Apple token with it; late billing events for your old user ID are ignored so they cannot recreate anything;
6. on the device you deleted from, the account's whole stored copy is removed — records, settings, the meal log and progress photos including the image files — and reminders are cancelled.

Our server keeps a deletion record: the deleted user ID, when deletion was requested and completed, and the outcome of each step above (see Section 10). It contains none of your records. If deletion cannot finish, the App tells you so; try again or contact us. Deleting your account does not cancel an App Store subscription — cancel that in your Apple ID settings (the App links you there). Other devices where you were signed in lose their session when they next connect; a stale copy on such a device cannot be uploaded, because the account no longer exists, and is removed when the App is deleted from that device. Encrypted database backups age out within the window in Section 10.

13. Your rights (United States)

Depending on your state you may have the right to know what personal information we hold, to access it, to correct it, to delete it, to obtain a portable copy, to opt out of sale or sharing (we do none), to withdraw consent for consumer health data processing, and not to be discriminated against for exercising these rights. Most of these are available directly in the App (export, edit, delete). For anything else, email support@getprotocols.app; we will verify your request against your account email and respond within the time the applicable law requires (45 days under most state laws, extendable once). If we deny a request you may appeal by replying to our response.

Washington and Nevada residents (consumer health data): we do not sell consumer health data and have never done so; therefore no signed authorisation exists. You may exercise the rights above and may appeal a denial as described.

California residents: we do not "sell" or "share" personal information as defined by the CCPA/CPRA and have not done so in the preceding 12 months. Categories collected in the last 12 months: identifiers (name, email, user ID, device identifier, push address), health and other sensitive personal information you enter, commercial information (subscription state, referral rewards), and internet or network activity limited to server error metadata. Sources: you, Apple Health if connected, Apple and RevenueCat for purchase state. Purposes and recipients: Sections 5 and 8. We do not respond to browser "Do Not Track" signals because neither the App nor the website tracks you across other sites or services. To exercise CCPA rights, use the controls in the App or email support@getprotocols.app; you may designate an authorised agent, whom we will ask to prove their authority.

14. International users

Protocols is operated from the United States and our servers are in the United States. If you use the App from outside the US, your information is processed in the US. Where GDPR or UK GDPR applies, our legal bases are contract (providing the App you signed up for), consent (AI sharing, Apple Health, optional profile fields — withdrawable at any time), and legitimate interests (security, abuse prevention, support). You have the rights of access, rectification, erasure, restriction, portability and objection, and the right to lodge a complaint with your supervisory authority. Transfers to the US rely on standard contractual clauses with our processors.

15. Changes to this policy

We will post any changes here with a new effective date. For material changes — especially any change to what is shared with an AI provider or any new third party — we will notify you in the App or by email before the change takes effect and obtain consent where the law requires it.

16. Contact

Kale Wayne Rogers, doing business as Protocols 11506 Trinity Park Way, Bakersfield, CA 93311, United States support@getprotocols.app https://getprotocols.app In the App: Settings → Support → Report a problem or ask a question