mirror of https://github.com/openclaw/clawhub.git synced 2026-08-14 08:52:21 +00:00

Files

T

Patrick Erichsen e8a75de2b1 refactor: remove root install telemetry (#2673 )

* refactor: remove root install telemetry

* chore: add root telemetry cleanup job

* fix: preserve legacy root telemetry deletion

* fix: handle token list after account deletion

* test: isolate local-auth e2e from production crons

2026-06-15 19:42:51 -07:00

1.4 KiB

Raw Blame History

summary, read_when

summary

read_when

Install telemetry collected by the ClawHub CLI and how to opt out.

Working on telemetry / privacy controls

Questions about what data is collected

Telemetry

ClawHub uses minimal CLI telemetry to compute aggregate install counts.

When telemetry is collected

Telemetry is only sent when:

You are logged in in the CLI.
You run clawhub install <slug>.
Telemetry is not disabled (see “How to disable” below).

If you are not logged in, nothing is reported.

What we collect

On each reported clawhub install, the CLI sends one best-effort install event.

The event includes:

slug: the installed skill slug.
version: the installed version, when known.

What we do not collect

No folder paths or folder-derived identifiers.
No file contents.
No per-run logs, prompts, or other CLI output.

Install counts

ClawHub maintains aggregate counters per skill:

installsAllTime: unique users who have reported at least one CLI install for the skill.
installsCurrent: unique users who have reported an install and have not deleted their telemetry.

Transparency + user controls

Everyone only sees aggregated install counters.

Deleting your account also deletes your telemetry data.

How to disable telemetry

Set the environment variable:

export CLAWHUB_DISABLE_TELEMETRY=1

With this set, the CLI will not send install telemetry.

1.4 KiB Raw Blame History