Telemetry and privacy

Air Jam records visits to a bounded page path, selected product actions such as opening the quick start or entering the Arcade, a normalized referrer host and campaign values when present, the deployment environment, and event timestamps. The server may infer a broad human, bot, or agent class and an allowlisted agent family from request headers.

A random identifier groups events only within the current browser page context. It is held in memory and disappears when that context ends. It is an approximate browsing-session measure, not a durable identity or a count of unique people.

Air Jam does not persist raw IP addresses, full user-agent strings, full URLs or query strings, raw referrers, email or account IDs, search text, arbitrary metadata, or browser fingerprints in this telemetry system.

Telemetry does not use cookies, local storage, or session storage. A transient request-derived key may rate-limit abuse, but neither the address nor that key is stored as telemetry.

Air Jam’s policy is to retain raw telemetry events for 90 days. Daily records used to avoid counting the same ephemeral session twice have the same 90-day limit after their aggregate is stable. Aggregate daily counts are retained long-term.

The deletion operation is implemented and available to Air Jam operators. Recurring enforcement belongs to Air Jam’s separately deployed operational worker; that worker is not active in production yet and must be activated and observed before the 1.0 release. Once active, a failed retention run makes worker readiness fail until a later run succeeds.

Only authorized Air Jam operators can access telemetry reporting. The product dashboard receives aggregate counts, not raw telemetry rows. Product telemetry is kept separate from account lifecycle and authoritative gameplay-usage data.

This is a precise disclosure for Air Jam’s public product telemetry, not a complete hosted-account privacy policy. Accounts, authentication providers, gameplay usage, submitted reports, and uploaded media have separate data lifecycles. Air Jam will not make broader retention, export, or deletion promises until those paths are implemented and independently proven.