Desktop update privacy notice

Effective August 16, 2026 · Beta release path

This notice covers the network path used to check for, download, and publish Agenaxy desktop Beta updates. It does not change the data path of a model or connection you separately choose for your work.

What an update check sends

Update checks send the app version, macOS, processor architecture, event time, a request event UUID, and the app's existing randomly generated installation ID. The installation ID is reused from Agenaxy's existing installation identity; the updater does not create a second identifier.

The request does not include your account, projects, models, prompts, files, paths, tasks, or other user content. Update checks are mandatory operational requests and continue when optional product telemetry is disabled.

Why the installation ID is used

The service records at most one update-reachability row per installation per day, together with app version, system, and architecture. This lets us see whether an update can reach installed Beta apps. It is reported separately from optional usage telemetry and the existing app.active metric.

Downloads and network addresses

Release metadata and packages are delivered through Cloudflare Pages and R2. Like any internet service, Cloudflare's network receives the connecting IP address and normal transport metadata in order to route and protect the request. Agenaxy does not add the IP address to the update payload and does not write it to the update activity table or application logs.

Verification on your Mac

Agenaxy downloads only the package for the current architecture. The app verifies the complete downloaded archive against its embedded Tauri updater public key before offering installation. Partial downloads may remain in the app's macOS cache so an interrupted download can resume.

Questions

Contact dev@agenaxy.ai.