A clear view
of your privacy.

Visitor analytics.

We use Vercel Web Analytics to understand visits, popular pages, referral sites and general device and country statistics. It does not use analytics cookies. We remove query strings and fragments, group product and discussion pages, and exclude private sharing links from page-view tracking. We do not send names, emails, quiz answers, health records, community messages or form contents as analytics events.

Preview notice · October 13, 2026. This notice describes the delivered prototype. A reviewed production privacy policy is required before a public launch with real accounts and health information.

What stays in this browser.

The interactive preview stores your preview account (first name and email), profile answers, health conditions, check-ins, stack entries, confirmed lab markers, genetic test results, saved products, saved AI research answers, workout plans and completed sets, paused workout progress, community posts and images, points, and preferences in browser local storage. Peptide-finder answers, manually entered purchase records and affiliate follow-up notes are also local. When you sign in, your records are kept in your account’s own space in this browser and you stay signed in until you sign out; the first time you sign in, what you did before signing in moves into your account and is removed from the shared space. Signing out hides your records from the next person on this device. Fields you choose to share with an affiliate or in a private link are also copied to Betterlife’s server, as described below. This storage is not an encrypted health vault. Use fictional information and avoid shared devices.

When you choose AI workout help.

Creating an AI workout sends the time, place, equipment, focus and pace you select to OpenAI through the application server. If you explicitly select “Use my last 3 workouts,” their dates, exercises, sets and weights are included. Your profile, conditions, medications, check-ins and private notes are not automatically included.

“Organize with AI” sends the workout note you enter to OpenAI. Include only information you want to share. You review the extracted information before it is saved. Manual logging and starter workouts do not use an AI service. Requests set store:false; provider processing and retention policies still apply. The server does not log note bodies or credentials.

When you ask Betterlife a research question.

Submitting a question sends its text, the selected research task, and up to three recent questions and short answer summaries to OpenAI. The service searches scientific and regulator sources and prepares a cited answer. Search queries can be processed by the provider’s search services. Ask general research questions rather than entering identifying or private health information. Your profile, medications, check-ins, labs, workouts and private notes are not automatically included. Opening a suggested question only fills the form; it does not send it.

Research requests set store:false; provider processing and retention policies still apply. The application does not log question bodies or credentials. Conversations remain in page memory unless you choose Save answer. Saved questions, answers and sources are stored in this browser and included in profile export and deletion. Start a new conversation to clear the context sent with the next question. Read-aloud uses your browser’s speech service when requested.

If you joined through an affiliate’s link.

When you sign in after arriving through an affiliate’s link, Betterlife’s server records your account identifier, that link’s code, your first name and last initial, and when you joined and were last active, so the affiliate sees that you signed up. Nothing else is shared unless you turn on sharing under Profile → Privacy & sharing and tick a field. Each field is off until you tick it: your contact details (name and email); goals; peptide matches; the Platinum peptides in your current stack and when you started them; recorded purchases (product, date and total); the date of your last check-in; your health profile (your age in years, never your date of birth, plus sex, height, weight and activity level); your health conditions and medications (the conditions you recorded, your medication note and the medications you take now); and lab results (the name, value, unit, reference range and date of each confirmed marker, up to your 50 most recent; report and file names stay private). Genetic test results are never shared.

While sharing is on, your browser sends the ticked fields to Betterlife’s server, which checks them and keeps them with your signup in a private file on the preview server, and replaces them as your records change. Turning sharing off, or unticking a field, removes it from what the affiliate can see. Affiliates see only people who joined through their own link, and the follow-up ideas on their dashboard never use your health details. Removing a field cannot erase what the affiliate has already seen or copied.

Private links for coaches.

Coaches without a Betterlife account, such as the Platinum Betterlife Team, a biochemist or a fitness coach, see your health profile only through a private link you create under Profile → Privacy & sharing (signed-in members whose records stay in this browser). You choose what each link shows, from: your health profile, health conditions and medications, and lab results (each as described above), your goals, peptide matches and current stack. A link never shows your name, email, date of birth, purchases, check-ins, photos, genetic test results or the notes on your stack entries. It shows a copy of the chosen fields as they were when you created the link; later changes appear only if you refresh it.

Anyone who has the link can open its read-only page, so give it only to the person it is for. Each link contains a long random code. Betterlife’s server keeps a one-way fingerprint (SHA-256 hash) of that code, never the code itself, together with the copy of your chosen fields, who you said the link is for and the link’s dates, in a private file on the preview server. A link expires after the period you choose (30 days unless you pick 7 or 90), and you can revoke it at any time. Either way it stops opening at once, and its copy of your details is deleted: immediately when you revoke it, or with the next change to the links once it has expired. You can have up to 10 active links.

Each time a link opens, Betterlife counts the view and records when it was last viewed, which you see next to the link; who opened it is not recorded. Messaging apps that preview links may open it too, which counts as a view. Link pages are excluded from search engines and are never cached. An expired or revoked link shows the same message as one that never existed. Revoking cannot erase what someone has already seen or copied, and deleting your browser records does not revoke links: revoke them first.

When you turn on Personalize in Ask.

Ask answers from Platinum’s library first. When AI is available, it sends your question, up to two recent questions with short answer summaries and the library content for the answer to OpenAI to write a reply; every number in that reply is checked against the library. Personalize is off until you turn it on. While it is on, each question also shares your Find my peptides goals and preferences (experience, format and budget), the Platinum peptides in your current stack with the amount, frequency and start date you recorded, your matches, saved products and your latest check-in (its date, scores, consistency and any side effects you noted, with severity). It shares only whether conditions or medications are on file, never what they are. Your name, email, date of birth, weight and measurements, labs, other stack items, notes and photos are never shared. Your choice is saved with your preferences until you turn it off in Ask. Requests set store:false; provider processing policies still apply.

Translate or listen to information pages.

When you choose a language or press Listen on a reference, product or journal page, the application server sends that public page’s educational text to OpenAI. It does not include your profile, private records or community posts. Translation uses store:false. Translations and generated voice clips are cached temporarily in server memory to avoid repeating requests; audio in the page is released when you leave or change language. The voice is AI-generated. AI translation may contain errors; the English original is always available. Provider processing policies still apply.

AI access and usage.

The local preview can use AI on this machine. When account AI is configured, your sign-in is checked before research, translation, audio or workout requests. The private service records feature counts and temporary request identifiers to enforce usage limits. Those records do not include your questions, answers, health records or sign-in credentials. Your Firebase token is not sent to OpenAI. Reading a cached translation or audio section does not use another generation allowance. Limits and temporary capacity messages appear when a request cannot start.

What leaves the browser.

The local Next.js server serves the site and image assets. Fonts are hosted with the application. Product and research links open third-party websites when you choose them. PBL store links can include a referral code and general source tags, without health answers, medications, lab results, or symptoms.

When Firebase environment settings are supplied and you use sign-in, the entered account credentials are handled by Firebase Authentication. When private account storage is also configured, signing in opens a separate account workspace. It does not upload anonymous preview records. Completed finder answers, profile details, stack entries, check-ins, confirmed lab markers, saved peptides and manually recorded purchases are loaded and saved through the authenticated private service. The header reports whether a save is confirmed or needs attention.

In an account workspace, workouts, photos, learning progress, saved research answers, and unfinished community drafts stay in this browser tab. A recovery copy of unsaved core records is kept in the tab only when you choose to load the saved version after a save problem. Signing out clears these account-specific tab records; unsaved changes can be lost. The separate anonymous preview remains in browser local storage. Browser copies are not encrypted health vaults.

Completed account matching keeps dated versions of your ranked goals, disclosed conditions, medication note, active compound names, matching rules and research shortlist. Updating your answers does not overwrite earlier versions. This history is saved through the private service, included in your account export and private to you. Affiliate sharing covers your chosen current fields; it does not grant access to this private history. Matching history does not copy lab files, purchase details or unrelated journal notes.

Community discussions.

The anonymous preview keeps its discussions in this browser and labels fictional examples. In a configured account workspace, the community service receives your chosen community name, the post or reply you explicitly publish, and any progress fields you select and review. Your private profile name and health history are not added automatically. Published discussions are visible to signed-in members, including on their home page. Unfinished drafts stay in the account’s browser tab and are cleared on sign-out. Bookmarks are private to your account. Authors can withdraw and restore a discussion; moderation can hold or remove it. Withdrawal is not erasure of server records.

Your sharing choices.

An affiliate invitation shows their chosen display name after sign-in. Opening the link does not connect your account. Accepting adds a connection with record sharing off and saves the referral only if no earlier referral exists. Until you share fields, the affiliate sees a private client label. Invitation links expire after 30 days and can be replaced or turned off by the affiliate.

Affiliate and coach sharing is off by default. In a configured account workspace, open My profile → Privacy & sharing to choose fields for each assigned affiliate. You review your choices before confirming. Your profile name accompanies the fields you share: goals, current research matches, purchase records, check-in measurements, stack entries or confirmed lab markers. Affiliates may use shared information for product discussions and commercial follow-ups. Purchase amounts and affiliate revenue do not affect matching.

In an account workspace, medical screening answers, medications, symptoms, private reflections, document files, filenames and order references are excluded from the affiliate view, and private links for coaches are not available yet. The service checks the affiliate’s role, second-factor sign-in, active assignment and your current sharing choices. Once Stop sharing is confirmed, future reads of those fields are blocked. The affiliate screen refreshes access while visible and clears shared details when hidden. Stopping access cannot erase information already viewed or copied.

Affiliates can save private conversation notes, a stage and an optional follow-up date. Notes remain with that affiliate relationship and are not sent to you; saving a note does not send a message or schedule a reminder. Unsaved notes last only while the affiliate workspace stays open. The anonymous preview demonstrates these controls in one browser and does not change permissions in an account.

End this connection turns off all sharing with that affiliate. Reconnecting requires a fresh invitation review and leaves previous sharing choices off. Disconnecting keeps the original referral attribution and does not erase notes or copies the affiliate already holds. Account store links use the saved referral and public product/source tags; they exclude your name and health records. Partner-confirmed purchases and commissions require the separate store integration.

Export or delete.

Open My profile → Privacy & sharing to export your preview records or remove them. Browser storage can also be cleared through your browser settings. Removing your records turns affiliate sharing off but does not revoke private links; revoke those in the same place. Exported files and any copies you make remain your responsibility to remove.

In an account workspace, export downloads saved core records from the service and deletion submits a pending request. Both require a second factor at sign-in. In Account security, you can verify your email, connect an authenticator and complete the second sign-in step when the account service is configured. Setup keys and codes are handled by Firebase Authentication and stay out of your health records, community and AI conversations. A deletion request is not confirmation that records have been erased. A configured retention process must complete it. Account export does not include community records, the separate tab-only tools or unsaved changes. Community export and retention workflows are not connected yet.

Before production.

Live integration acceptance, project configuration, storage permissions, backups, retention schedules, privacy contacts, vendor agreements, legal review, and operational security review must be completed before real health records are collected.