01 · Site analytics
Cookieless counts and optional analytics
We use PostHog to count page views without cookies. It also counts four actions. These are a search or checker result shown, a comparison shown, a shared or copied link or citation, and a sent correction report. These counts set no cookies and save nothing in your browser.
PostHog receives the page address without its query string or fragment, the site that sent you, and general browser and device details. The page address shows which page you opened, such as a peptide guide. PostHog never receives your search words, names you type into the checker, or your form answers. Each action is sent as a fixed code, such as “result shown.”
If something on a page breaks in your browser, PostHog also gets a short error report. The report holds the error type, a short error message, and the place in the code where it broke. It also holds basic browser details and the page address without its query string. A message can include a few words from the page. We cut each message to 200 characters. Web addresses in the report lose their query strings and anything after a # sign. We send at most 10 error reports for each page you open. We use them only to find and fix broken pages.
Our server passes your network address to PostHog with each count and error report. PostHog uses it only to make a code that changes every day, mixed with browser details. PostHog does not store the address. That code lets us count visitors without tracking you from one day to the next.
These counts and error reports stop if your browser sends Do Not Track or Global Privacy Control. They also stop if you turn analytics off below. PostHog handles this data under its privacy policy. We do not use it for ads or medical profiles.
Optional site analytics and Google Analytics stay off until you allow them. Your choice is stored in a cookie and browser storage. We ask for a fresh choice when we add a new analytics recipient. You can change your choice below at any time.
Our own database stores daily totals for selected tool actions. Each record contains only a date, an approved action code, and a count. It has no visitor or session record. These totals remain separate from Google Analytics.
If you allow analytics, our server also sends Google general page categories, such as “article,” and approved actions, such as opening content. A random visit code links events while the page is open. It stays in memory, not in a tracking cookie. It resets when you reload the site or turn analytics off. This code does not identify you, but it lets Google group events from the same visit.
Google receives no search words, peptide names, page addresses, query strings, referrers, document titles, or form answers. Search, input tools, correction reports, private routes, and pages with query strings or fragments are excluded from Google collection. No Google tracking script runs in your browser. Our server does not forward your network address, browser details, or cookies to Google.
We use these records to improve navigation and site content. We do not use them for ads or medical profiles. Advertising features and automatic event collection are off. Turning analytics off stops new events; it does not remove records already sent. Google processes analytics data under its privacy policy. The hosting service still handles normal request data needed to deliver the site.
Google event and user data retention is set to two months. New activity does not restart that period. Google can retain aggregate reports for longer. Our own daily totals have no automatic deletion date, as described below.
02 · What the site collects
Correction reports
A report contains the page URL, disputed text, explanation, optional source URL, and optional email address that the sender enters. The service also creates a private report reference, a private deletion code, creation and expiry times, and a temporary anti-abuse code. The service does not keep the raw network address.
Do not submit medical records, treatment details, government identifiers, payment information, or other sensitive personal data.
03 · How the site uses reports
Reports are used only to review corrections
Private submissions are available only for correction review, response, abuse prevention, and service security. The Peptide Field does not publish them automatically. A public correction record does not include the submitter's email or private free text unless The Peptide Field first gets separate, clear permission.
04 · How long the site keeps it
Reports are set to expire after 90 days
A correction report expires 90 days after the service receives it. The service deletes expired reports the next time it receives a report. If no new report arrives, an expired report can remain in the database. There is no separate timed deletion process. The confirmation screen also lets you delete the report at once during that browser session with its private deletion code.
Counters help limit repeated reports within a set period. The service removes expired counters when it next checks an incoming report. They store a protected code, never the raw network address.
Daily analytics totals contain only a date, a predefined action code, and a total count. The site has no automatic deletion date for these totals. It uses them to compare long-term site use. They cannot be tied to a visitor, search, or page.
05 · Questions and changes
Questions or trouble deleting a report
Use the correction form with /privacy as the page URL. Include the relevant private reference. Do not include the private deletion code in a new report.
Material changes to this policy will be dated here. Current policy revision: October 14, 2026.