PeptideUniv ("we", "our", or "us") operates the PeptideUniv application and website.
PeptideUniv works without an account. If you create one, the same records follow you between the iOS app, the Android app and peptideuniv.com. This policy describes both: what stays on the device when you are signed out, and what leaves it when you are signed in.
1. Without an account
Signed out, the app holds the following sensitive, health-adjacent research information only on your device:
- Saved research schedules, peptide or compound names, amounts, dates, and times
- Logged research events, optional notes, and optional site-rotation history
- Physical vial inventory, remaining quantities, reconstitution details, and inventory history
- Onboarding status, appearance settings, and local-reminder preferences
- We do not receive these records. Nothing is uploaded.
- The app contains no crash-reporting SDK, no advertising SDK and no attribution SDK. It does send anonymous product-usage events, described in sections 5a and 5b, which never include what you enter here.
- Local reminders are scheduled by the device operating system. Reminder permission and delivery are controlled by iOS or Android.
- Local app storage is sandboxed by the operating system but is not additionally encrypted by PeptideUniv.
2. With an account
An account is optional and every feature works without one. Creating one requires an email address and a password. Once you are signed in, the records in section 1 are copied to our servers so that your devices and the website show the same data. Specifically:
- Sign-in is handled by Supabase, which stores your email address, a hashed password, your account identifier and your session tokens.
- Your records — schedules, logged entries (amount, injection site, notes, times), site-rotation history, inventory (peptide, vial size, remaining quantity, lot number, supplier, expiry) and app preferences — are stored by us on Cloudflare infrastructure at sync.peptideuniv.com.
- A device identifier generated by the app is stored alongside them so that edits made on different devices can be reconciled and so that a lost device can be signed out.
Supabase and Cloudflare process this data on our instructions as service providers. We do not sell it, share it for advertising, or use it to build profiles. Signing out of a device removes the account's synced records from that device.
3. Subscriptions and payments
- Buying PeptideUniv Pro requires an account, so that access follows the account rather than a single device or browser.
- In the apps, purchases are made through the Apple App Store or Google Play. We never see your card details. RevenueCat receives your purchase history, your account identifier and device identifiers in order to tell the app whether a subscription is active.
- On the website, payment is handled by Stripe. Stripe holds the payment method; we store only a Stripe customer identifier, your email address, the subscription's status and its renewal date.
- Subscription status is the only thing shared between the stores and our servers. Your schedules, logs and inventory are never sent to Apple, Google, RevenueCat or Stripe.
4. User-initiated exports
- The app can generate a protocol-reference PDF in app cache.
- A PDF leaves the app only when you choose a destination using the operating-system share sheet.
- Copies saved to Files, email, cloud drives, messaging services, or other destinations are governed by your chosen destination and are not removed by deleting your PeptideUniv data.
5. Website data
Independently of any account, the website may process a locally generated browser identifier, email addresses you submit for results or billing support, web-push subscription information, and Stripe subscription or entitlement metadata. Website schedules and calculator results are held in your browser unless you sign in, at which point section 2 applies.
The website measures how it is used in three ways. Whether the first two run depends on where your device says you are, as section 5b explains.
- Google Analytics on every page of the website except this policy and the terms, disclaimer, support and account pages. It records page views and feature interactions along with the IP address, approximate location, device and browser your visit came from, and sets its own cookies (named
_ga). This is website analytics only. Nothing you enter into the app is sent to Google Analytics.
- Our own usage events, sent to our server on Cloudflare: what happened (a page or section was viewed, a calculator was opened or run, a button or upgrade prompt was clicked, a checkout was started or finished), the page, the page you came from and any campaign tags in the link, the browser identifier mentioned above, a per-visit identifier and your browser's user-agent. We keep a one-way hash of the IP address, not the address itself. When you use a calculator, the event says which calculator and which preset you picked, never the numbers you entered (vial amount, water or dose). It never carries your email address.
- Cloudflare Web Analytics. Cloudflare, which hosts the website, adds its own measurement script to the pages it serves. It counts visits and page views and measures how quickly pages load. It does not set cookies, it runs for every visitor, and the choice in section 5b does not switch it off.
5a. Usage data from the apps
So that we can see which parts of the app are used and where people get stuck, the iOS and Android apps send a small number of product-usage events to
PostHog (United States). This is separate from your records. In the EU, EEA, UK and Switzerland it is off until you allow it; elsewhere it is on by default and you can turn it off (section 5b).
- Anonymous. Events carry a random identifier created on the device at install (in the regions in section 5b, when you choose Allow). They do not carry your email address, your account identifier, or any advertising identifier, and PostHog is instructed not to build a profile from them. The app also tells PostHog not to record the IP address the events arrive from and not to work out a location from it.
- What is sent. The name of the thing that happened — the app opened, a schedule was saved, a dose was logged, a vial was added, an upgrade prompt was shown, a purchase was started or finished — along with which screen it came from, whether the account has Pro, how many active schedules it has, the app version and the platform.
- What is never sent. Peptide or compound names, amounts, doses, sites, notes, inventory contents, schedule identifiers, your email address or your account identifier. The app drops anything outside a fixed list before it leaves the device.
- Turning it off. Settings → Privacy & Local Data → Share anonymous usage data. Switching it off discards anything still waiting to be sent and stops any further sending on that device.
- There is no session recording, no automatic capture of taps or screens, and no advertising use.
5b. Where analytics ask first, and how to change your choice
If your device appears to be in the European Union, the European Economic Area (Iceland, Liechtenstein and Norway), the United Kingdom or Switzerland, Google Analytics, our own website usage events and the app's usage data are off until you allow them. Everywhere else they are on by default and you can turn them off. Cloudflare Web Analytics (section 5) is not affected by this choice.
- How we decide where you are. On your device, from the languages your browser or phone is set to and its time zone. We do not look up your location from your IP address and do not ask for location permission for this. If any one of those settings points to one of these regions, we ask first, so some people outside them are asked too.
- On the website, in those regions. On your first visit a banner asks “Help improve PeptideUniv?” with Allow and Decline. Until you choose Allow, Google Analytics is not loaded and our own usage events are not sent.
- On the website, elsewhere. Google Analytics and our own usage events run as described in section 5 unless you choose Decline.
- Changing it on the website. Use Cookie & analytics settings at the bottom of any page that uses Google Analytics, for example the home page. It reopens the same Allow / Decline choice. Choosing Decline after allowing switches Google Analytics off and removes its cookies from peptideuniv.com. Your choice is saved in this browser only, so another browser or device, or clearing this site's data, starts again from the default for your region.
- In the app, in those regions. The app asks once, “Help improve Pep U?”, with Allow and Not now. Until you choose Allow, no usage data is sent or kept on the device, not even the random identifier.
- In the app, elsewhere. Usage data is on until you turn it off.
- Changing it in the app. Settings → Privacy & Local Data → Share anonymous usage data, in any region.
6. Storage, transmission, and third parties
- Traffic to Supabase, sync.peptideuniv.com, Stripe and RevenueCat uses HTTPS/TLS. No internet transmission can be guaranteed risk-free.
- App updates are delivered over the air by Expo Application Services, which receives the request's IP address and app version as any content-delivery network does.
- Our service providers are Supabase (sign-in), Cloudflare (hosting, record storage and cookieless website analytics), Stripe (website payments), RevenueCat (store subscription state), Expo (app updates), Google Analytics (website analytics only), PostHog (anonymous app usage data) and our email provider. Each processes data under its own terms and on our instructions.
- We do not sell personal information. We disclose data only as needed to operate requested services, comply with law, protect rights and safety, or complete a business transfer subject to applicable law.
7. Cookies and browser storage
The website may use cookies or local storage for:
- Theme, browser/device identity, session, subscription-status caching, saved web schedules, and feature settings
- Security, checkout state, support, analytics, reminders, and user-requested backup/sync behavior
- Google Analytics cookies, only while Google Analytics is allowed to run (section 5b), and your analytics choice itself, kept in local storage
8. Deleting your data
- Delete your account — in the app, Settings → Account → Delete account; on the website, the account panel. It requires your password and a typed confirmation. It removes the account, its schedules, logged entries, site-rotation history and inventory from our servers, and removes the sign-in itself. This cannot be undone.
- Delete local data — Settings → Data Controls → Delete all local data removes PeptideUniv-owned records held on that device, cancels its pending PeptideUniv reminders, and returns the app to onboarding.
- Uninstalling the app normally removes its sandboxed local records, subject to operating-system behavior.
- Deleting your account stops a subscription bought on peptideuniv.com from renewing; you keep access for the period you have already paid for. A subscription bought in the App Store or Google Play must be cancelled there, because only the store can cancel it.
- Neither control can remove files you exported to another app or service.
- To delete your account and the data saved to it, see Delete your account.
- For anything else, or to request a copy of your data, contact support@peptideuniv.com. We may need information to locate and verify the applicable record.
9. Security
We use reasonable administrative and technical safeguards appropriate to the service. Passwords are stored hashed by Supabase and are never visible to us. Sensitive actions such as deleting an account require re-entering your password. Local app storage is not application-level encrypted, and no storage or transmission method is completely secure. We have not commissioned an independent security review.
10. Children
PeptideUniv is not designed for children. Do not provide personal information through the service if you are not legally permitted to do so in your location.
11. Changes
We may update this policy as product behavior, SDKs, or legal requirements change. The date above identifies the current version.
12. Contact