ZackEyes
Privacy notes

Local-first by default.

ZackEyes does not require an account to show local AI coding agent status. The product is designed around your Mac, your terminal workflow, and explicit public feedback through GitHub.

01

No account required

ZackEyes can be downloaded from GitHub Releases and used without creating a ZackEyes account.

02

Code stays out of the website

The website does not upload your source code, agent prompts, terminal history, or local project files.

03

Public feedback is explicit

Bugs, install issues, compatibility reports, and feature requests are handled through GitHub Issues.

04

Analytics

The current website does not add a third-party analytics script. If analytics is introduced later, this page should name the provider and the measured events.

What leaves your Mac?

The public website and release channel use GitHub infrastructure. When you download the app, you are fetching a DMG from GitHub Releases. When you file feedback, the content you post to GitHub Issues is public unless GitHub or the repository settings say otherwise.

Network requests

ZackEyes checks GitHub release metadata and downloads installer assets. Its pricing table is bundled for offline calculation, then checked online from the public GitHub pricing.json at startup and every 24 hours. These requests fetch public data; they do not upload prompts or replies.

While a local Codex session is active and the announcement setting is enabled, ZackEyes checks the public CodexReset feed at most every five minutes. The request carries no account credentials, session data, prompts, or local paths. The provider receives ordinary network request metadata.

SSH observation and local history

Enabling a remote host opens a key-authenticated SSH connection to the host you choose. Project/path, agent, model/effort, permission-mode (approval/sandbox), tool name, state and last-activity metadata travel from that host to your Mac; prompts, replies and tool arguments do not. The separate local usage archive stores counts, bounded names, hashed identities, resumable import state and timing metadata under ~/.zackeyes/usage/ on your Mac. SSH destinations are saved in ~/.zackeyes/remote-hosts.json; credentials are handled by your existing system SSH setup. Neither feature uploads this data to ZackEyes servers.

GitHub Releases

Used for installer downloads and update metadata. The app can check the latest release endpoint and download the DMG directly.

GitHub Issues

Used for bugs and requests. Include only logs, screenshots, or project details that you are comfortable sharing publicly.

Local agent status

The product is built to surface local Claude Code and Codex CLI status in the macOS notch workflow, not to create a hosted agent dashboard.

Local files and settings

ZackEyes may use local configuration and agent hook files such as `~/.zackeyes`, `~/.claude/settings.json`, and `~/.codex/hooks.json` to connect local agent events to the notch UI.

Delete local data

First use Settings → Integrations → Uninstall Integrations… while the app is installed, then quit and remove it. Keep ~/.zackeyes to retain local data, or copy it before deletion: removing it erases Usage history, SSH host configuration, settings and existing journal files. See the uninstall guide.

Need to report a privacy concern?

Open a GitHub Issue with the ZackEyes version, macOS version, and the behavior you observed.