Skip to content
Shelzo

Privacy and statistics

Shelzo separates daily usage statistics from optional crash reports. You can control both in Settings › General › Privacy.

What the daily ping contains

Usage statistics are on by default in configured builds. The app reports a random installation ID, app version and build, macOS version, processor architecture, beta status, installed engine names, and counts for sessions, chats, terminals, turns, computer actions, routine runs, and enabled connectors.

Activity counts describe the previous 24 hours; the connector count describes currently enabled connectors. The payload also includes its schema version. A stable random installation ID lets successive pings be associated with the same installation. It is not derived from your hardware or account.

The ping contains no prompts, replies, code, file paths, folder names, chat titles, account identifiers, emails, license keys, or credentials. For example, it can report that two engines are installed and several turns ran, but not what you asked them to do.

Turn statistics off

  1. Open Settings (⌘,).
  2. Select General and find Privacy.
  3. Turn off Send anonymous usage statistics. This stops app pings; turning it back on resumes their schedule.

Update checks and downloads still have server-side request counts. These use daily-changing IP hashes rather than storing raw IP addresses in the statistics records. Statistics records are retained for 90 days. See the privacy notice for the full description.

Crash reports

Send crash reports is a separate, optional setting and is off by default. Configured shipping builds use Sentry for stack traces and app version information, with code, prompts, and file paths excluded. Turning off daily statistics does not change your crash-report setting.

Your engines and connectors

These statistics settings do not change the data sent to your chosen engine or connector to perform a task. For example, a computer-use screenshot is an engine tool result, not part of the daily ping.

If it fails

A disabled crash-report control can mean the build has no crash-report configuration. Read its explanation. Development builds without a statistics endpoint do not send pings. If unsure which collection is enabled, check both Privacy switches separately.