Desktop workflows
Artemis is positioned as a local-first Windows operator tool. The desktop product and its local workflow claims should be described separately from the public website and account services.
Architecture note // Information boundariesWhat leaves your PC.
What leaves your PC.
What does not claim to.
Artemis is a local-first desktop product, but not every Artemis surface is local. The website, account, billing, analytics, and error-monitoring layers use networked services and should be described precisely.
This public architecture note describes product boundaries at a high level. It does not substitute for a detailed security review, a final privacy policy, or a provider-specific data-processing agreement.
Section // 01
System boundaries
Website and account services
The public site, sign-in, account access, billing, and release information are networked surfaces. They are not offline or device-only workflows.
Analytics and monitoring
The website uses limited analytics and technical error monitoring. These systems help measure site use and diagnose failures, and they are disclosed in the privacy notice.
Operator responsibility
Operators remain responsible for account security, provider permissions, and reviewing automation behavior. Never share passwords, recovery codes, or platform tokens with support.
Section // 02
Plain-language commitments
Accurate scope
Do not market Artemis as zero-cloud, zero-telemetry, or no-trackers while website analytics, error monitoring, account, and billing services are enabled.
Version source
Do not call a build current until the Download Center, Changelog, public page, and package metadata all read from the same release record.
Security boundary
Do not request, store, or transmit passwords, recovery codes, QR data, or third-party tokens through public support paths.
Section // 03
What this page still needs
Before a production launch, publish an approved data-flow diagram, a complete provider list, technical retention rules, a security reporting method, and release-specific system requirements.
Current stance
This page intentionally states limits instead of filling gaps with technical promises that have not been verified.