Data collection

The crash reports and usage data Hoy can send to Cua: the switches, the exact payloads, how they are sent, and how to preview or turn them off.

Hoy can send Cua two kinds of data, each controlled by its own switch (EULA v2.2, section 12). Both switches are on by default, and both can be turned off before the first launch, so nothing is sent from the first start. Turning either off changes no feature.

Only Hoy's background service sends, and only from an installed release. Each switch is read when the data would be sent, so turning one off takes effect at once, with no restart. Guest contents are never collected.

The switches#

SwitchEnvironment variableConfig key (<home>/privacy.json)hoy config name
Crash reportsHOY_CRASH_REPORTScrash_reportscrash-reports
Usage dataHOY_USAGE_DATAusage_datausage-data

Off spellings: off, false, no, 0, disabled. On: on, true, yes, 1, enabled. An unknown value is ignored (the setting stays on).

The switches every Cua program honors (Cua Driver, the cua CLI and SDKs, the Cua Spaces app) turn both off too:

SwitchScope
DO_NOT_TRACK=1 (anything but empty, 0 or false)This environment. Wins over everything, including the HOY_* variables.
CUA_TELEMETRY=0 (also the older CUA_TELEMETRY_ENABLED=false and CUA_TELEMETRY_DISABLED=1)This environment.
cua telemetry off ([telemetry] enabled = "off" in $CUA_HOME/config.toml, default ~/.cua/config.toml)This Mac's user account. Hoy reads it when it would send.

They only turn data off: CUA_TELEMETRY=1 does not turn on a switch you turned off for Hoy.

Precedence, as in Cua Driver: DO_NOT_TRACK, then the HOY_* variable, then CUA_TELEMETRY, then cua telemetry off, then Hoy's config file, then the default (on). Hoy's background service runs from launchd and does not see your shell's environment, so an environment variable reaches it only if it was set for the install (the installer then saves it in the config file) or for the service itself. hoy config show reports the switches as the shell you run it in sees them.

Turn data off#

Before the first launch, any of:

# 1. at install time (saved to the config file before Hoy first starts)
curl -fsSL https://hoy.cua.ai/install.sh | HOY_TOKEN=... HOY_CRASH_REPORTS=off HOY_USAGE_DATA=off bash
curl -fsSL https://hoy.cua.ai/install.sh | HOY_TOKEN=... DO_NOT_TRACK=1 bash     # both off, the same way
# 2. the config file, in the Hoy home (default ~/Library/Application Support/hoy)
echo '{"crash_reports": false, "usage_data": false}' > "$HOME/Library/Application Support/hoy/privacy.json"
 
# 3. the command (creates the home if needed)
hoy config set crash-reports off
hoy config set usage-data off

hoy config show prints both switches, where each setting comes from (default, file, environment, do_not_track, environment_shared or shared_config, the names Cua Driver's telemetry status uses), and the sender (sender: active and the endpoint host). hoy config get <switch> prints on or off.

Preview what would be sent#

hoy config preview usage-data
hoy config preview crash-reports

These print the exact request the next usage report, or the latest crash report, would send. They send nothing.

Usage data: exact payload#

Counts and versions only. One JSON object, sent at most once a day:

{
  "schema": 1,
  "hoy_version": "0.16.0",
  "macos_version": "26.5.2",
  "mac_model": "Mac16,1",
  "key_id": "acme",
  "counts": {"vm_start": 4, "vm_stop": 4, "snapshot": 1, "restore": 1, "fork": 0, "image_create": 0},
  "errors": {"refused_cap": 1}
}
FieldMeaning
schemaPayload version, an integer.
hoy_versionHoy's version.
macos_versionThe host's macOS version.
mac_modelThe host's model identifier (hw.model).
key_idThe license key's customer_id, if a key is installed. The field is absent otherwise.
countsNumber of times each feature was used since the last send: vm_start, vm_stop, snapshot, restore, fork, image_create.
errorsNumber of error events by short code, only for codes that happened: refused_cap (a start refused by the 2 macOS VM limit), refused_memory (refused for host memory), start_failed, snapshot_failed, restore_refused, fork_failed, image_create_failed. Codes only, never messages.

Not in it: VM names, image names, file paths, user or host names, IP or MAC addresses, command lines, hoy exec input or output, anything from inside a guest.

The counts are kept on the Mac in <home>/usage-counts.json until the next report, which empties it. Nothing is counted while usage data is off, and turning it off drops what was counted. The first report goes out a few minutes after Hoy first starts. After that, at most one every 24 hours (plus up to an hour, different on each Mac).

Crash reports: exact payload#

Sent when a Hoy component crashes, once per crash:

{
  "schema": 1,
  "hoy_version": "0.16.0",
  "macos_version": "26.5.2",
  "mac_model": "Mac16,1",
  "key_id": "acme",
  "component": "hoy",
  "exception": "SIGSEGV",
  "stack": ["hoy+0x1a2c4", "hoy+0x3f9a0"]
}
FieldMeaning
componentThe Hoy program that crashed: the hoy command, the background service or the VM engine.
exceptionThe signal or exception name.
stackSymbol names and offsets of the crashing thread inside Hoy's own binaries: <component>`<symbol>+0x<offset>, or <component>+0x<offset> in a binary without symbols (release binaries carry none). At most 64 frames. No arguments, no register or memory contents, no frames from other libraries, no guest memory.
the other fieldsAs for usage data.

Hoy does not install a crash handler. Its background service reads the crash reports macOS itself writes for your user (~/Library/Logs/DiagnosticReports), picks the ones from Hoy's own processes, and takes from each only the fields above. It looks about once a minute, so a crash of the service itself is sent once it runs again. Each crash is sent once, at most 10 a day. A crash from before Hoy first looked, or from while crash reports were off, is never sent, even after you turn them back on.

How it is sent#

Each report is one HTTPS POST to https://eu.i.posthog.com/capture/, the EU data region of PostHog, the product analytics service Cua uses for its other Mac tools. The body is the payload above as the event's properties, inside the envelope the service needs, and with the property names every Cua product's events share:

{
  "api_key": "<Cua's public project key>",
  "event": "hoy_usage_daily",
  "distinct_id": "key:acme",
  "properties": {
    "schema": 1, "hoy_version": "0.17.0", "macos_version": "26.5.2", "mac_model": "Mac16,1", "key_id": "acme",
    "counts": {"vm_start": 4, "vm_stop": 4, "snapshot": 1, "restore": 1, "fork": 0, "image_create": 0},
    "errors": {"refused_cap": 1},
    "product_version": "0.17.0", "os_family": "macos", "os_major": "26", "$lib": "hoy", "$lib_version": "0.17.0",
    "$process_person_profile": false,
    "$geoip_disable": true
  }
}
Envelope fieldMeaning
api_keyCua's public project key. It can only add events, not read them.
eventhoy_usage_daily or hoy_crash_report.
distinct_idkey: and the key_id when a license key is installed. Without one, anon: and a random id made new for every report, so two reports cannot be linked. Hoy keeps no installation id.
product_version, os_family, os_major, $lib, $lib_versionThe same facts again under the names Cua Driver's events use, so one query covers both: product_version and $lib_version are hoy_version, os_family is always macos, os_major is the first number of macos_version, $lib is always hoy. Nothing new about your Mac.
$process_person_profile, $geoip_disableAsk the service not to build a profile and not to look up a location from the request's IP address.

The request comes from your Mac's IP address, as any request does. Hoy adds no address of its own. It waits at most 3 seconds (the same budget as Cua Driver), runs on its own thread (no VM operation ever waits for it), and is tried once. If it fails (offline, DNS, TLS, a timeout, an error answer) that report is dropped, not kept for later. Nothing else is queued, so the data on the Mac never grows beyond the counts file and a small <home>/telemetry-state.json (when the last report went, which crash reports were handled).

A copy of Hoy that is not an installed release never sends. To see what would be sent without sending it, run hoy config preview.

Update check#

Separate from the two switches above, and not telemetry: once a day Hoy asks the Hoy release API whether a newer release is out (see Update and rollback). It sends the installed Hoy version, the update channel and your download token (in a header), from your IP address. It sends nothing about your Mac or your VMs. The service keeps no per-check record. Turn it off with hoy config set update-check off or HOY_UPDATE_CHECK=off.