Skip to content

Data the CLI sends

The Awnexa CLI sends anonymous usage statistics from v0.1.0 onward, and nothing else. It calls AWS APIs (read-only) with your own credentials and stores the results on your machine. Your AWS configuration data is never sent to Awnexa or to any third party.

This page lists every field the usage statistics contain. If a field is added, it is listed here before the release that sends it.

  • They are on by default. The first time you run the CLI, it tells you that usage statistics are collected and how to turn them off, and sends nothing on that run. When you run it in a terminal, it also asks whether to keep them on (press Enter to keep them on, or answer n to turn them off). Sending starts from the next run. When the CLI runs without a terminal (for example from Claude Code, a script or CI), it shows the notice without asking.
  • The MCP server (awnexa mcp) sends only after that notice has been shown by the CLI, because its output is usually not visible to you.
  • One event is created per CLI command (or per MCP tool call). Events are sent only to Awnexa’s own backend, https://api.awnexa.net/v1/events.
  • --help, --version, runs that fail while parsing their arguments, and the telemetry command itself are never counted.

Turning them off and checking what is sent

Section titled “Turning them off and checking what is sent”
What you want How
Turn off for good awnexa telemetry disable (also deletes the install ID and unsent events)
Turn off with an environment variable AWNEXA_TELEMETRY=0 (or off / false), or DO_NOT_TRACK=1
Turn back on awnexa telemetry enable (creates a new install ID)
See whether it is on, and why awnexa telemetry status
See the events before and after sending awnexa telemetry show (unsent events and the last 10 sent)
Print events without sending them AWNEXA_TELEMETRY=debug (printed to stderr)
Field Example Notes
schema awnexa.telemetry/v1 Version of the event format
installId random UUID Random per machine. Not derived from your AWS account, user name or host name. Deleted when you turn statistics off
eventId random UUID Avoids counting a resent event twice
time 2026-11-02T03:00:00Z Rounded to the minute
awnexaVersion 0.4.1
nodeVersion 22.12 Major and minor only
os / arch darwin / arm64 Not the OS release number
interface cli / mcp
ci true / false Whether the CI environment variable is set (not its value)
sample true / false Whether the command used the sample data of awnexa init --sample (trying Awnexa, not real use)
command resources list / awnexa_overview One of Awnexa’s own command or MCP tool names
options ["--compact","--limit"] Names of the options you gave, never their values
optionChoices {"--format":"table"} Only for options whose value is one of a fixed list of choices
outcome ok / scan_incomplete / usage / user_error / aws_auth / error Kind of exit
errorCategory access_denied Category of the error (for example throttled, access_denied, user_error, internal). Never the message or stack trace
errorCode NO_SCAN Awnexa’s own error code, or other
durationMs 5300 Rounded to 100 ms

Sent in metrics. Counts that could help identify an environment are sent as ranges.

Field Example Notes
regions 2 Number of regions scanned (not their names)
plugins 68 Number of Awnexa plugins that ran
accounts 1 / 2-10 / 11-50 / 51+ Number of AWS accounts stored in your local database, as a range. Never the account IDs
dataDirs same ranges as accounts Number of data directories you scanned in the last 90 days, as a range. Never the paths: only a hash of each path is kept, on your computer, next to the telemetry settings (awnexa telemetry disable deletes it)
resources 0 / 1-99 / 100-999 / 1k-9.9k / 10k+ Number of resources, as a range
relationships same ranges Number of relationships, as a range
complete true / false Whether the scan collected everything
coverage {"complete":120,"access_denied":3} Number of collection units per status
pluginCoverage {"s3":{"complete":4}} The same, per Awnexa plugin ID. Never resource counts or resource types
  • AWS configuration data: resource IDs, ARNs, names, tags (keys or values), properties, evidence, resource types, region names
  • AWS account IDs, credentials, profile names, role names
  • File paths, host names, user names, values of environment variables
  • Values of options (--region, --profile, --name, --tag, …)
  • Error messages and stack traces

Before an event is stored for sending, the CLI drops it if anything in it looks like an AWS account ID, an ARN or an IP address.

  • Your IP address is not logged or stored. The request rate is limited for the API as a whole, and a firewall in front of it also refuses an address that sends far more than one CLI would (it looks at the address only to count requests and keeps no record of it).
  • Raw events are kept for 13 months and then deleted. Aggregates that contain no install ID are kept.
  • To have your data deleted, send us the installId shown by awnexa telemetry status.

The paid add-ons that are planned will send, separately from usage statistics, a license key and the Awnexa version to check the license: only when the license is close to its expiry date (at most once a day), not on every command. Team sharing will send scan results only when you turn it on yourself, and will show what it sends first. Neither exists yet; this page will describe them before they are released.