PepLog Privacy Policy
Contents
PepLog is operated by True Avenue LLC. This policy covers our iOS app and trypeplog.com. Your personal logbook records are stored on your device, not synced to a PepLog cloud logbook. We separately process information to operate accounts and subscriptions, answer food lookups, understand app usage, attribute referrals, and measure website advertising, as explained below. Available features and data flows depend on your app version and the features you use.
What we collect
Your logbook records: what you log — doses, vials, weights, hydration, progress photos, notes, reminders, meals, and nutrition totals — is stored locally. We do not upload those records to our analytics or affiliate providers. Food lookup requests and feature-use events are separate from your saved records and are described below.
For your account: your email address (or the identity shared by Apple or Google sign-in) and a randomly generated account ID. Described in Your PepLog account below.
For subscriptions: your purchase state (which subscription, trial status, renewal dates), linked to your account ID so your access works on any device you sign into. Described in the Subscriptions section below.
Usage milestones: a small number of product milestones (like how far setup progressed), described in Usage milestones below. PostHog also receives screen views, time on screens, feature interactions, and action outcomes, associated with a guest identifier or your account ID.
Referrals: when you use a referral code or supported referral link, Insert Affiliate and RevenueCat process referral, installation/customer identifiers, and subscription information to attribute purchases and calculate commissions.
Food lookups: online searches send the search terms or product barcode to our Supabase-hosted food lookup service. They are not sent to PostHog or Insert Affiliate.
Website visits: when you visit trypeplog.com, our website sends TikTok limited technical and event information from your browser, such as pages viewed, IP address, browser and cookie identifiers and App Store button clicks, so we can measure advertising performance. This does not include your PepLog health records.
Your PepLog account
Creating a PepLog account — with Sign in with Apple, Google, or an emailed one-time code (no passwords) — stores your email address and a unique, randomly generated account ID with our authentication provider, Supabase. The account lets you sign in and have your PepLog subscription recognized across supported devices. The same account ID also connects the usage analytics and referral records described below. Your tracking entries are not synced to our servers. We never sell your email address or share it for advertising. Users who installed PepLog before accounts existed can keep using PepLog without one.
What stays on your device
The information you choose to enter — such as your name, weight entries, the compounds you log, vial details including any cost you record, doses, injection sites, progress photos, meals, nutrition goals, saved personal foods, and notes — is stored locally on your device using Apple’s on-device storage. It is under your control. Deleting the app removes its local logbook data; device backups and copies you export are separate.
Progress photos
Progress photos are taken with your camera and written to PepLog’s own private folder on your device. PepLog does not upload photo contents to our servers, analytics, or affiliate providers. You can choose to save or share a copy yourself.
PepLog asks for camera access the first time you take one. It does not browse your entire photo library. If you choose to import a progress or profile photo, Apple’s photo picker gives PepLog access to the item you select. Photos you take in PepLog are not added to your camera roll unless you explicitly save one.
You can delete any photo from inside the app at any time, and deleting the app removes its local copies. Copies saved elsewhere and device backups are controlled separately.
Costs you record
PepLog lets you record what a vial cost, and asks during setup for a rough monthly spend estimate. Both are optional. Both are stored only on your device, are used only to show you your own figures inside the app, and are never sent to us, to payment providers, or to anyone else. They are not connected to your PepLog account.
Food search and barcode lookup
Online food search sends the search text or scanned/entered product barcode to our food lookup service hosted on Supabase to retrieve nutrition information. A signed-in request also uses your account session for authentication. The service uses an account-derived identifier for request limits; guests share a request limit. Network services can also receive ordinary connection information, such as an IP address.
The barcode camera reads the product code on your device; camera images are not uploaded for this lookup. Your saved meal history, portions, nutrition totals, and personal goals are not included in the lookup request. Search text and barcode values are not included in PostHog analytics or affiliate attribution. Local saved foods and manual entry remain separate from online lookup.
Third parties
PepLog uses Supabase for authentication and website/backend services, RevenueCat for subscriptions and usage milestones, PostHog for product analytics, and Insert Affiliate for referral attribution. Apple handles in-app payments. Website hosting and email providers support the website and communications; Resend delivers partner-program emails. Meta and TikTok advertising measurement is described separately below.
We do not send your saved medication logs, vial records, weight, hydration, meal records, notes, or photo contents to PostHog, RevenueCat, Insert Affiliate, Meta, or TikTok. Feature-use metadata is different from the contents of your logbook: for example, an event can show that you opened a logging screen without including what you logged. PepLog does not collect Apple’s advertising identifier (IDFA). This does not mean that the services described here receive no identifiers or usage information.
Local records and cloud services
PepLog does not provide cloud synchronization of your personal logbook. Account information, subscription records, analytics, referral records, website information, and online food requests are processed by cloud services as described in this policy. They are distinct from your locally stored logbook and photos.
Device backups
If you use Apple’s standard device backup (iCloud Backup or an encrypted local backup), your PepLog data may be included in that backup, the same as other apps on your device. Those backups are governed by Apple’s privacy policy and your own device settings, not by us.
Notifications
PepLog can show you local reminders and encouragement — for example, hydration check-ins or reminders you set for your own logging schedule. These notifications are created and scheduled entirely on your device: PepLog does not use push notifications, no notification content or data is sent to us or anyone else, and nothing about them leaves your device. Notifications are optional — you can decline the permission when asked, or turn them off anytime in iOS Settings.
Subscriptions and purchases
PepLog Pro is an auto-renewing subscription purchased through Apple. Apple processes the payment; we never see your payment details.
To make your subscription work across reinstalls and devices, PepLog uses RevenueCat, a subscription-management service. RevenueCat receives your account ID (or an anonymous identifier if you have no account) and your purchase information (which subscription you bought, trial and renewal status). None of your logged health information is ever sent to RevenueCat. RevenueCat’s privacy policy is at revenuecat.com/privacy.
When you start a trial or subscribe, RevenueCat reports that purchase event to Meta so we can measure which ads bring people to PepLog. That report does not include your logbook entries or IDFA. It is separate from PostHog product analytics and affiliate commission reporting.
The Settings screen shows a “Support ID” — that subscription customer identifier — which you can include when you email support so we can look up your subscription and help. Sharing it reveals nothing about your logs.
Usage milestones
To understand where new users get stuck, PepLog records a small number of usage milestones — the furthest setup step, setup completion, paywall views, and a timestamp when a dose is first logged — associated with your RevenueCat customer identifier (anonymous before account linking, or linked to your account). They contain nothing you enter in the app: no doses, no compounds, no weights, no notes. These milestones are separate from PostHog collection and its saved opt-out preference.
Product analytics (PostHog)
We use PostHog to understand which features people use, where onboarding stops, and where interactions fail, so we can improve PepLog. Events include screen views and time spent on screens, app foreground/background activity, navigation and button interactions, onboarding progress and completion, successful sign-in, paywall views, and purchase/restore outcomes. Macro logging and barcode/referral events report outcomes such as saved, removed, applied, skipped, invalid, or failed.
These events contain predefined screen/action labels, timestamps, elapsed time, limited option values, app/SDK version information, session identifiers, and test/production markers. They do not contain typed text, food searches, barcode values, referral codes, medication or meal names, amounts, weight values, notes, photo contents, email addresses, phone numbers, or passwords. Checkout outcomes are app events, not verified revenue or commission reports.
Before sign-in, events use a generated guest identifier stored on the device. When you sign in, we link that guest history to your Supabase account ID, so onboarding and later usage can be understood as one journey. This is account-linked, pseudonymous analytics, not fully anonymous data. The same account ID can connect usage across devices. Signing out or switching accounts starts a separate analytics identity instead of joining two accounts together.
We do not enable PostHog session recordings, screenshots, automatic capture of screen text, or keystroke recording. We remove device model, locale, and screen-size properties from events and disable IP-based geolocation. The event IP field is replaced with a placeholder, although PostHog still receives network connections and can see their source IP at the transport layer.
In app versions with this analytics integration, collection is enabled by default unless an existing saved analytics opt-out disables it. We preserve previously saved app/PostHog opt-outs. The current app does not offer a new analytics settings switch. An unset preference is not a record of explicit consent. To raise a privacy objection or request information or deletion, contact support@trypeplog.com.
Our PostHog project uses its United States hosting region. See PostHog’s privacy policy.
Affiliate referrals
If you enter a referral code, paste a supported PepLog referral link, or open a supported link in the app, we use Insert Affiliate and RevenueCat to associate the referral with subscription purchases and calculate affiliate commissions. Code validation sends the company identifier and referral code to Insert Affiliate. Its SDK also reports initialization and referral association, including a referral identifier with a random installation suffix, source, and timestamp.
RevenueCat stores referral attributes on the subscription customer. Its configured webhook can forward customer IDs/aliases, referral attributes and other subscriber attributes, product and transaction identifiers, purchase amounts/currency, trial/renewal/cancellation/ refund status, and event timestamps to Insert Affiliate. This connects the referral before and after account linking. It does not include your saved health or meal records.
Referrals are optional. You can skip the referral step or remove an applied code in the referral screen. Removal clears the local referral and requests removal of prospective RevenueCat referral attributes; it does not erase already delivered events, past commissions, or historical subscription attribution. Contact us for requests about those records.
The app does not enable Insert Affiliate’s device-matching or automatic clipboard-reading features. Pasting is initiated by you. A pre-install link click is not guaranteed to carry a code through installation; you may need to reopen the link or enter the code after installing.
Visiting an insertaffiliate.link page is separate from the app: Insert Affiliate can collect link-click and browser/network information, including IP address and approximate location, under its privacy policy and cookie policy. Disabling matching inside PepLog does not disable collection on that external website.
Website accounts and partner program
Website sign-in uses session cookies to keep you signed in. Our website referral routes can record a referral click, campaign parameters and landing-page URL, and store a first-party referral cookie for up to 30 days. A qualifying website signup can connect that click to the account for attribution. This is separate from an Insert Affiliate link or the app’s optional referral screen.
If you apply to our partner program, we process the contact, country, social-profile, audience and application information you submit to review your application and communicate with you. Partner accounts also have referral, commission, payout and audit records. If you submit content-performance screenshots or a tax form through the partner portal, those files are uploaded to our Supabase storage for program review and tax administration. Tax forms can include a legal name, address and tax identification number; this is separate from the iOS app’s local logbook. Support messages contain whatever information you choose to send us; please do not send sensitive logbook information unless it is necessary for your request.
Advertising measurement
We advertise PepLog on third-party platforms, including Meta and TikTok. To understand which ads bring people to PepLog, we work with advertising and measurement partners that receive limited information about advertising performance.
Earlier versions of PepLog asked, on the subscription screen, whether you allowed the app to track you. That prompt has been removed. PepLog no longer accesses or shares your device’s advertising identifier with Meta or with anyone else.
When you visit trypeplog.com, the TikTok Pixel sends TikTok limited technical and event information from your browser, including pages viewed, IP address, browser and cookie identifiers. We use this to measure whether TikTok advertising led someone to visit our website. It does not receive your PepLog account information or any health or protocol records. TikTok’s privacy policy is at tiktok.com/legal/page/us/privacy-policy/en.
On our public landing page, we also send page-view and App Store button-click events through TikTok’s Events API. These reports may include your IP address, browser information, TikTok cookie identifier, and TikTok ad click identifier when available. Browser and server reports of the same action share an event identifier to avoid counting the action twice. Server reports exclude URL query strings, form contents, email addresses, account identifiers, and health records. An App Store button click does not tell us whether you installed the app or made a purchase.
What is never shared for advertising: your logged doses, vials, injection sites, notes, weight, hydration entries, or other sensitive user-entered health and protocol records. These remain within PepLog and are not sent to advertising partners.
Subscription and purchase lifecycle events are sent to Meta by RevenueCat, our subscription provider, on our behalf to measure advertising performance. These events do not include the sensitive health and protocol records described above, and they do not include your device’s advertising identifier.
Deleting your account
You can permanently delete your PepLog account in two places: in the app (Settings → PepLog Account → Delete Account), or on the web at trypeplog.com (Account menu → Settings → Delete account). You do not need to install the app to delete an account you created on the website. Either route does the same thing. Deletion removes the authentication identity, including its email and sign-in provider connections. It does not automatically remove separate support correspondence, partner applications or tax files. Business records such as attribution, subscription events, commissions, payouts and audit records can remain under a pseudonymous account identifier. Removing the sign-in identity does not necessarily make all retained records anonymous or automatically erase records held by PostHog, RevenueCat, or Insert Affiliate. Requests concerning those records can be sent to us at the address below. Entries on your device remain under your control; account deletion is not the same as deleting the local logbook.
Deleting an account or the app does not cancel an Apple subscription. Manage or cancel that subscription in your Apple account’s subscription settings.
Retention and privacy requests
Local records remain until you remove them or delete the app; exported copies and device backups have separate lifetimes. Account information supports your account until deletion. Subscription, referral, commission and audit records may need to be retained for payment reconciliation, refunds, disputes, fraud prevention, and legal or accounting obligations. Analytics and service records have separate retention and deletion settings; deleting the app does not delete previously transmitted events.
Contact support@trypeplog.com to request details about records associated with you or their retention, access, correction, or deletion. Depending on where you live, you may also have rights to a portable copy, restriction of processing, objection to certain processing, withdrawal of consent where processing relies on it, and a complaint to your local data-protection authority. We may need to verify your identity and consider applicable exceptions before fulfilling a request. A generated identifier is still personal data when it can be linked to you.
Processing locations and security
Our service providers may process information outside your state or country, including in the United States. In particular, the PostHog project used by PepLog is hosted in the United States. Provider arrangements and applicable data-protection requirements govern that processing; a hosting location is not a guarantee of legal compliance.
The app uses encrypted HTTPS connections for these online services and keeps local logbook files within its app storage. No storage or transmission method is completely secure. Protect your device and sign-in accounts, and contact us if you suspect unauthorized access.
Children
PepLog is intended for adults aged 18 and older and is not directed to children.
Medical disclaimer
PepLog is a personal logging and measurement tool. It does not provide medical advice, dosing recommendations, or treatment guidance, and it does not recommend or endorse any substance. Always consult a qualified healthcare provider before starting, stopping, or changing any regimen.
Changes to this policy
If this policy changes, we will update the date at the top of this page.
Contact
Questions about this policy can be sent to support@trypeplog.com.