Back to Home

Privacy Policy

This page explains what information PeptideBenchmark may collect, how it may be used, and what third-party services may be involved when you use the site.

Overview

PeptideBenchmark is a content website focused on peptide benchmark data, research coverage, and editorial guides. Public content does not require an account. Eligible vendors may separately use a magic-link vendor portal and sponsor billing services.

Information we may collect automatically

Like most websites, PeptideBenchmark and the infrastructure providers used to serve it may automatically collect limited technical information such as:

  • IP address
  • browser type
  • device or operating-system information
  • referring page or domain
  • pages visited and basic request timing

This kind of information is generally used for site delivery, reliability, abuse prevention, debugging, and aggregate traffic understanding rather than for creating user accounts or selling products directly to you.

Public access and vendor accounts

PeptideBenchmark does not require account creation to read public content and does not maintain a consumer member-login system. Vendor representatives may use email-based authentication for private portal and billing functions; associated access, vendor, and transaction records are used to provide and secure those services.

Newsletter and sponsorship inquiries

If you sign up for the Weekly Peptide Intel newsletter or a sponsorship waitlist, we collect the email address you submit. For sponsorship inquiries, we may also collect the vendor or company name, your note, the placements you select, preferred timing and term, and a budget range. We may add limited internal status, qualification, proposal, and follow-up notes needed to manage the inquiry. Signups are protected by Cloudflare Turnstile, which processes the verification challenge under Cloudflare's own privacy terms.

Newsletter subscriptions are double opt-in: no issue is ever sent to an address that has not clicked the confirmation link. Subscription state (pending, confirmed, unsubscribed) is stored in Cloudflare Workers KV, and emails are delivered through Amazon SES. Every issue includes a one-click unsubscribe link and header; unsubscribing takes effect immediately and permanently until you re-subscribe and reconfirm.

Newsletter emails contain no tracking pixels — we do not measure opens, and links go directly to their destinations. Newsletter addresses are used only to administer the newsletter. Newsletter subscription and unsubscribe choices are separate from sponsorship communications.

Sponsorship inquiry data is used to evaluate fit, respond to the request, prepare terms or a proposal, manage the sales relationship, and follow up about relevant placement availability. After a public waitlist request has been stored, PeptideBenchmark may send one automatic acknowledgement for each newly requested placement. The message asks the recipient to confirm that mailbox; future public requests are not included in slot-opening outreach until the exact requested placement is confirmed. A slot becoming available does not itself send a broadcast: opening outreach is sent only after an operator reviews and approves the specific inventory, terms, content, and recipients. Addresses and inquiry details are never sold or shared for unrelated marketing.

Sponsor emails provide a sponsor-specific unsubscribe option. A sponsor opt-out suppresses future sponsor outreach without changing a Weekly Peptide Intel subscription, and a newsletter unsubscribe does not change sponsor inquiry records. A message already accepted for delivery may still arrive. A minimal hashed suppression record may be retained so the sponsor opt-out continues to be honored. Sponsor unsubscribe links use random opaque capabilities; only a one-way token digest and its hashed-recipient mapping are retained, for no more than 730 days.

Sponsorship lead records are stored in Cloudflare Workers KV and expire no later than 730 days after their last update. A delivery journal in Cloudflare D1 stores hashed recipient identifiers and limited campaign and delivery metadata for duplicate prevention and audit history; retained campaign membership commitments are secret-keyed. After verified erasure removes the ordinary recipient hash and lead id, the remaining campaign commitment cannot be rebuilt by guessing an address from the journal alone. The journal does not store the raw email address or the inquiry note. A hashed per-placement acknowledgement job is committed before a successful public response so scheduled maintenance can retry a message interrupted after intake. Its acknowledgement-job, authorization, unsubscribe-capability, and delivery-history rows are assigned a 730-day retention deadline and are removed by scheduled sponsor-email maintenance. Sponsor email delivery passes the destination address and message through Amazon SES. Internal email/push alerts contain only a lead id and requested placement, not the submitted email, vendor name, note, or qualification fields. You may request correction or deletion through the contact page; verified deletion requests remove the lead record and its lookup indexes, remove mailbox authorizations, and scrub identity from any immutable campaign membership record. A later public submission cannot silently recreate an erased lead; re-entry requires a deliberate re-consent process. Separate suppression, transaction, security, or accounting records may be retained as legally or operationally required.

Core public content can be browsed without creating an account or providing any of the above.

Referral and affiliate links

Some pages may contain referral or affiliate links. If you click one of those links, the destination site may be able to tell that the visit came from PeptideBenchmark or a PeptideBenchmark-associated referral code or identifier.

We may receive compensation, points, or similar credit if a referral relationship applies. That activity is governed in part by the privacy and tracking practices of the destination site, not just PeptideBenchmark.

Third-party content and embeds

Some pages may include third-party embedded content, such as YouTube videos. When you load a page with an embedded third-party player or widget, that third party may collect data such as IP address, browser information, and interaction data, and may set cookies or similar tracking technologies depending on its own policies and your browser settings.

Analytics and tracking

PeptideBenchmark uses privacy-oriented analytics to understand aggregate traffic patterns and measure outbound referral clicks to vendor storefronts. These tools do not create user accounts and are not used to sell personal information.

  • Cloudflare Web Analytics — cookie-free pageview and performance metrics when enabled. See Cloudflare Web Analytics.
  • Google Ads click measurement (first-party) — if you arrive from a Google ad, Google appends a click identifier (such as gclid) to the landing URL. The site stores that identifier in your browser's local storage (no cookies, no tag or pixel) for up to 90 days. If you later click a tracked vendor link, the identifier may be reported back to Google Ads so the ad click can be counted as having led to a vendor visit. It identifies the ad click, not you, and is not combined with any information that identifies you.
  • First-party outbound click counts — when you click a tracked vendor storefront or affiliate link, the site may record the vendor slug, link placement (for example vendor profile or pricing board), and page path via a first-party endpoint. No email, name, or checkout data is collected.

How information may be used

Information associated with site usage may be used to:

  • deliver and secure the site
  • diagnose technical problems
  • understand broad traffic patterns
  • monitor abuse, spam, or malicious activity
  • evaluate performance of content or referral flows at an aggregate level

Third-party services

Depending on the deployment environment, PeptideBenchmark may rely on third-party infrastructure and platform providers, such as hosting, CDN, DNS, repository, or embedded-media providers. Those providers may process technical request data in the course of serving the site.

Data sharing

We do not describe the site as selling personal information directly through the current public content experience. However, third-party services involved in serving, embedding, or referring traffic may receive technical or referral-related data as part of normal operation.

Data retention

Sponsorship lead records expire within 730 days of their last update. Sponsor acknowledgement-job, authorization, campaign/delivery, and opaque unsubscribe-capability rows are assigned a 730-day maintenance deadline as described above. Minimal newsletter and sponsor suppression records may be retained to honor opt-outs. We do not publish one fixed schedule for infrastructure logs, aggregate analytics, transaction records, or third-party platform data; those periods depend on security, accounting, legal, and provider requirements.

Children's privacy

PeptideBenchmark is not directed to children. If you are a parent or guardian and believe a child has provided personal information through the site, contact us and we will review the situation.

Changes to this policy

This policy may be updated as the site changes. If PeptideBenchmark adds material data collection or changes how personal information is used, this page will be revised to reflect that. (Last substantive update: September 18, 2026, for sponsor acknowledgement, campaign-delivery, and suppression operations.)

Contact

If you have questions about this privacy policy or the way the site handles public content and referral disclosures, use the contact path provided on the site.