Install analytics

The one anonymous ping a damn.dev instance sends when it comes online, exactly what it contains, and the single switch to turn it off.

When an instance comes online it sends one anonymous ping, then a weekly heartbeat, so we can see the project is being used and count live installs. Nothing about your workspace ever leaves your machine.

What we send#

A random install id (generated locally, tied to no account), plus:

  • the version you're running,
  • the install path (npm, docker-local, docker-vps, or Tauri),
  • your OS and architecture (e.g. darwin/arm64),
  • when this install was first and last seen.

The exact payload:

json
{
  "installId": "9f2c1a44-…",
  "version": "0.28.0",
  "installPath": "docker-local",
  "os": "darwin/arm64",
  "firstSeen": "2026-07-02T09:14:00.000Z"
}

What we never send#

  • workspace data or agent files,
  • messages, deliverables, or secrets,
  • your name, email, or account,
  • agent activity, usage, or feature counts,
  • anything you or your agents create.

Ceiling — This is install analytics, not product analytics. We count that an instance exists and what version it runs. We do not, and by design cannot, see what happens inside it.

Turning it off#

Set either variable and no ping is ever sent:

text
DAMN_DEV_DISABLE_ANALYTICS=1

We also honor the cross-tool DO_NOT_TRACK=1 standard. The exact payload is the one shown above — there is nothing else.

Note — The ping is fire-and-forget and never blocks boot. If it can't persist its anonymous id it skips entirely, rather than counting your one install as many.

Next#

Previous← Data, backups, networking & updatesNextEnforced vs Trusted →