Collect less.
Explain what remains.
Stratum Praxis uses lightweight analytics to understand routes and product interactions. Free browser utilities are designed to avoid collecting more personal information than the task requires.
Analytics currently used
The public site uses PostHog for selected analytics. The current site configuration disables automatic event capture, automatic page-view capture and session recording. Stratum sends explicit events for things such as page/funnel views, route clicks, result visibility, conversion steps and performance/quality signals.
An anonymous browser identifier and first/last-touch attribution data can be stored in localStorage or sessionStorage. Attribution can include UTM parameters, landing path and a sanitized referrer origin/path. The analytics code is configured not to send purchaser email or email fields as event properties.
Checkout and third-party links
When you choose an existing paid route, checkout can occur on a third-party service such as Stripe. The site may add an anonymous route reference and UTM attribution parameters to a Stripe checkout URL so Stratum can connect a purchase path to the page or campaign that led to it.
Payment providers and other external services process data under their own privacy terms. Stratum does not control the data practices of external sites you choose to visit.
Browser utilities
Many Stratum utilities are designed to calculate or compare information directly in the browser. A tool may use localStorage to preserve state or preferences. Where a tool fetches external public data, or where a page has a different data flow, that behavior should be stated in the interface.
Your controls
You can clear site data through your browser controls, including localStorage and sessionStorage. Browser privacy tools can also restrict third-party scripts or storage. Disabling those features may reduce attribution or saved-state behavior, but core public pages should remain readable.
Changes
This page describes the current public-site behavior and may be updated when analytics, checkout, storage or connected services materially change. Product-specific handling disclosed on a product or checkout page takes precedence for that interaction.