Verified 2026-08-05. Agent Island v1.7.1 requires no Agent Island account and sends no product telemetry. Claude Code and Codex session content stays on the machine. This page separates that promise from provider usage requests, release checks, and consent-based website analytics.
What the desktop app reads
Agent Island reads the local files that Claude Code and Codex already write. The status layer looks for session identity, event type, event time, and enough turn state to distinguish working, your turn, error, stalled, and idle. The local cost layer can read token categories and model identifiers from the same provider records.
The app does not need the prompt text to display a provider state. It also does not need an Agent Island account, hosted workspace, or transcript upload service.

What stays on the device
Session scans, reminder delivery keys, local usage events, report-card data, and preferences remain on the machine. Deduplication keys prevent one local event from being counted or announced repeatedly. They are bookkeeping for the desktop app, not a server-side user profile.
Sharing is explicit. If the user exports a report card, copies an image, opens a public GitHub issue, or sends a diagnostic file, that user action moves information outside the app. Agent Island does not treat an export button as permission to upload the underlying transcript.
Which network requests can occur
Some features need a network connection. When usage reporting is enabled and local provider credentials are available, the app can ask the relevant provider for quota or reset information. The request goes from the device to that provider. It is not routed through an Agent Island account.
The app can also check the public GitHub release surface for updates. On macOS, Sparkle verifies update metadata and the release signature before installation. These update and provider requests are different from product telemetry because they serve a user-visible function and are sent to the named service.
What no product telemetry means
Agent Island does not send session state, prompts, transcripts, token history, model history, alert activity, feature usage, or a device analytics profile to an Agent Island backend. There is no Agent Island sign-in requirement.
This claim does not cover the privacy practices of Anthropic, OpenAI, GitHub, Homebrew, Microsoft, Vercel, or any site a user chooses to open. Their requests and accounts remain governed by those services.
The website has a separate consent boundary
The public website is deployed on Vercel. Google Analytics loads only after a visitor selects Allow analytics. It measures website navigation and does not receive Claude Code or Codex session data from the desktop app. Advertising signals and ad personalization are disabled.
Desktop privacy and website analytics should not be collapsed into one vague claim. The desktop product has no product telemetry. The website has optional, consent-based visit analytics.
How to audit the boundary
- Read the public source and identify every networking client.
- Map each request to a visible feature such as provider usage or update discovery.
- Run the desktop app with a network monitor and exercise one feature at a time.
- Inspect local data directories before and after a session scan.
- Keep website analytics tests separate from desktop runtime tests.
An audit should record the version, platform, enabled settings, observed hosts, and request purpose. Absence of a request in one short run is evidence for that run, not proof about every future release.
Report a privacy issue safely
Open a GitHub issue with the operating system, Agent Island version, the unexpected host or behavior, and reproduction steps. Remove tokens, credentials, full transcripts, personal file paths, and payment information before posting. A private disclosure path should be used when the report contains a security vulnerability.
Read the concise privacy notice, the capability matrix, or inspect the public source.
← All documentation