Skip to main content
Dure sends nothing until you say so. On first launch the main window asks whether to share anonymous usage data; until you answer, and if you decline, no usage event leaves your machine. You can change your answer at any time under Settings → Privacy and telemetry.

​
What is sent when you opt in

Events go to PostHog in its US cloud region. Each event carries a random install id (never an account, email or device name), the app version, the release channel, the operating system name and version, and the CPU architecture. PostHog is told not to build a person profile and not to look up your location, and the PostHog project is configured to discard the IP address of the request. That list is the whole allowlist: an event that is not on it, or a property that is not listed, cannot be sent, and provider is bounded to a short lowercase id. PostHog keeps events for one year on its free plan and seven years on paid plans.

​
What is never sent

File paths, repository, branch and worktree names, URLs, commit messages, prompts, agent output, terminal contents, error messages, host names, user names and IP addresses. There is no field for any of them.

​
Turn it off

  • Settings → Privacy and telemetry → Anonymous usage data: turn the switch off. Dure tries to send one final telemetry_opted_out event, deletes the install id, and stops.
  • Set DO_NOT_TRACK=1 or DURE_TELEMETRY_DISABLED=1 in the environment Dure starts from. Either overrides the switch without changing it; the Settings page names which one is in effect.
  • Continuous-integration environments (CI, GITHUB_ACTIONS, GITLAB_CI, CIRCLECI, TRAVIS, BUILDKITE, JENKINS_URL, TEAMCITY_VERSION) never send.
A build without a telemetry key, such as a local development build, shows no question and no switch, and sends nothing.

​
Other data lanes

The diagnostic report and in-app feedback are separate: each is sent only when you press Send, and neither carries the usage-data install id.