Website analytics
The public website initializes limited analytics to understand page use and improve the site. This is not the same as an offline desktop product claim.
Artemis should describe its information boundaries plainly. The desktop product is designed for local-first workflows, while the public website, member account, billing, analytics, and error-monitoring surfaces use networked services.
The public website initializes limited analytics to understand page use and improve the site. This is not the same as an offline desktop product claim.
The website records technical error and performance information to diagnose faults. Depending on the event, this can include page path, browser context, event details, and a session identifier.
Member sign-in, account access, and payment workflows use networked service providers. The relevant provider terms and privacy notices apply to those services.
Artemis describes its desktop workflows as local-first. That does not mean every Artemis surface is offline or that no data ever leaves a device.
This notice does not make a zero-telemetry, zero-cloud, or no-trackers promise. Those statements would be inaccurate while website analytics and error monitoring are active.
Never submit passwords, recovery codes, one-time codes, QR data, or platform tokens in a support request. Those are account secrets, not diagnostic details.
A production privacy policy needs a verified legal contact, a complete provider list, data categories, purpose and retention detail, user-rights process, international-transfer terms, and an effective date. Those terms are not yet published here.