Effective date: October 1, 2026
Version: 26a-2026-10-01
Last updated: October 1, 2026
Changelog: Initial standalone explanation of browser storage, analytics choices, and source-audited marketing tags.
This notice explains browser storage and similar technologies on Axiom Helm public pages and in the application. It supplements, and should be read with, the Privacy Policy.
1. Necessary storage and services
Clerk's authentication cookies/storage keep sign-in sessions and security controls working. Clerk SDK cookie names and durations have not been independently verified, so this notice does not enumerate names that have not been confirmed. Hosting and routing providers may use their own strictly necessary request/security storage. These are not optional analytics and do not depend on the analytics preference.
Public pages load Google Fonts; the contact form uses Cloudflare Turnstile for necessary anti-abuse checks. These services may receive network/browser request information. They are not PostHog analytics or the planned customer-site marketing tag and are not gated on accepting optional analytics.
2. Optional analytics and identification
- Google Analytics 4: measures page views on public marketing pages after optional analytics consent. It is not loaded in authenticated app or admin areas. Browser Do Not Track and Global Privacy Control signals block this tag. Withdrawing consent disables it and reloads the document.
- PostHog: loads only after the visitor explicitly chooses to allow optional analytics. A decline stops optional analytics and clears PostHog identifier cookies and local storage in that browser.
- Snitcher: may identify a company from a public-page request's network IP. It runs only on eligible public marketing pages and the exact root sign-in/sign-up pages after the shared analytics choice and the current Snitcher notice are recorded in the same flow. Automatic form-field tracking is disabled. A successful eligible public form or first-party voluntary sign-up may share only approved name/email/company fields when the required consent is active. No credentials, authentication secrets, or private-app data are sent.
- Replit published-traffic analytics: may be separately enabled by an operator in publishing settings. It is cookieless infrastructure request analytics and is not controlled by the browser's optional analytics choice.
There is no separate Snitcher prompt or second Accept button. Reopen the same choices at any time using . Declining optional analytics keeps PostHog and Snitcher off in the browser. These choices do not disable necessary authentication, fonts, contact abuse protection, hosting traffic analytics, or the analytics services of a provider whose account you choose to connect.
3. Browser privacy signals
Do Not Track (DNT) is a strict opt-out and is not overridden by a later acceptance. Global Privacy Control (GPC) defaults optional processing off. On the public root site only, an explicit current Allow choice may override GPC for PostHog and Snitcher, as previously specified by the operator. The choice is not automatic consent, is versioned with the Snitcher notice, and can be changed later. A planned 25-series customer-site tag is not mounted and is not covered as a live tracker.
4. Storage keys and duration
On the public site, known preference keys include axiom_cookie_consent, helm-tag-consent-v1, axiom_snitcher_consent_v1, axiom_gpc_posthog_explicit_accept_v1, and axiom_gpc_root_snitcher_explicit_accept_v1. sidebar_state controls a user interface preference and is stored for seven days. Session and preference lifetimes depend on the feature and browser. Cookie names for Clerk are not asserted here because they have not been verified. The planned __Host-helm_vid browser identifier and helm-tag-session-v1 storage are not live first-party tracking keys.
You can clear optional analytics by declining in preferences, clearing relevant site data in your browser, or changing your choices. Clearing browser storage may also sign you out or reset product preferences. A choice stored in a browser does not automatically apply to another browser or device.
5. Storage controlled by third-party connections
After connecting Google, Microsoft, Stripe, a social service, or another provider, that provider may set or use its own cookies in its own service. This site does not control those cookies or browser settings used on an external provider's domain.
To exercise a personal-information right or request account data removal, use Data Export & Deletion. Cookie choices do not delete a server-side account, connected-provider data, or previously transmitted data.
Privacy questions: privacy@axiomhelm.com. 850 Holt Drive, Bigfork, MT 59911
Changelog
October 1, 2026: Initial standalone explanation of browser storage, analytics choices, and source-audited marketing tags.