Privacy Policy

Zilix ("Zilix," "we," "us," or "our") provides a local daemon, a desktop application, an organization control plane, and a web app served by that control plane (collectively, the "Service") that let a developer run coding agents on their own machine under policy and human approval. This Policy explains what data the Service collects, why, how it's protected, and your rights over it.

By installing, pairing with, or otherwise using the Service, you agree to the practices described in this Policy. If you do not agree, do not use the Service.

1. Who this applies to

This Policy covers everyone who interacts with the Service in any capacity:

• individual developers who install the desktop application and its daemon;
• anyone who binds a remote device to a daemon through an organization endpoint;
• visitors to Zilix's websites, documentation, and download pages;
• members and administrators of an organization that has enrolled a device.

Rights-specific sections (GDPR for the EEA, UK and Switzerland; CCPA/CPRA for California residents; children's privacy) are part of the sections still in legal review. Until they are published, contact us to exercise any of those rights and we will honour the request.

2. The short version

• Your source code stays on your machine. The daemon runs locally; agent sessions, files, and terminals stay on your hardware. Remote clients talk to your daemon over an end-to-end encrypted channel — an organization endpoint may route that traffic but cannot decrypt it, and Zilix has no server that stores, indexes, or can read your code.
• We collect a small amount of product and crash telemetry (stack traces and event metadata, scrubbed of anything that looks like a secret). It is on by default and you can switch it off entirely by setting ZILIX_TELEMETRY=0.
• Using zilix on your own requires no account at all. If your employer enrols your machine in an organization, that organization receives your identity and device metadata and the audit and spend records created after enrolment — not your prompts or your code.
• We do not sell your data. We do not run advertising. We do not build cross-app profiles of you.
• The Service is not intended for processing protected health information (PHI) or other regulated health data. Redaction in the Service catches secret-shaped values (API keys, tokens, credentialed URLs) — it does not detect or de-identify PHI, and you should not route it through the Service today.
• Everything below explains exactly what, why, and how you can opt out or delete it.

3. Data we do not collect

Because this is unusual for a developer tool and worth stating plainly, before listing what we do collect:

• We do not collect, transmit, or store your source code, repository contents, terminal output, or file contents on any Zilix-operated server. All of that stays on the machine running the daemon and travels only across the end-to-end encrypted channel between your own devices. Where an organization endpoint is hosted by us, it brokers that traffic as ciphertext and holds organization records — users, devices, policy, audit events and spend rollups — but never the contents of a session. Organizations can also self-host that endpoint; no organization feature requires our hosting.
• We do not run a cloud build, cloud agent execution, or cloud storage service that your code passes through.
• We do not use your code, prompts, or agent conversations to train any model, ours or a third party's.
• We do not sell, rent, or trade personal information to data brokers or advertisers.

4. Data we collect, and why

4.1 Device identity data (local-first)

To bind a remote device to your daemon, the Service generates and stores:

• an ed25519 device identity keypair, and
• a bearer token authorizing that device.

These live in the browser's non-extractable key storage on a remote device, and in the daemon's local configuration directory on your own machine, written owner-only. They are never transmitted to Zilix.