Privacy Policy
Last updated: November 12, 2026
This page explains what data Designing Longevity collects, how we use it, and what control you have. We try to be plain about it: this isn't a legalese exercise, it's a description of what actually happens.
Who we are
Designing Longevity is an editorial publisher and tools site focused on peptides and longevity. We are not a healthcare provider, pharmacy, or telehealth service. We don't prescribe anything, dispense anything, or have a clinician-patient relationship with you. We are also not a HIPAA-covered entity.
What we collect, and why
If you don't sign up
We collect standard server logs (timestamp, page requested, user agent, referrer) for operations and security. We use Google Analytics and PostHog for aggregate traffic analytics. These tools may set cookies; you can opt out of analytics via standard browser settings or extensions.
Homepage choice counts
When homepage choice counts are on, we use them to see which shortcuts readers use. We store weekly totals by button and menu version. A count measures clicks and can include repeat visits. This setting applies to this browser profile on this site.
Checking this browser's setting…
Session recording
We use Hotjar by Contentsquare to see where visitors get stuck on public pages. Hotjar uses browser storage and a browser identifier to record page visits, clicks, pointer movement and scrolling. Search, account pages and tools that ask for personal health details run outside the recording. In locations where prior consent is required, Hotjar loads only after you allow it. You can stop future recordings in this browser below. See the Contentsquare Privacy Center.
Records from the earlier topic quiz
We counted quiz-start and quiz-completion requests separately. Each request had its own random diagnostic ID, event type, timestamp and delivery status. This measurement set no tracking cookie, created no browser identifier and did not link quiz activity to provider clicks. These records contain no quiz answers, health topic, account ID, IP address, raw user agent or raw page URL. We excluded Do Not Track, known bots and prefetch requests and kept signed test traffic separate. Requests could be missed or repeated, so these counts do not establish individual completion rates, unique people, medical eligibility, sales or commissions.
If you sign up for an account
We use Firebase Authentication (Google) to manage accounts. We store your email, display name, and (if you sign in with Google) profile photo URL. We use this to identify you and personalize your experience.
If you save protocol items (peptides, supplements, lifestyle interventions, exercises, lab targets), reconstituted vials, dose logs, daily-adherence checks, or measurements, we store them in Firestore scoped to your account. This data is your protocol; we don't share it with anyone, sell it, or use it to train models.
When you click an outbound provider link
Provider-profile buttons route through /go/[provider-slug] so we can measure outbound requests. These records contain the provider, a general placement label, a random request ID, timestamp and delivery status. Each request stands alone; it is not linked to quiz activity or a browser identifier. We exclude known bots and prefetch requests, separately mark our test requests, and skip measurement when your browser sends Do Not Track. These records contain no account ID, IP address, raw user agent, peptide context, or quiz answers. A recorded request does not establish a unique person, a qualified referral, or a commission.
See our provider vetting methodology for the full affiliate disclosure.
FTC-required affiliate disclosure
We currently have no active provider affiliate relationships. If that changes, we will disclose the paid relationship next to the relevant link and explain the qualifying event. Our policy excludes per-prescription compensation and pay-to-rank inclusion. Provider-selection criteria are described in our methodology; a paid relationship would not replace those criteria.
Third-party services we use
- Firebase (Google) for authentication and data storage. Their privacy policy applies to data they process on our behalf.
- Vercel for hosting. Standard server logs.
- Google Analytics and PostHog for aggregate traffic analytics.
- Hotjar by Contentsquare for session recordings on public pages.
- SendGrid for transactional email (protocol reminders).
- Sentry for error monitoring.
Email reminders
If you save a peptide protocol, we may send you reminder emails when something needs your attention (vial expiring, cycle phase flipping). Every reminder includes a one-click unsubscribe link that turns off all reminders for your account. You can also email us to unsubscribe manually.
Your control over your data
- See it: all your saved protocol data is visible in My Protocol.
- Delete an item: archive or delete any protocol item from its detail page; we cascade-delete the item and all its sub-records (vials, dose logs, etc.).
- Stop reminders: click the unsubscribe link in any reminder email, or email us.
- Delete your account: contact us from the address on your account and we'll delete the account and all associated data within 30 days.
What we don't do
- We don't sell your data.
- We don't share your protocol or dose logs with anyone, including the providers we list.
- We don't use your data to train AI models.
- We don't link click logs to your account ID.
Children's privacy
Designing Longevity is intended for adults 18 and over. We don't knowingly collect data from anyone under 18. If you believe a minor has created an account, email us and we'll delete it.
Changes to this policy
If we materially change how we handle data, we'll update this page and bump the "Last updated" date at the top. For significant changes affecting saved-account holders, we'll email you.
Contact
Questions, requests, or anything privacy-related, see our contact page.