guide

Data Flow & Privacy

@zlogic.run has no project-owned cloud API, control plane or proxy service. A normal turn flows like this:

Data flow

Your message → Local Agent runtime → Your configured Provider → Streaming response → Local storage

Everything happens locally: message assembly, context construction, tool execution, file I/O, conversation persistence.

What we collect

@zlogic.run does NOT:

  • Upload conversations, code, prompts, keys or usage
  • Use third-party CDNs, Google Fonts, GitHub API or analytics scripts
  • The site is fully static — no external services

The single exception: the desktop app (zlogic Desktop) sends one anonymous install receipt to zlogic.run on every launch — a random install ID, the app version, OS and CPU architecture, with no IP address and no personal data — to count installations. See the privacy & credits page. The CLI and this website never send it; delete telemetry.yaml in the config directory and restart to stop.

What's stored locally

  • Conversation history: SQLite database in the state root (~/.local/state/zlogic/state.db by default)
  • Configuration: config.yaml, models.yaml, env.yaml and policy.yaml under the config root (~/.config/zlogic/)
  • Keys: in your OS keyring (macOS Keychain / Windows Credential Manager / Linux Secret Service) or environment variables — never in files
  • Usage records: call counts, tokens and cost estimates
  • Grants: project-level authorizations persisted to disk
  • Checkpoints: local history snapshots in a shadow object store — your git is untouched
  • Memory: durable facts you (or the agent, with your approval) chose to persist
  • Daemon devices: paired-device records live under ~/.local/state/zlogic/daemon/ — only token hashes are stored, never the plaintext token

Deleting a conversation removes the local record. There is no cloud copy.

License

The CLI and the agent runtime are open source under Apache-2.0, developed in the public zlogic repository and complete enough to build, run and modify. The desktop app, the remote daemon and the closed-source tool packs that ship with them are distributed as binaries only, and are built on the crates published there. Third-party open-source components that the product builds on keep their own licenses (see the credits page).