Your setup.
Your privacy choices.

Updated November 1, 2026

Analytics is optional and off until you allow it. Your choice does not affect the planner, compatibility checks, advisor, garage, or shared links.

What optional analytics records

We measure section views, planner starts, valid advisor requests and successful results, successful setup saves or updates, and deliberate gear shopping clicks. Manufacturer clicks can include a public catalog model key and the section used. We may record short campaign labels (UTM source, medium, campaign and placement), an external referring website’s hostname, and a broad screen-size group.

Random browser IDs expire after 30 days; visit IDs renew after 30 minutes of inactivity. The server stores hashes of these IDs. Counts estimate browsers and visits, not verified people. Bots that imitate ordinary visitors may still be counted. Blockers, opt-outs and declined consent reduce recorded traffic. Campaign reports start with this release; historical attribution is unavailable.

What analytics leaves out

We do not send setup names, selected outfits, rider measurements, advisor notes, trip details, form text, email addresses, complete referrer URLs, query strings, or shared-plan URL fragments to the analytics database. No third-party analytics provider receives these events. Network infrastructure necessarily handles request metadata; STANCE does not save IP addresses or user-agent strings in its analytics table. A short-lived hashed address bucket in server memory limits abuse.

Control collection

Choose No thanks or Allow analytics on the optional notice. Use Analytics preferences in the planner footer to change your choice. Turning analytics off stops new collection and clears local analytics IDs. It does not delete saved gear or already recorded server events. Browser Do Not Track and Global Privacy Control take priority over consent.

If browser storage is blocked, your choice and random IDs may last only on the current page. Signed-in owner visits are excluded unless the owner deliberately enables a separate test journey. The owner can also use ?stance_qa=1 for a persistent browser QA exclusion and ?stance_qa=0 to clear that exclusion; neither grants consent.

Storage, access and retention

Events stay in STANCE’s first-party Cloudflare D1 database. Reports require the site owner’s authenticated ChatGPT account. Public visitors cannot read reports. Reports cover up to 90 calendar days. Events older than 90 days are deleted in bounded batches during collection or report requests. There is no guaranteed daily background cleanup: if the site is idle, older records can remain until cleanup next runs.

Your saved gear and advisor

The garage, current setups, apparel checklists, preferences and any profile you choose to remember remain in browser storage. Clearing site data can remove those items, so export a backup first. Shared setup links encode the setup in a URL fragment; only share them with people you choose. Analytics never sends that fragment. If you choose AI-assisted advice, the advisor separately sends the profile needed to answer that request; analytics records only the action and whether results were shown.