Privacy Policy
Effective November 6, 2026
This policy describes native Swift version 0.8.0 and later on iPhone and iPad, and the Android app from version 0.9.0, when installed; it does not announce availability in any store. Where Android differs, see Android app (Google Play). If you use version 0.7.0 or earlier, see the earlier-version policies below.
1. Who we are
PepProtocol, formerly DoDose, is operated by Evergoods Holdings LLC. We provide personal record keeping for protocols, dose history, nutrition, water, activity and workouts, symptoms, photos and progress. This section describes the native Swift app, version 0.8.0, and the related account, optional cloud sync and optional AI services. Contact [email protected] for support and privacy requests.
2. Your records and optional permissions
The records you enter, saved photos, notes and assistant conversations are stored on your device. Basic manual tracking can be used as a guest. Signing in does not upload your records by itself. If you have Premium and turn on cloud sync, a copy is also stored with your account, as described in Cloud sync (Premium) below. You can export a supported backup and choose where to save it; anyone with access to that file may be able to read its contents. Keep your device and exported files secure.
Camera access is optional, and the system photo picker lets you select particular images. Photos you add in the app are saved as resized copies without location metadata. Saving a photo does not itself send it for AI analysis. Notifications use the reminder preferences and schedule times you choose and require iOS permission. Optional dictation uses on-device speech recognition when supported; the app does not save or send the audio recording to our servers. You can type instead.
3. Apple Health
If you choose to connect Apple Health, Apple's permission sheet controls which supported categories the app may read. These can include body measurements, activity, nutrition, sleep, and heart and vital metrics. The app does not request reproductive health or clinical health records. Access is read-only: the app displays permitted Health information on your device and does not write data to Apple Health. It does not copy that Health information into your PepProtocol records, so it is not included in cloud sync or exported backups. It is not uploaded to our account or sync service, billing services or AI providers. You can change permissions in Apple Health or iOS Settings. We do not use Apple Health information for advertising or tracking.
4. Sign in with Apple and account services
Optional Sign in with Apple uses Apple and our Convex-hosted account service to authenticate you. We process Apple's app-specific account identifier, an internal account ID and session/security information. The native sign-in flow does not ask for your name or email address. We securely retain encrypted Apple authorization material so we can revoke the connection when you delete your account. The account's internal ID is also used to associate and restore eligible Premium access through RevenueCat, including eligibility for cloud sync. Signing in does not by itself upload your tracking records; cloud sync is a separate Premium choice.
5. Cloud sync (Premium)
Cloud sync is optional and stays off unless you turn it on. It requires Sign in with Apple, or Sign in with Google on Android, and active Premium access. When it is on, the app stores a copy of your PepProtocol records with your account and keeps your signed-in devices up to date. This includes protocols, peptide and medication dose records, notes, nutrition and saved meals, water, weight, body measurements, symptoms, workout plans and logged workouts, assistant conversations saved in the app, AI results you chose to save, your profile answers such as goals, age, height, biological sex and weight targets, and app settings. It also includes blood work results and attached documents, and the progress, meal, saved-meal and note photos you add. When you turn on cloud sync on a device, the records already on it are copied to your account; if your account already has records from another device, you choose what to copy. Cloud sync does not upload Apple Health information, dictation audio (which the app does not save), a workout that is still in progress, or certain display preferences kept only on the device.
Synced records and photos are stored with Convex, our database and hosting provider, in its US East (Northern Virginia) region. They travel over encrypted HTTPS connections and are tied to your account through your signed-in session; our service does not let one account read another account's records. Photos are encrypted by our service with AES-256-GCM before they are written to storage, and they are never given a public link. Other synced records are stored in our database as structured data and are not separately encrypted by the app before upload. Because we manage the encryption keys, cloud sync is not end-to-end encrypted: our service decrypts your photos to return them to your signed-in devices.
We use synced records only to store them and sync them to your signed-in devices. We do not use them for advertising or tracking, do not share them with Meta or other advertising partners, and do not send them to AI providers. AI features send only the content you choose to share, as described in Optional AI processing. Convex processes this data on our behalf as a service provider.
Cloud sync is not a backup service. We do not currently keep separate backups of the cloud database, so a service failure could cause synced data to be lost. If you change the same record on more than one device while offline, the app keeps conflicting versions for you to review where it can, but we cannot guarantee that every offline change will combine as you expect. Keep exporting backups of records you want to preserve.
Turning off cloud sync, signing out or losing Premium stops future syncing from that device; records already on the device stay there. If Premium ends, syncing pauses until Premium is active again. None of these actions deletes your cloud copy. It remains stored until you delete your account; we do not currently delete cloud copies automatically after Premium ends or after a period of inactivity. When you delete a record or photo while syncing, it is marked deleted in your synced records and removed from your other signed-in devices when they next sync. Earlier versions of synced records remain in your account's sync history, and encrypted photo files remain in storage, until you delete your account. To remove your cloud copy entirely, use Delete account, described in Retention, deletion and your choices.
6. Optional AI processing
AI features require your sharing permission and eligible Premium access. When you use them, selected content is sent to our service providers and OpenAI for processing: photo analysis uses our Railway-hosted gateway, and the assistant uses our Convex-hosted service. Meal-photo analysis sends a resized copy of your selected image and the selected meal category to estimate food and nutrition. Progress-photo analysis sends the selected image, and an earlier comparison image if you choose one, to describe visible photographic differences. It is not a medical assessment and does not estimate body fat, diagnose conditions or determine treatment effects. Image metadata is removed from the sharing copy, but the visible picture may still identify you.
The assistant sends your prompt and, for chat or logging, up to eight recent messages from the selected conversation. Research/community searches do not send that conversation history. These features do not automatically send your complete stored health history or Apple Health records. Text you choose to share may nevertheless contain health or other sensitive information. Requests also contain technical information and a persistent installation identifier used for request limits and service operation.
Our gateway and assistant service are designed not to save prompts, photos or replies in an application database and requests that OpenAI not store responses for later retrieval. Conversations and AI results that you keep in the app are part of your records; if cloud sync is on, they are stored with your account like your other synced records. This is not a promise of zero retention by hosting or AI providers. Provider security, abuse-monitoring and legal retention may still apply under their policies. Review OpenAI's API data controls and Railway's privacy policy and Convex's privacy policy. Revoking AI sharing stops future requests; it does not recall a request already processed. Review AI results before saving them, and do not rely on them for medical decisions.
7. Purchases and service providers
Apple and RevenueCat process in-app purchase and subscription information, including product, transaction, entitlement and account identifiers. Where offered to eligible U.S. App Store users, web checkout opens your browser and uses RevenueCat and Stripe to process the purchase. Billing providers may request contact and payment details on their checkout pages. We use subscription information to provide access, including eligibility for cloud sync, restore eligible purchases, support customers and understand subscription performance. Subscription prices, renewal terms and any eligible offer are shown before purchase. The Swift app does not promise an automatic fourteen-day Premium preview.
Advertising measurement and tracking: the app asks for permission through Apple's App Tracking Transparency prompt. Only if you tap Allow, RevenueCat shares subscription events (such as a trial start, purchase or renewal, the product and price) together with device identifiers (such as the advertising identifier and IP address) with Meta to measure our advertising. If you ask the app not to track, these events are not sent to Meta. You can change this at any time in iOS Settings, Privacy & Security, Tracking. Health information, tracking records, photos and AI conversations, including anything stored through cloud sync, are never shared for advertising.
This Swift release does not embed the old app's PostHog, TikTok or Sentry SDKs. Service providers may retain technical request, security and operational logs. We do not sell your personal records or use your health or tracking records for targeted advertising. Support messages contain the address and information you choose to send; avoid attaching unnecessary medical records.
8. Retention, deletion and your choices
Local records remain on each device until you remove them or erase the app's data. Cloud sync copies remain until you delete your account, as described in Cloud sync (Premium). Temporary sync position markers, which contain no record content, expire after seven days and are removed automatically. For a signed-in account, use Delete account in Settings to request deletion of the server account, including its synced records, sync history and photos, and to revoke its Apple connection. Deletion blocks account access immediately, then removes this data in stages and retries automatically if Apple or another service is temporarily unavailable. The deletion flow reports completion after its server process finishes; it may require signing in again first. A minimal status receipt is retained so an interrupted deletion can report its outcome without retaining the deleted account identity. In rare cases, a photo upload interrupted at a particular moment can leave an encrypted file that is not linked to any account; account deletion cannot yet identify these files, and we are working to remove them.
Deleting the account does not automatically erase records stored on your devices, including account copies on other signed-in devices and guest records, copies you exported, separate device backups, or billing records held by Apple, RevenueCat or Stripe. You can remove an account copy from a device in Settings, under Local account copies. Account deletion does not cancel a subscription; cancel through the provider that billed you. Provider billing, security, fraud-prevention or legally required records may remain under separate retention requirements. Contact support for requests about information held outside the account-deletion flow. Depending on your location, you may have rights to access, correct, export or delete information, or object to certain processing.
We use encrypted connections, access controls, encryption of synced photos and device security facilities, but no system can guarantee absolute security. Our providers may process data in the United States or other countries. We will update the policy when practices change.
9. Android app (Google Play)
The sections above also apply to the Android app, except as described here. On Android, permissions use Android's prompts, and references to Apple, iOS and App Tracking Transparency apply to iPhone and iPad only.
Sign in with Google. Optional Sign in with Google uses Google and our Convex-hosted account service to authenticate you. Google sends the app a signed token that may contain your name, email address and profile picture link. Our service verifies the token and keeps only Google's account identifier, an internal account ID and session/security information; it does not save your name, email address or picture. We hold no Google authorization to revoke when you delete your account. You can remove the connection in your Google Account.
Health Connect. If you choose to connect Health Connect, its permission screen controls which categories the app may read: weight, height, body fat, lean body mass, steps, active calories, hydration, nutrition, heart rate, resting heart rate, heart rate variability, blood oxygen, respiratory rate, blood glucose, blood pressure, sleep and exercise. Access is read-only: the app shows permitted values on its Health Connect screen while you have it open and does not write to Health Connect. It keeps only your list of chosen categories on the device. The values are not copied into your PepProtocol records, so they are not included in cloud sync or exported backups. They are not sent to our services, billing services or AI providers, and are not used for advertising. You can change or remove access at any time in Health Connect.
Location. The Android app does not request location permission. Gym arrival reminders, which use location on iPhone, are not available on Android.
Records, photos and backup. Your on-device records are stored in the app's private storage. Android's own device backup may include them when it is on, under your Google account's settings; sign-in credentials are excluded. The system photo picker lets you select particular images, and camera access is optional. Photos are saved as re-encoded copies without location metadata. Progress-photo analysis on Android sends only the selected image.
Purchases. Google Play and RevenueCat process in-app purchase and subscription information, including product, transaction, entitlement and account identifiers. RevenueCat assigns an anonymous identifier when the app starts and links it to your internal account ID if you sign in. Cancel subscriptions in your Google Play account. The Android app has no web checkout.
Advertising and analytics. The Android app contains no advertising SDK, does not use the Android advertising identifier and does not embed PostHog, Sentry, TikTok or Meta SDKs.
Advertising measurement. On Android, RevenueCat shares subscription purchase events (such as trial starts, purchases and renewals) with Meta to measure our advertising. These events are linked to RevenueCat's app user identifier, not to an advertising identifier. The Android app does not request the advertising identifier and has no App Tracking Transparency equivalent.
Deletion. Delete your account in the app under Settings, Account and cloud sync, or follow the steps on our account deletion page, which also lets you request deletion by email without the app.
Earlier versions: October 7, 2026 privacy policy (version 0.8.0)
Privacy Policy for version 0.8.0
Effective October 7, 2026
This policy describes native Swift version 0.8.0 when installed; it does not announce that version's App Store availability. If you use version 0.7.0 or earlier, see the earlier-version policies below.
1. Who we are
PepProtocol, formerly DoDose, is operated by Evergoods Holdings LLC. We provide personal record keeping for protocols, dose history, nutrition, water, activity and workouts, symptoms, photos and progress. This section describes the native Swift app, version 0.8.0, and the related account, optional cloud sync and optional AI services. Contact [email protected] for support and privacy requests.
2. Your records and optional permissions
The records you enter, saved photos, notes and assistant conversations are stored on your device. Basic manual tracking can be used as a guest. Signing in does not upload your records by itself. If you have Premium and turn on cloud sync, a copy is also stored with your account, as described in Cloud sync (Premium) below. You can export a supported backup and choose where to save it; anyone with access to that file may be able to read its contents. Keep your device and exported files secure.
Camera access is optional, and the system photo picker lets you select particular images. Photos you add in the app are saved as resized copies without location metadata. Saving a photo does not itself send it for AI analysis. Notifications use the reminder preferences and schedule times you choose and require iOS permission. Optional dictation uses on-device speech recognition when supported; the app does not save or send the audio recording to our servers. You can type instead.
3. Apple Health
If you choose to connect Apple Health, Apple's permission sheet controls which supported categories the app may read. These can include body measurements, activity, nutrition, sleep, and heart and vital metrics. The app does not request reproductive health or clinical health records. Access is read-only: the app displays permitted Health information on your device and does not write data to Apple Health. It does not copy that Health information into your PepProtocol records, so it is not included in cloud sync or exported backups. It is not uploaded to our account or sync service, billing services or AI providers. You can change permissions in Apple Health or iOS Settings. We do not use Apple Health information for advertising or tracking.
4. Sign in with Apple and account services
Optional Sign in with Apple uses Apple and our Convex-hosted account service to authenticate you. We process Apple's app-specific account identifier, an internal account ID and session/security information. The native sign-in flow does not ask for your name or email address. We securely retain encrypted Apple authorization material so we can revoke the connection when you delete your account. The account's internal ID is also used to associate and restore eligible Premium access through RevenueCat, including eligibility for cloud sync. Signing in does not by itself upload your tracking records; cloud sync is a separate Premium choice.
5. Cloud sync (Premium)
Cloud sync is optional and stays off unless you turn it on. It requires Sign in with Apple and active Premium access. When it is on, the app stores a copy of your PepProtocol records with your account and keeps your signed-in devices up to date. This includes protocols, peptide and medication dose records, notes, nutrition and saved meals, water, weight, body measurements, symptoms, workout plans and logged workouts, assistant conversations saved in the app, AI results you chose to save, your profile answers such as goals, age, height, biological sex and weight targets, and app settings. It also includes the progress, meal, saved-meal and note photos you add. When you turn on cloud sync on a device, the records already on it are copied to your account; if your account already has records from another device, you choose what to copy. Cloud sync does not upload Apple Health information, dictation audio (which the app does not save), a workout that is still in progress, or certain display preferences kept only on the device.
Synced records and photos are stored with Convex, our database and hosting provider, in its US East (Northern Virginia) region. They travel over encrypted HTTPS connections and are tied to your account through your signed-in session; our service does not let one account read another account's records. Photos are encrypted by our service with AES-256-GCM before they are written to storage, and they are never given a public link. Other synced records are stored in our database as structured data and are not separately encrypted by the app before upload. Because we manage the encryption keys, cloud sync is not end-to-end encrypted: our service decrypts your photos to return them to your signed-in devices.
We use synced records only to store them and sync them to your signed-in devices. We do not use them for advertising or tracking, do not share them with Meta or other advertising partners, and do not send them to AI providers. AI features send only the content you choose to share, as described in Optional AI processing. Convex processes this data on our behalf as a service provider.
Cloud sync is not a backup service. We do not currently keep separate backups of the cloud database, so a service failure could cause synced data to be lost. If you change the same record on more than one device while offline, the app keeps conflicting versions for you to review where it can, but we cannot guarantee that every offline change will combine as you expect. Keep exporting backups of records you want to preserve.
Turning off cloud sync, signing out or losing Premium stops future syncing from that device; records already on the device stay there. If Premium ends, syncing pauses until Premium is active again. None of these actions deletes your cloud copy. It remains stored until you delete your account; we do not currently delete cloud copies automatically after Premium ends or after a period of inactivity. When you delete a record or photo while syncing, it is marked deleted in your synced records and removed from your other signed-in devices when they next sync. Earlier versions of synced records remain in your account's sync history, and encrypted photo files remain in storage, until you delete your account. To remove your cloud copy entirely, use Delete account, described in Retention, deletion and your choices.
6. Optional AI processing
AI features require your sharing permission and eligible Premium access. When you use them, selected content is sent to our service providers and OpenAI for processing: photo analysis uses our Railway-hosted gateway, and the assistant uses our Convex-hosted service. Meal-photo analysis sends a resized copy of your selected image and the selected meal category to estimate food and nutrition. Progress-photo analysis sends the selected image, and an earlier comparison image if you choose one, to describe visible photographic differences. It is not a medical assessment and does not estimate body fat, diagnose conditions or determine treatment effects. Image metadata is removed from the sharing copy, but the visible picture may still identify you.
The assistant sends your prompt and, for chat or logging, up to eight recent messages from the selected conversation. Research/community searches do not send that conversation history. These features do not automatically send your complete stored health history or Apple Health records. Text you choose to share may nevertheless contain health or other sensitive information. Requests also contain technical information and a persistent installation identifier used for request limits and service operation.
Our gateway and assistant service are designed not to save prompts, photos or replies in an application database and requests that OpenAI not store responses for later retrieval. Conversations and AI results that you keep in the app are part of your records; if cloud sync is on, they are stored with your account like your other synced records. This is not a promise of zero retention by hosting or AI providers. Provider security, abuse-monitoring and legal retention may still apply under their policies. Review OpenAI's API data controls and Railway's privacy policy and Convex's privacy policy. Revoking AI sharing stops future requests; it does not recall a request already processed. Review AI results before saving them, and do not rely on them for medical decisions.
7. Purchases and service providers
Apple and RevenueCat process in-app purchase and subscription information, including product, transaction, entitlement and account identifiers. Where offered to eligible U.S. App Store users, web checkout opens your browser and uses RevenueCat and Stripe to process the purchase. Billing providers may request contact and payment details on their checkout pages. We use subscription information to provide access, including eligibility for cloud sync, restore eligible purchases, support customers and understand subscription performance. Subscription prices, renewal terms and any eligible offer are shown before purchase. The Swift app does not promise an automatic fourteen-day Premium preview.
Advertising measurement and tracking: the app asks for permission through Apple's App Tracking Transparency prompt. Only if you tap Allow, RevenueCat shares subscription events (such as a trial start, purchase or renewal, the product and price) together with device identifiers (such as the advertising identifier and IP address) with Meta to measure our advertising. If you ask the app not to track, these events are not sent to Meta. You can change this at any time in iOS Settings, Privacy & Security, Tracking. Health information, tracking records, photos and AI conversations, including anything stored through cloud sync, are never shared for advertising.
This Swift release does not embed the old app's PostHog, TikTok or Sentry SDKs. Service providers may retain technical request, security and operational logs. We do not sell your personal records or use your health or tracking records for targeted advertising. Support messages contain the address and information you choose to send; avoid attaching unnecessary medical records.
8. Retention, deletion and your choices
Local records remain on each device until you remove them or erase the app's data. Cloud sync copies remain until you delete your account, as described in Cloud sync (Premium). Temporary sync position markers, which contain no record content, expire after seven days and are removed automatically. For a signed-in account, use Delete account in Settings to request deletion of the server account, including its synced records, sync history and photos, and to revoke its Apple connection. Deletion blocks account access immediately, then removes this data in stages and retries automatically if Apple or another service is temporarily unavailable. The deletion flow reports completion after its server process finishes; it may require signing in again first. A minimal status receipt is retained so an interrupted deletion can report its outcome without retaining the deleted account identity. In rare cases, a photo upload interrupted at a particular moment can leave an encrypted file that is not linked to any account; account deletion cannot yet identify these files, and we are working to remove them.
Deleting the account does not automatically erase records stored on your devices, including account copies on other signed-in devices and guest records, copies you exported, separate device backups, or billing records held by Apple, RevenueCat or Stripe. You can remove an account copy from a device in Settings, under Local account copies. Account deletion does not cancel a subscription; cancel through the provider that billed you. Provider billing, security, fraud-prevention or legally required records may remain under separate retention requirements. Contact support for requests about information held outside the account-deletion flow. Depending on your location, you may have rights to access, correct, export or delete information, or object to certain processing.
We use encrypted connections, access controls, encryption of synced photos and device security facilities, but no system can guarantee absolute security. Our providers may process data in the United States or other countries. We will update the policy when practices change.
Earlier versions: October 1, 2026 privacy policy (version 0.7.0)
Privacy Policy for version 0.7.0
Effective October 1, 2026
This policy describes native Swift version 0.7.0 when installed; it does not announce that version's App Store availability. If you use an earlier version, see the earlier-version policy below.
1. Who we are
PepProtocol, formerly DoDose, is operated by Evergoods Holdings LLC. We provide personal record keeping for protocols, dose history, nutrition, water, activity, symptoms, photos and progress. This section describes the native Swift app, version 0.7.0, and the related account and optional AI services. Contact [email protected] for support and privacy requests.
2. Your records and optional permissions
The records you enter, saved photos, notes and assistant conversations are stored on your device. Basic manual tracking can be used as a guest. Signing in does not enable automatic cloud backup or restore of these tracking records in this version. You can export a supported backup and choose where to save it; anyone with access to that file may be able to read its contents. Keep your device and exported files secure.
Camera access is optional, and the system photo picker lets you select particular images. Saving a photo does not itself send it for AI analysis. Notifications use the reminder preferences and schedule times you choose and require iOS permission. Optional dictation uses on-device speech recognition when supported; the app does not save or send the audio recording to our servers. You can type instead.
3. Apple Health
If you choose to connect Apple Health, Apple's permission sheet controls which supported categories the app may read. These can include body measurements, activity, nutrition, sleep, and heart and vital metrics. The app does not request reproductive health or clinical health records. Access is read-only: the app displays permitted Health information on your device and does not write data to Apple Health. It does not automatically upload that Health information to our account backend, billing services or AI providers, or copy it into your manually entered logs. You can change permissions in Apple Health or iOS Settings. We do not use Apple Health information for advertising or tracking.
4. Sign in with Apple and account services
Optional Sign in with Apple uses Apple and our Convex-hosted account service to authenticate you. We process Apple's app-specific account identifier, an internal account ID and session/security information. The native sign-in flow does not ask for your name or email address. We securely retain encrypted Apple authorization material so we can revoke the connection when you delete your account. The account's internal ID is also used to associate and restore eligible Premium access through RevenueCat. This does not turn your on-device tracking history into an automatically synchronized account backup.
5. Optional AI processing
AI features require your sharing permission and eligible Premium access. When you use them, selected content is sent to our service providers and OpenAI for processing: photo analysis uses our Railway-hosted gateway, and the assistant uses our Convex-hosted service. Meal-photo analysis sends a resized copy of your selected image and the selected meal category to estimate food and nutrition. Progress-photo analysis sends the selected image, and an earlier comparison image if you choose one, to describe visible photographic differences. It is not a medical assessment and does not estimate body fat, diagnose conditions or determine treatment effects. Image metadata is removed from the sharing copy, but the visible picture may still identify you.
The assistant sends your prompt and, for chat or logging, up to eight recent messages from the selected conversation. Research/community searches do not send that conversation history. These features do not automatically send your complete stored health history or Apple Health records. Text you choose to share may nevertheless contain health or other sensitive information. Requests also contain technical information and a persistent installation identifier used for request limits and service operation.
Our gateway and assistant service are designed not to save prompts, photos or replies in an application database and requests that OpenAI not store responses for later retrieval. This is not a promise of zero retention by hosting or AI providers. Provider security, abuse-monitoring and legal retention may still apply under their policies. Review OpenAI's API data controls and Railway's privacy policy and Convex's privacy policy. Revoking AI sharing stops future requests; it does not recall a request already processed. Review AI results before saving them, and do not rely on them for medical decisions.
6. Purchases and service providers
Apple and RevenueCat process in-app purchase and subscription information, including product, transaction, entitlement and account identifiers. Where offered to eligible U.S. App Store users, web checkout opens your browser and uses RevenueCat and Stripe to process the purchase. Billing providers may request contact and payment details on their checkout pages. We use subscription information to provide access, restore eligible purchases, support customers and understand subscription performance. Subscription prices, renewal terms and any eligible offer are shown before purchase. The Swift app does not promise an automatic fourteen-day Premium preview.
Advertising measurement and tracking: the app asks for permission through Apple's App Tracking Transparency prompt. Only if you tap Allow, RevenueCat shares subscription events (such as a trial start, purchase or renewal, the product and price) together with device identifiers (such as the advertising identifier and IP address) with Meta to measure our advertising. If you ask the app not to track, these events are not sent to Meta. You can change this at any time in iOS Settings, Privacy & Security, Tracking. Health information, tracking records, photos and AI conversations are never shared for advertising.
This Swift release does not embed the old app's PostHog, TikTok or Sentry SDKs. Service providers may retain technical request, security and operational logs. We do not sell your personal records or use your health or tracking records for targeted advertising. Support messages contain the address and information you choose to send; avoid attaching unnecessary medical records.
7. Retention, deletion and your choices
Local records remain until you remove them or erase the app's data. For a signed-in account, use Delete account in Settings to request deletion of the server account and revoke its Apple connection. The deletion flow reports completion after its server process finishes; it may require signing in again first. A minimal status receipt is retained so an interrupted deletion can report its outcome without retaining the deleted account identity.
Deleting the account does not automatically erase guest records on your device, copies you exported, separate device backups, or billing records held by Apple, RevenueCat or Stripe. It does not cancel a subscription; cancel through the provider that billed you. Provider billing, security, fraud-prevention or legally required records may remain under separate retention requirements. Contact support for requests about information held outside the account-deletion flow. Depending on your location, you may have rights to access, correct, export or delete information, or object to certain processing.
We use encrypted connections, access controls and device security facilities, but no system can guarantee absolute security. Our providers may process data in the United States or other countries. We will update the policy when practices change.
Earlier versions: September 14, 2026 privacy policy
Privacy Policy for earlier versions
Effective September 14, 2026
1. Who we are
PepProtocol, formerly DoDose, is operated by Evergoods Holdings. It is a record-keeping app for protocols, shots, nutrition, hydration, symptoms, and progress. This policy covers the app and pepprotocol.halfwind.studio.
You can use the app without creating a PepProtocol account or providing an email address. Basic tracking stays free. Optional paid features and AI do not change ownership of your records.
2. Your records and device permissions
The app stores the records you enter locally on your device. These may include compound names, amounts, schedules, injection sites, inventory, symptoms, food and protein, water, activity, weight, measurements, photos, notes, private templates, and saved assistant conversations.
Camera and photo-library access are optional. A selected photo is saved or sent only for the feature you choose. Notifications use the reminders you configure. You can manage these permissions in iOS Settings.
If you enable Apple Health access, the app reads or writes the data types you authorize for tracking and progress features. Health data is not used for advertising. Manage or revoke access in the Health app. Imported data may remain in your local records until you remove it.
3. Optional AI food estimates and assistant
Before the first AI request for each feature, the app asks for permission to share data with our gateway hosted by Railway and with OpenAI, which generates the response. You can decline and continue manual tracking. You can change the AI-sharing choice in the app; changing it stops future requests and does not recall requests already processed.
- Food estimates: the selected food photo, description, meal category, and notes are sent to estimate food items and nutrition.
- Assistant: your prompt, optional attached photo, up to 12 recent messages, and the relevant tracking context shown by the feature are sent to produce a contextual reply.
- Request metadata: the gateway and providers also process network and technical information, including IP addresses, request times, and an app installation identifier used to limit requests.
Photos, prompts, conversation text, and health context may identify you or contain sensitive information. These inputs are not automatically anonymized before they are sent.
AI responses can be inaccurate. Review and edit estimates before saving. The assistant is not a medical provider and does not determine a treatment plan.
Our gateway does not intentionally save AI prompts, photos, or replies in its database. It requests that OpenAI not store responses for later retrieval. This does not mean zero retention: OpenAI may keep API content in abuse-monitoring logs, normally for up to 30 days, with legal and safety exceptions.
See OpenAI API data controls, OpenAI Privacy Policy, and Railway Privacy Policy.
4. Backups, exports, and sharing
On supported Apple devices, iCloud sync can store an app snapshot in your private CloudKit database when available and enabled. You can create a manual backup or data export and choose where to save or share it. A clinician PDF is generated from the records you select; you choose its recipient through the share sheet.
5. Purchases and the free preview
Basic tracking is free. The 14-day Premium preview starts in the app without payment or automatic billing. Optional Premium subscriptions are purchased through Apple. Apple and RevenueCat process purchase receipts, product identifiers, subscription status, and a pseudonymous app-user or installation identifier to provide and restore access. We do not receive your full payment-card details.
See RevenueCat privacy information and Apple privacy information.
6. Analytics, advertising measurement, and diagnostics
The app uses PostHog for limited product usage information. On iOS, TikTok advertising measurement is enabled only after your App Tracking Transparency permission. Sentry helps diagnose errors using sanitized error types, app release information, and code locations.
The website is hosted as part of halfwind.studio, which processes technical request information to serve and secure pages. This website release does not load advertising pixels. We do not sell personal information or use user-entered health records for advertising targeting.
7. Support and other disclosures
If you contact support, we receive your email address and the information you choose to include. Please avoid sending medical details or complete backups unless needed for your request.
8. Retention, deletion, and your choices
Local records remain until you remove them or erase the app data. Deleting local data does not automatically remove separate iCloud/device backups, exported files, records written to Apple Health, or information previously sent to a provider.
Depending on your location, you may request access, correction, deletion, or a copy of personal information we hold, or object to certain processing. Contact [email protected].
Deleting the app or its records does not cancel an Apple subscription. Manage subscriptions in your Apple account settings.
9. Security, international processing, and updates
We use encrypted connections and access controls to protect data in transit and limit access to service systems. Providers may process information in the United States or other countries with different privacy laws.
For privacy requests or product help, visit Support or email [email protected].