No browser tracking tools
This frontend sets no cookies, uses no local storage, and loads no third-party analytics, tracking pixels, scripts, fonts, or images. It does not offer accounts, a mailing list, or a contact form.
Page views and outbound clicks
Anonymous page-view reporting is enabled. After a successful public HTML page render, the server sends the page path and, for a review, its article slug to the publishing service. Obvious automated visitors are skipped. Private previews do not send page-view events.
Following a product button sends its product ID to the publishing service to record an outbound click and retrieve the stored destination. These events measure page views and link clicks, not purchases, revenue, or commissions.
Event requests may include a daily rotating HMAC visitor hash, calculated on the server from the UTC date, connection IP address, and browser user-agent with a private salt. The raw IP address and user-agent are never included in the event payload. The hash allows approximate daily visitor counts; it is not a browser cookie.
Search and cached content
Search checks titles and excerpts from public article-list pages on the server. The search phrase stays on this frontend; it is not sent to the publishing API. It is present in the page URL and may appear in browser history or hosting access logs. The frontend caches public API content on disk, separated by site and token. It does not cache private previews or search phrases.
Hosting and retention limits
The web server receives connection information needed to serve requests. Its operator may keep access or error logs under its own configuration. This frontend does not create visitor logs or define a retention period for hosting logs or publishing-service events. No claim about those systems’ retention is made here.
When you visit a merchant
Product links can contain merchant tracking parameters used for affiliate attribution. The destination host is shown next to the button. Merchants and source sites have their own privacy policies and may set cookies after you leave. This frontend sends no referrer header from its pages.