Telemetry

Claude-mem includes anonymous usage analytics (via PostHog) to help prioritize fixes and features.

It is on by default (opt-out). Events are anonymous, identified only by a random install UUID, and every property passes a strict whitelist — see What is collected and What is NEVER collected below. Turning it off is one command:

npx claude-mem telemetry disable

The standard DO_NOT_TRACK environment variable is also honored and overrides everything. The installer asks once at the end of npx claude-mem install so the default is never silent for new installs — your answer (either way) is remembered and never re-asked, and the prompt is skipped entirely when DO_NOT_TRACK is set or in CI/non-interactive installs.

What is collected

When enabled, events are anonymous and identified only by a random install UUID (crypto.randomUUID(), generated locally on first use).

Low-volume lifecycle events (install_*, uninstall_completed, worker_started) build an analytics profile keyed to that random UUID so aggregate retention and cohort statistics are computable — the profile contains nothing beyond the whitelisted fields below (platform, version, IDE/provider choice). It is not, and cannot be, connected to you: there is no name, email, IP, hardware ID, or any other identifier. All high-volume events (session_compressed, search_performed, context_injected, error_occurred) are sent with $process_person_profile: false and build no profile at all.

Every event property passes through a strict whitelist scrubber — any key not in this table is silently dropped before sending:

One value is derived server-side rather than sent by the client: PostHog resolves the request's sender IP to a coarse location (country / region / city) at ingestion, before the IP itself is discarded. The client never attaches an IP to any event, and the raw IP is never stored — see What is NEVER collected.

Events

What is NEVER collected

These are enforced in code: properties go through a whitelist (only the fields in the table above survive), not a blocklist. Every whitelisted field is either a number, a boolean, or a value from a closed set we define — there is no field that could carry free-form user content.

How to opt out (four ways)

Any one of these keeps telemetry off — they are checked in this order, first match wins:

1. DO_NOT_TRACK — the universal opt-out. Set DO_NOT_TRACK=1 and telemetry is forced off, overriding everything else.
2. CLAUDE_MEM_TELEMETRY=0 (also false / off) — environment override. (CLAUDE_MEM_TELEMETRY=1 conversely forces it on.)
3. Telemetry config file — enabled: false in telemetry.json (see below).
4. CLI command:
   bashCopy

   npx claude-mem telemetry disable
   

Check the current state — and which of the four layers decided it — anytime:

npx claude-mem telemetry status

Debug mode

Want to see exactly what would be sent? Set:

CLAUDE_MEM_TELEMETRY_DEBUG=1

With debug mode on (and telemetry enabled), every would-be event payload is printed to stderr and nothing is sent over the network.

Where the config lives

Consent and the anonymous install ID are stored in telemetry.json inside the claude-mem data directory:

• Default: ~/.claude-mem/telemetry.json
• Or $CLAUDE_MEM_DATA_DIR/telemetry.json if you've overridden the data dir

{
  "enabled": false,
  "installId": "<random UUID>",
  "decidedAt": "2026-06-09T21:00:00.000Z"
}

The enabled field is only present once you've made an explicit choice (installer prompt, telemetry enable, or telemetry disable). A file with just an installId means no decision was recorded and the default (on) applies. Delete the file to reset completely — a fresh install ID is generated on next use.