Privacy

Private by default. Clear by design.

Zyron stores workspace history on the computer running the workspace. Optional account features, connections and mobile access use additional services as described below. Stable and Beta product analytics are off by default. Zyron Remote from .18 and iPhone/iPad from build 139 share limited usage data by default, with a local switch to turn it off. Zyron Beta has separate, always-on crash and release diagnostics.

Where your data lives

Workspace chats, projects and operational state live in a local SQLite database on the host computer. Desktop and mobile clients also keep local history, drafts and caches. A connected device can access that host with your authorization. Optional Zyron account features store profile information, private usage aggregates and saved Inbox recaps in our account database on PostgreSQL/Supabase, accessed through our Cloudflare API. These saved account records are separate from product analytics.

Where your prompts and code go

The host computer connects directly to the provider you chose — Claude, Codex, OpenCode, Cursor, Antigravity, Grok, Droid, and so on — using your own existing logins. That provider receives the prompts and code needed for the session, governed by their privacy terms. Zyron does not proxy normal provider requests through its own model service. For managed remote connections, Cloudflare transports chat and file traffic between your approved device and the host before the host contacts the provider.

Optional accounts and connections

Local desktop use does not require a Zyron account. Signing in enables account features and managed device connections. Authentication uses WorkOS; the account API and managed tunnels use Cloudflare. Approved devices can access the selected host, including its chats and files, through that connection. You can revoke device access. Information you choose to publish on your profile is public; saved Inbox recaps are private.

Product analytics and Remote diagnostics

Stable and Beta product analytics are off by default. Zyron Remote from version 1.0.6-remote.18 and the native iPhone/iPad apps from build 139 share limited usage data by default. Settings → Privacy → Share usage and diagnostics turns sharing off on that installation; an existing off choice is preserved. On Remote desktop this switch also controls crash and error diagnostics. Another computer or account does not change your local choice.

Product events use a random identifier for this installation. It is independent of your login and billing account; no account identifier or account-derived hash is sent. Active counts represent installations, so one person using multiple devices can count more than once. We do not use advertising, cross-app tracking or data brokers.

When sharing is enabled, we receive

  • Fixed event names, built-in command categories, connection outcomes and failure categories
  • A random installation identifier, event identifier and timestamp, independent of login and billing
  • Your app version, release channel, app surface and platform
  • Bounded durations and token counts, with fixed provider and mode categories
  • With host product sharing enabled, daily aggregate executions by catalogued provider/model, requested effort and outcome, with per-field token coverage

Product analytics never include

  • Your prompts, messages, or chat history
  • Your code, files, diffs, or repository contents
  • Your API keys, tokens, or provider credentials
  • Your name, email, or IP-based location profile

Raw product events are stored in Cloudflare D1 behind an authenticated dashboard and scheduled for deletion after 30 days from receipt. Cleanup uses capped daily batches; an unusually large backlog can take longer. Local queues are bounded to 500 events and seven days. Turning sharing off clears unsent events, cancels active sends and removes the local analytics identifier. Re-enabling creates a fresh random identifier without linking it through an account. The first account-free upgrade also replaces the old analytics identifier and discards its unsent telemetry, preserving your choice and workspace history. Switching off cannot recall data already received. Usage counters are best-effort observations, separate from account and billing records. Custom model and command names are reduced to fixed categories rather than sent as free text.

Beta and Remote desktop diagnostics keep known error categories, numeric source locations, process/release health and aggregate usage counters. They exclude error messages, function/file names, log excerpts and raw crash memory dumps. Diagnostic reports have separate retention. New diagnostics do not carry provider/model/execution/token data; historical rolling samples remain separately labelled until retention removes them. Extracted provider and turn usage rows are scheduled for deletion 90 days after receipt, with the same capped-batch limitation; other diagnostic event records currently have no automatic expiry. The 30-day product-event cleanup does not remove those records.

Host execution aggregates follow that computer’s own product-sharing choice, including work requested by connected phones and controllers. Completed UTC-day snapshots use catalogued model and finite effort/mode/outcome categories. Token fields have separate measurement counts: absent values are unknown, while explicitly measured zero stays zero. Daily receipt hashes expire after 14 days; anonymous day/channel counters and coverage after 90 UTC days, using capped cleanup batches. No host/account identifier accompanies those model counters. Offline, late, capped and missing-time data can leave gaps; these are observations, separate from renderer events and billing totals.

Separate Beta diagnostics

Zyron Beta sends crash, error, release-health and daily usage diagnostics automatically, using fixed categories, numeric source positions and bounded counters. They exclude prompts, replies, file contents, credentials, error prose, function/file names, log excerpts and raw crash memory. Stable does not send Beta diagnostics. Product analytics consent does not control this separate Beta path. Older installed clients used broader diagnostics; legacy text is stripped at ingestion and raw dump routes are retired. Historical storage cleanup requires a separate operator action; this policy does not claim previously received data has already been deleted. See the diagnostics documentation for its field allowlist and storage details.

Feedback you choose to send

The in-app Feedback Zyron dialog sends only when you press Submit. It includes the text you wrote, app version, operating system, provider and model, runtime modes, and session/turn status so we can understand the conditions around a problem.

Feedback context excludes chat messages, prompts, project paths, repository contents, session logs and screenshots. Feedback reports are delivered through our website and email provider to the Zyron maintainer for support and product improvement, rather than being added to an analytics profile.

Open source

Zyron is open source under the MIT license. If a sentence on this page isn't enough, you can verify every claim yourself — read the code on GitHub.

About this website

This marketing site (the page you're reading) uses privacy- friendly Cloudflare Web Analytics for anonymous, aggregate visit counts. No cookies, no cross-site tracking, no selling of data.

Last updated November 8, 2026. Questions? Reach out on X.

Download Zyron