Telemetry and data

Axorith uses PostHog for website analytics and optional desktop product telemetry. The website and desktop app keep separate visitor identities.

Website analytics

When you visit axorith.com, the PostHog Web SDK records page views, page exits, visit sessions, Web Vitals, referrer source categories, and validated UTM source, medium, and campaign tags. Pages are reduced to fixed categories such as home, modules, and privacy. Full page and referrer URLs, domains, ad click IDs, UTM content, and UTM search terms are removed before events are sent. It also records clicks on download and GitHub links. Download click events include the CTA location and Windows platform; a release version is included only when the site actually knows it. PostHog may infer coarse location from network metadata.

The website uses PostHog's browser identity. Axorith does not use IP addresses, user-agent matching, fingerprinting, or other heuristics to connect a website visitor with a later desktop installation.

Desktop telemetry

Usage telemetry is enabled by default and can be turned off in the app's Privacy settings. The setting is shared by Client and Host. Updates read the saved preference, and a fresh install keeps the existing default.

When enabled, the desktop app sends Axorith and operating system versions, application lifecycle events, preset and module IDs and built-in module types, session IDs and lifecycle, commitment and break configuration, schedule changes, changed settings categories, onboarding counts, update and installation outcomes, and structured error details. A hashed device identifier is used as the existing desktop PostHog identity. Installer and first-launch events share a separate random installAttemptId for installation funnel analysis.

Error events contain an exception type, stable fingerprint, subsystem, operation, severity, handled/fatal status, and limited sanitized method names. Repeated errors are rate-limited and summarized.

Information we do not send from the desktop app

Desktop telemetry does not include preset names, custom module or action names, setting values, filesystem or executable paths, process names, command-line arguments, URLs, domains, Home Assistant entity IDs, access tokens, secrets, raw exception messages, or full stack traces. Axorith does not send IP addresses as event properties. PostHog may infer coarse location from network metadata.

PostHog and identity

Website and desktop events go to the same Axorith PostHog project, but use separate identities. The website does not use the desktop device identifier, and installAttemptId is a funnel correlation value rather than an identity.

For questions, contact mail@axorith.com.