Privacy policy

Effective October 4, 2026.

Your desktop profile

Settings, service definitions, isolated browser sessions, mail caches, credentials, notifications, and diagnostic logs stay in your computer’s application data. Chattium does not upload your desktop profile to a synchronization database. Service sign-ins and content requests go directly to each provider under its own privacy policy. Operating-system protected storage is used for secrets where supported. Profile exports are encrypted with your passphrase and exclude computer license authorization and its private key.

Computer licensing

Activation sends the purchaser email, purchase credential, a Chattium-specific hash of the operating system’s computer identifier, a generated device public key, and the platform to the licensing server. Raw hardware identifiers and the device’s private key are not sent. The server stores the assigned computer, subscription/trial or perpetual beta status, authorization dates, transfer history, and support/admin actions. Account-level trial assignment and consumed history prevent a fresh trial when creating more licenses, reinstalling or transferring.

The app stores its device private key, purchase credential, signed authorization, and a local clock checkpoint in operating-system encrypted storage. It contacts licensing services on activation, release, billing requests, renewal confirmation at expiration, or recovery from an abnormal clock change. There are no routine online licensing checks between activation and expiration. These licensing requests do not include service messages, mail content, browsing history, or AI conversations.

Payments and emails

Stripe Managed Payments processes explicitly authorized subscription checkout, payments and billing management under its privacy policy. Chattium stores Stripe identifiers and status, but does not receive full card numbers. Hosted Supabase Auth delivers account sign-in codes through its configured SMTP service; direct Resend helpers deliver activation, billing and administrator verification codes. Those email delivery providers receive the recipient address and email content for delivery. Stored delivery content is encrypted. Verification codes are single-use, time-limited, and subject to attempt limits.

Privacy & analytics on this computer

Daily aggregate analytics are enabled by default and linked to your verified-email account and registered computer. They are not anonymous. Turn collection off under Settings → Misc → Privacy & analytics. Opt-out clears unsent local summaries and synchronizes the computer-wide preference when connected. Previously uploaded history is retained indefinitely. Reenabling starts a new stream and collects future activity only.

Summaries contain fixed built-in service IDs and configured instance counts, a generic custom-website count, daily yes/no manual built-in service use and daily feature use. A service placed in several workspaces counts once. Reliability totals cover launches, confirmed crashes separately from unclean exits, fixed-ID service load failures, native mail connection and terminal startup failures, encrypted import/export and update outcomes. Startup and service-load durations use coarse buckets.

Analytics exclude message and mail content, AI conversations, provider account identities, emails, device names, raw hardware identifiers, license keys, custom website names or URLs, titles, commands, paths, raw errors, logs and individual action timestamps. Local summaries are bounded and stored with operating-system encryption. The first summary upload occurs four hours after each app launch, then every four hours using elapsed time, with quiet retries while offline. Preference changes synchronize sooner. No startup or exit summary flush occurs. A separate limited reporting credential cannot activate or renew a license or change billing.

Operational logs remain local. The workspace profile is not uploaded to a Chattium synchronization service. Licensing, account and billing requests remain separate from optional analytics.

Website and admin security

The hosting provider may process IP addresses, URLs, browser information, and request times for reliable delivery and security. Hashed request identities are used for rate limiting. The private admin page uses an essential, secure session cookie and records license-management actions for accountability. The site does not include advertising pixels. App aggregate analytics follow the separate computer preference described above.

Retention and requests

Local data remains until you delete it. Licensing and trial records are retained to support paid terms, transfers, fraud prevention, and applicable accounting obligations; perpetual beta records remain while the license exists. Expired verification sessions, rate-limit buckets, and delivered email content are periodically removed. Stripe and Resend retain records under their own policies. Contact privacy@chattium.com to request access, correction, or deletion of server records. Deleting licensing records may prevent activation or renewal, and records required by law may be retained.