PeptaHub
The comprehensive peptide reference
● PRIVACYLAST UPDATED · 2026-04-22

Your data, plainly.

PeptaHub is an independent reference site. The policy is short because the collection is minimal. Privacy by design, not by lawyer-speak.

§ 01

Summary

In one paragraph: PeptaHub uses Google Analytics 4 (GA4) to understand aggregate site usage and improve the content. GA4 sets a small number of first-party cookies that allow it to distinguish returning visits from new ones; it does not build cross-site advertising profiles from this data. If you sign up for the email newsletter, the email provider (Beehiiv) stores your email address and a few engagement signals so we can send you the newsletter and improve it. PeptaHub does not sell data, does not share it with advertisers, does not run retargeting pixels, and does not use Meta Pixel or similar ad-network trackers. You can unsubscribe with one click and your data is removed from the newsletter provider within 30 days.

§ 02

What we collect when you browse peptahub.com

PeptaHub uses Google Analytics 4 (property ID G-49WKRDWXHN) for aggregate site analytics. GA4 collects, in aggregate:

  • The URL of the page you viewed and time-on-page
  • The URL of the page you came from (HTTP referrer)
  • Your browser and operating system (from the User-Agent string)
  • Approximate geographic location (typically city-level) derived from your IP address. GA4's IP Anonymization is enabled; full IP addresses are not retained.
  • Device type (desktop / mobile / tablet)
  • Engagement events (clicks, scrolls, outbound links) used to understand which content helps readers

GA4 sets first-party cookies (see § 05 below) to distinguish returning visits. PeptaHub does not use Google Ads, Google Signals, or any Google advertising feature that would enable cross-site ad retargeting. We do not upload user-ID data to GA4 and do not enable Google's cross-device identity graph.

PeptaHub does not use Meta Pixel, TikTok Pixel, or any other surveillance-adtech tool.

If you prefer to opt out of analytics entirely, most modern browsers support a Do Not Track signal (PeptaHub honors it) or you can install the official Google Analytics opt-out browser add-on.

§ 03

What we collect if you sign up for the newsletter

PeptaHub's newsletter is sent via Beehiiv. When you sign up, Beehiiv stores:

  • Your email address (required)
  • Your first name, if you provide one (optional)
  • Engagement signals: whether you opened a given email, which links you clicked, and aggregate open/click rates over time
  • The signup source (e.g., quiz completion or newsletter form) and any tags you click through in the welcome sequence (e.g., "interested in longevity")

This data is used to send the newsletter, segment the list so the content stays relevant to you, and improve the email sequence over time. It is not sold, not shared with advertisers, and not used for purposes outside the newsletter relationship.

You can unsubscribe at any time via the one-click link in any newsletter email. After you unsubscribe, your data is purged from active lists immediately and removed from the Beehiiv account within 30 days.

§ 04

If you email us directly

If you send a question, correction, or feedback to hello@peptahub.com or corrections@peptahub.com, we read it and reply. The email and its content are stored in the regular mail provider's inbox. Emails are not added to the newsletter list automatically, and are not shared with third parties.

If you ask us to delete your email thread, we will.

§ 05

Cookies

peptahub.com uses a small set of cookies. None of them are used for advertising or cross-site tracking:

  • Google Analytics cookies _ga (2 years) and _ga_* (2 years) are set by GA4 to distinguish returning visits from new ones and to count sessions. These are first-party cookies readable only by peptahub.com; they do not follow you to other sites.
  • Preference cookies— e.g., a dark-mode / light-mode toggle and a "dismissed cookie notice" flag. Local to your browser, not transmitted to any server.
  • Cloudflare security cookies — set by our CDN provider (Cloudflare) to protect the site from bots and abuse. These are short-lived, functional, and not used for advertising.
  • Supabase authentication cookies — set only if you sign up for an account in Phase 14+. These store your session token so you stay signed in. Short-lived (1 hour access token, 30-day refresh token). First-party, not used for advertising.

No advertising cookies. No third-party trackers. No cross-site fingerprinting. If that changes, this page updates first. If you are in a jurisdiction that requires opt-in consent for analytics cookies (e.g., EU/EEA under ePrivacy), use your browser's cookie controls or the GA opt-out add-on linked in § 02 to decline.

§ 06

Data retention

Plausible analytics data is retained in aggregate form indefinitely — it contains no personal identifiers, so there is nothing to delete per user. Newsletter data (email, engagement history) is retained for as long as you are a subscriber, plus up to 30 days after unsubscription. Correspondence sent to PeptaHub email addresses is retained for as long as useful for responding to the thread, then archived or deleted.

§ 06a

Data licensing program (optional)

PeptaHub offers an optionaldata-licensing consent. This is a deliberate, opt-in grant — signup and full use of the platform never require it, and if you don’t grant it, none of your data can be included in any research export.

What the grant includes.If you grant consent, your de-identified tracking and review data (dose logs, wellness logs, vial stock rows, stacks, protocols, reviews, review comments) can be included in aggregate research datasets PeptaHub may license to third parties — for example, academic researchers or pharmaceutical partners studying peptide usage patterns at population scale. “De-identified” means: no user ID, no email, no username, no display name, no free-text fields that could re-identify you. Only the structured fields (peptide slug, dose amount, rating, timestamps at day-level resolution).

What the grant does not include. The grant never includes your email address, direct messages, comment reply bodies, or any other free-text field. It never permits re-identification. It never permits sharing data with advertisers or data brokers. It is not a consent to marketing or to being contacted about the research.

Why we ask.Peptide usage data at scale is scientifically valuable — there is no comparable structured dataset today. Consent-based aggregate research is how adjacent platforms (23andMe × GSK, PatientsLikeMe × UnitedHealth) have contributed to peer-reviewed findings. This program is the long-term research contribution path for PeptaHub. It is explicitly not the revenue model (subscriptions are).

How to grant or revoke. Visit Account settings→ Data & privacy. Grant and revoke are one-click. Revoking stops future inclusion of your data in new export batches. Previously-exported aggregates that were already shipped under the prior grant cannot be recalled from the recipient, but no new exports will include your rows after revocation.

Audit trail. Every grant and revoke writes a timestamped row to the audit_events table you can request via Access (§ 07). Nothing about the program is silent.

§ 07

Your rights

Under GDPR, CCPA, and similar frameworks, you have the right to:

  • Access — ask what data PeptaHub holds about you (for the newsletter, this is always: your email address + engagement history).
  • Correction — ask us to correct any inaccurate data.
  • Deletion — ask us to delete your newsletter data. One-click unsubscribe is the fastest route; emailing privacy@peptahub.com also works.
  • Portability — ask for a copy of your data in a machine-readable format.
  • Objection — object to any use of your data outside the explicit newsletter relationship (PeptaHub does not use data outside that relationship, but the right exists).

To exercise any of these rights, email privacy@peptahub.com. We respond within 30 days (usually much faster).

§ 08

Changes to this policy

If PeptaHub's data practices change — new provider, new data type collected, anything material — this page is updated with the change and the "last updated" date in the header reflects it. If the change materially expands what we collect, existing newsletter subscribers receive an email notice before the change takes effect.