Anonymous usage telemetry

Dynamo can send anonymous usage data so we can see which features help game devs and what to build next. It is opt-in and off by default — nothing is sent unless you say yes to the one-time prompt. It never includes your prompts, code, file contents, file paths, AI responses, email, or IP. You can turn it off (or on) at any time with dynamo telemetry off. This page is the detail behind that prompt.

When telemetry is enabled, the Dynamo CLI sends small, anonymous events:

• Which commands and features you use — e.g. that a tool, skill, or slash command ran and whether it succeeded. Names only, never inputs or outputs.
• Funnel milestones — first launch, first command, first AI-assisted edit/run, sign-in, and upgrade — so we can see where new users get stuck.
• Errors — that a turn failed and a coarse category (e.g. network, rate-limit), never the error text, stack trace, or any content.
• Environment — your operating system (e.g. darwin), the Dynamo version, and whether you're on the free tier.
• An anonymous install ID — a random identifier generated on your machine the first time telemetry runs (see below).

The following never leave your machine through telemetry. This is enforced in the CLI: events are reduced to simple counts and labels before sending, so content cannot be attached even by accident.

• Your prompts or messages to the AI.
• Your code, file contents, or file paths.
• AI responses, tool inputs, or tool outputs.
• Your email, real name, or IP address.
• Project names (beyond a hash) or any other personal content.

We also never use anything you do in Dynamo to train AI models, and we never sell your data.

The install ID is a random UUID created on your machine and stored locally. It is notderived from your account, email, license, or hardware — it's deliberately decoupled, so usage events can't be tied back to you. It exists only so we can tell “100 people tried the tool this week” apart from “one person ran it 100 times.”

Events from paid actions (gate checks, upgrades) additionally carry your license ID so we can measure conversion — those, and only those, are linked to your account and are covered by the export/delete controls below.

• First-run prompt — the first time you start Dynamo interactively, it asks once whether to send anonymous usage data. The default is no. It never re-asks, and it never prompts (or sends) in CI / piped / non-interactive runs.
• Any time, from the CLI — run dynamo telemetry on, dynamo telemetry off, or dynamo telemetry status. You can also toggle it under /config inside the app.
• Environment variables — set any of DYNAMO_TELEMETRY_OPT_OUT=1, DO_NOT_TRACK=1, DISABLE_TELEMETRY=1, or DYNAMO_TELEMETRY=0 to force it off, regardless of your saved choice. We honor the cross-tool DO_NOT_TRACK convention.
• Audit what would be sent — run with DYNAMO_TELEMETRY_DEBUG=1 to print the exact payload to your terminal and send nothing.

Telemetry events are sent to our own Supabase-hosted backend — the same infrastructure that runs your account. We do not send your usage data to any third-party analytics provider.

Raw events are kept for 90 days and then deleted automatically. We retain only aggregate counts (e.g. daily active installs, funnel totals) beyond that window — those carry no per-event identifiers.

Anonymous events (most of what we collect) carry no link to you, so there is nothing to attribute, export, or erase. For the license-linked events (upgrades and gate checks):

• Export them from dynamoengine.dev/account via Download my data— they're included in your data ZIP.
• Delete them by deleting your account from /account — your license-linked telemetry is removed along with the rest of your data.

This is part of, and incorporated into, our main Privacy Policy.

Questions about telemetry or your data: privacy@dynamoengine.dev