Privacy & measurement
What the optional site counter records
If the site owner enables the configured GoatCounter endpoint, this page records aggregate visits, campaign source/name, demo-check clicks, release-download clicks, team-pilot discussion clicks, Colab-open clicks, pipx installation-guide clicks, and field-guide demo/download clicks. The demo event contains no field contents or token counts. The checker itself remains offline.
GoatCounter's hosted service says it stores aggregate browser, operating-system, country, language, screen-width, page, and referrer counts. It processes the IP address and user-agent in memory to distinguish short sessions, but says it does not store those values or use browser cookies/local storage. The service's privacy details describe its current handling. Visitors can block the optional counter with browser privacy tools.
What is not measured
A demo-check event means someone clicked the in-browser example. It does not prove they downloaded or ran the Python tool. First CLI use and seven-day repeat use are not centrally observable in this offline product. A discussion click is not a qualified lead. A purchase is counted only after a payment provider's captured order and refunds/fees are reconciled; this site does not collect payments.
Current setup
The analytics endpoint is blank in this release, so the tracking script and all analytics requests remain disabled. Campaign links use only aggregate UTM source/campaign data; arbitrary query strings are not stored as page paths.
Questions or team-pilot requests can be shared in the public GitHub Discussions. Do not post confidential prompts, customer data, or secrets.