Peptide Vault

Apple Health

With your permission, Peptide Vault can read selected Apple Health data — for example body weight — to display it alongside your logs. Access is read-only: the app never writes anything to Apple Health.

Health data never leaves your device. It is not sent to our servers, to Coach, to any analytics or attribution service, or to any other third party. You can revoke access anytime in iOS Settings → Health → Data Access & Devices.

Coach (optional AI research assistant)

Coach is an optional Pro feature: a research-assistant chat. It only runs when you choose to use it. When you send a message, the text you typed is sent to our server, which forwards it to the OpenAI API to generate a reply.

By default, the message you type is the only thing sent. If you turn on the in-chat share toggle, the names of the compounds you track and a summary of your stack — which otherwise stay on your device — are included so answers can reference them. Your journal entries, notes, dose logs, and Apple Health data are never sent to Coach, with or without the toggle. You can turn the toggle off at any time.

We do not store your Coach messages on our server; they are processed only to generate the reply. OpenAI handles forwarded messages under its API data policy, which does not use API data to train its models by default. Coach requires no account: its requests carry a random per-install identifier used only for rate limiting, separate from your optional community profile.

Feedback you send us

Peptide Vault includes an optional feedback form, reachable from Settings → About Peptide Vault → Send feedback and from a one-time prompt after your fifth logged dose. It never sends anything on its own.

When you tap Send, the app transmits exactly four things: the note you wrote, the app's version number, a random identifier generated on this device so we can see that several notes came from the same install, and — only if you typed one into the optional field — an email address so we can reply. That random identifier is separate from the one used for analytics and cannot be joined to it; we convert it to a one-way hash on arrival and never store the original.

As with any request sent over the internet, our server also sees the IP address the note arrives from. It is used only to limit how many submissions one network can send, it is turned into a one-way hash before anything is written down, and it is never stored alongside your note.

Your dose logs, protocols, compounds, journal entries and Apple Health data are never included, with or without an email address. The server rejects any submission carrying a field outside that list.

Notes are stored in our database, hosted by Supabase, and are readable only by Jacob Teague. A copy may also be emailed to us through Resend and delivered to a Google mailbox. We keep notes for as long as they remain useful for improving the app, and delete them on request — email jacobteague50@gmail.com and, if you left an address, we can find and remove your note.

Optional community

Community is an optional space for adults aged 18 or older. Reading approved posts does not require a profile. To post, reply, report or block, explicitly accept the community rules and choose a public display name. The app creates a random credential in secure device storage; our server stores only its one-way hash, a random profile ID, your display name, rules acceptance and profile status. No email or billing identity is required or linked. There is no email-based recovery if the device credential is lost.

Posts and replies are stored for moderation. Pending and rejected submissions are visible only to their author and authorized moderators; approved text, display names and post dates are public to community readers. Reports and blocked-member relationships are private. If you separately accept the September 15, 2026 screening notice, only your submitted text may be sent to OpenAI for automated safety and community-rule checks. We do not include your display name, profile ID, credential, earlier conversation, private Coach chats, tracker records or purchase information. Clear posts may appear automatically; uncertain, flagged or unchecked posts wait for a moderator, including if the service is unavailable. Existing members and older app versions stay on human review until explicit screening consent. Automated checks can make mistakes and do not verify medical facts. Community does not automatically upload your protocols, cabinet, journal, Health data, photos or purchase history. Details you type into a post are part of the submitted text; avoid sensitive or identifying details.

Likes and replies create interaction and activity records. If you enable Community phone alerts, we store a random installation ID, its Expo push token, your Community profile reference and your likes/replies preferences. Expo and Apple or Google process delivery. Alerts use generic text and opaque conversation identifiers, without post text, member names, health records or purchase details. The community privacy notice describes retention, disabling alerts and deleting these records.

Threads expire after 30 days, and replies inherit the thread's expiry. Expired conversations are hidden immediately and removed by daily cleanup. You can remove your posts or delete your community profile in the app. Profile deletion revokes the credential, removes the name and block relationships, and replaces its posts with a deleted-member placeholder. Restricted moderation evidence may survive public deletion for up to 30 days from first capture, with removal at the next daily cleanup. Deleting the app alone does not delete community content; secure device storage may survive reinstalling.

Analytics and attribution

Peptide Vault uses PostHog and AppsFlyer to understand how the app is used and which marketing campaigns lead to installs. These tools receive a device identifier, a random per-install user ID, and product-interaction events such as app opened, onboarding steps, paywall viewed, and feature usage.

The advertising identifier (IDFA) is disabled and the app does not track you across other companies' apps or websites, so iOS shows no tracking prompt — there is nothing to opt out of at the OS level because cross-app tracking is off by design. Analytics events never include your regimen entries, dose logs, journal text, Health data, or Coach messages.

Purchase history is processed through RevenueCat to make your subscription work and for our own revenue analytics. The optional community profile is separate from purchases and analytics identifiers. Community credentials and text are not included in analytics events. The optional feedback reply-to field accepts an email address; community has no email field, and you should not put contact details in posts.

Third parties with access to your data

Peptide Vault's private tracking does not require an account. The optional community creates a separate pseudonymous profile. A small set of service providers receives the limited data described here so the app can work. We only use providers that are required, by their agreement with us and their own published commitments, to protect that data at least as strongly as this policy promises: to use it solely to deliver the service we asked them for, to keep it confidential and secure, not to sell it, and not to repurpose it for their own advertising.

PostHog — product analytics. Receives a random per-install identifier and product-interaction events such as app opened, onboarding step completed, paywall viewed, and feature usage.

AppsFlyer — install attribution. Receives campaign metadata and pseudonymous install identifiers. These identifiers can be linked with RevenueCat purchase events for attribution and analytics. The advertising identifier (IDFA) is disabled, so the app does not track you across other companies' apps or websites.

RevenueCat — subscription state. Receives purchase and subscription status so that Pro unlocks on your device. RevenueCat learns that you subscribed, never what you entered in the app.

Superwall — onboarding and paywalls. Receives the app's stable user identifier, subscription entitlement status, PostHog and available AppsFlyer identifiers, and the number of tracked compounds with a broad empty/single/stack category to present and measure subscription offers. These attributes do not include compound names, dose logs, journal text or Apple Health records.

OpenAI — optional Coach message processing and separately consented community screening. Coach sends your typed message, plus compound names and a stack summary only if you turn on its share toggle. Community screening sends only the post or reply text you intentionally submit after accepting its screening notice, with no separate profile, billing or private tracking fields. OpenAI handles these requests under its API data policy, which does not use API data to train its models by default. The community privacy notice explains this separate consent and how screening works.

Supabase — database hosting for optional feedback and community. Feedback includes the note text, app version, one-way install hash and optional reply-to email. Community includes the pseudonymous profile and credential hash, submitted text, thread dates and status, reports, blocks and restricted moderation records. It does not receive private tracker records automatically. Application hosting processes these requests and technical network information; the community signup limiter stores a keyed IP hash rather than a raw IP in community tables.

Resend — email delivery, and only for a feedback note you have sent. Receives the note text and your email address if you supplied one, in order to deliver a copy of it to us.

Google — the mailbox that copy is delivered to. Receives the same note text and, if you supplied one, your email address.

These services do not automatically receive your regimen entries, dose logs, journal text or Apple Health records. Optional submissions include whatever you choose to type or copy into them; avoid sensitive information. We do not sell personal information. The community privacy notice explains the providers and controls for that feature.

Data retention — how long your data is kept

Your private protocols, dose logs, journal entries, reconstitution inputs and Apple Health records stay on your iPhone until you clear them or remove the app. We have no server backup of those records to restore. Copies you intentionally submit through an online feature follow that feature's retention rules. Feedback notes remain on our server after the app is deleted; email us to request their removal. Community threads expire after 30 days, while profiles remain until deleted. Restricted moderation evidence and moderator action records expire after 30 days and are removed by daily cleanup.

Coach messages are not stored on our server. Each message is processed in the request that carries it, forwarded to OpenAI to generate the reply, and then dropped — we keep no chat history. Anything forwarded is retained and deleted by OpenAI under its own API data policy.

Analytics and attribution events are retained by PostHog and AppsFlyer under their standard retention schedules and deleted on those schedules. These events carry a random per-install identifier and campaign metadata; they are not linked to your optional community profile or its content.

Purchase and subscription records are retained by RevenueCat and by Apple for as long as needed to keep your subscription working and to satisfy their own legal, accounting, and tax obligations.

Purchases

Paid subscriptions are processed by Apple through the App Store. The app receives a purchase status signal from RevenueCat, the purchase management provider, which validates purchase receipts from Apple. RevenueCat learns that you purchased — never what you entered in the app. Manage or cancel anytime in iOS Settings → Apple ID → Subscriptions.

Not a medical device

Peptide Vault is a passive tracking tool. It is not a medical device and does not provide medical advice, diagnosis, or treatment. Only use it to log regimens, doses, or activities that have been directed by a licensed healthcare provider or that you have independently chosen to track for personal reference. Always consult a qualified healthcare provider before starting, changing, or stopping any protocol.