Analytics and email monitoring
Optional Umami analytics
If you choose Allow analytics, our self-hosted Umami service measures broad page categories, product views, successful cart additions and checkout starts. It receives a broad source category, screen size and language. The server processes your connection IP and browser user agent to derive identifiers that rotate daily and approximate device, browser and location information. Raw IP addresses and user-agent strings are not stored in Umami analytics records. Estimated visitors are not identified customers or exact people, and public events can be forged. We send no names, email addresses, telephone numbers, order identifiers, payment references, complete URLs, query strings or form values. Account, order-receipt and token-link pages are excluded. No replay or advertising tracking is enabled.
Your analytics choice
Optional collection starts only after you allow it. A first-party cookie named peptpro_analytics_choice remembers allow or decline for six months; it contains no identifier. Use Analytics preferences in the footer to change your choice. Browser Do Not Track and Global Privacy Control disable optional collection. Umami uses signed collection identifiers in page memory, not persistent browser storage. Withdrawing permission stops future collection; previously collected anonymous statistics remain until expiry. The automatic aggregate counters below operate separately.
Umami retention
A daily maintenance job removes optional analytics records older than 90 days and expires private backups after seven days. Expired records can remain in backups for up to seven additional days. Cleanup is bounded; failed runs or a backlog can delay expiry. Maintenance failures pause optional collection until resolved. Analytics access is restricted to authorized business users. Shopping, payment confirmation and fulfilment do not depend on Umami being available.
Automatic aggregate counts
The store automatically counts page views and actions in aggregate. These separate aggregate counters do not set or read an analytics cookie, create a visitor or session identifier, or store an analytics preference in browser storage. Counts are not linked to individual people and cannot be used to retrieve an individual browsing history. Ordinary cart, account and checkout cookies remain separate store features.
What analytics counts
We count page views, product link clicks, cart opens, checkout link clicks, support link clicks and successful cart additions. Counts are grouped by UTC day, action, broad page category, public product number and broad source category such as search or social. The browser derives the source category locally. We do not put complete page URLs, query strings or form contents in event requests, and those requests omit the Referer header.
What the analytics records exclude
No visitor or session IDs, browser fingerprints, raw IP addresses, user agents, email addresses, order details or message contents are stored in the separate aggregate counter records. Requests still need ordinary web-server processing to reach and secure the site. For collection abuse protection, the server briefly derives a rotating collision bucket from the connection IP; it stores only one of 64 bucket numbers, a minute and a count, not the IP or its hash. A global minute counter also limits traffic. No advertising tracking is enabled by this feature.
Retention and limits
The reporting and retention window is 90 UTC days. A daily background task removes older aggregate counters in bounded batches; cleanup may complete later if the site is inactive or a backlog needs additional batches. Storage is capped at 100,000 aggregate rows. At capacity, existing rows can still increase but new combinations are omitted until space is available. Reporting identifies known collection gaps. These are action counts, not unique people or session conversion rates. Rate limits, blocked requests and forged public events can affect the counts.
Separate email monitoring
The store separately records daily operational counts of email submissions accepted by its mail transport and submission failures. These counters never receive or store recipients, subjects or message contents. Accepted submission does not establish delivery, opening or reading. Email counters use the same aggregate retention and storage limits.