Privacy policy.

We collect the minimum necessary to run an editorial publication:

• Email address — only if you subscribe to our newsletter.
• Anonymous analytics — aggregated page-view data with no cookies tying it to an individual.
• Server logs — standard request logs (IP, user agent, timestamp) retained 30 days for abuse prevention.

We do not collect biometric data, location data beyond coarse IP geolocation, browsing history outside our site, or personal health information.

Email addresses are used only to send you issues of The Peptide Examiner newsletter and occasional critical updates (e.g., if an article you read contained a material error). We do not sell, rent, or share your email address with advertisers, vendors, or third-party marketers.

Analytics data is aggregated and used to understand which articles land, which don't, and how to make the publication better.

• Vercel — hosting and CDN. Sees request logs.
• Supabase — stores your email address if you subscribe.
• Resend — sends our newsletter email. Sees your email address and delivery metrics (opens, clicks).
• Plausible or Vercel Analytics — privacy-preserving, cookie-free page-view analytics.

We never use Facebook/Meta Pixel, Google Analytics with cross-site tracking, or ad-network retargeting pixels.

When you click an affiliate link on our site (always clearly labeled), we log the click anonymously (vendor, article slug, timestamp, coarse referrer) for our own performance reporting. We do not build a behavioral profile of you. The third-party affiliate partner you click through to has their own privacy policy, which applies once you leave our site.

You can unsubscribe from the newsletter at any time via the one-click link in every issue. You can also email privacy@thepeptideexaminer.com to request your data be deleted. We will comply within 30 days.

If you are in California (CCPA), the EU/UK (GDPR), or another jurisdiction with specific data-protection rights, those rights apply. Contact us at the address above to exercise them.

All data is transmitted over HTTPS. Email addresses are stored in Supabase (SOC 2 Type 2 compliant). Access to subscriber data is limited to the editorial team.

We will update this page when our data practices change and note the revision date at the top. Material changes will be communicated to subscribers via the newsletter.