Documentation Docs version: dev (Pre-release: Gitoodo has not been released yet)

For developers · Privacy and data

Network inventory of the desktop app

On this page
  1. 1. Connections of the app
  2. Opened in the browser only (no app connection)
  3. 2. Usage statistics in detail
  4. 3. Local only

Every outgoing connection Gitoodo makes, derived from the code. Network access lives only in the Rust core (crates/core); the frontend has none, and tokens are never part of a log line, an error text or the frontend. Privacy texts: privacy.md. Update this table whenever a new destination or trigger is added.

Legend for "Default": always = part of the core function, cannot be turned off without removing the account or feature; opt-in = only after an explicit choice; on by default = runs unless switched off, with a visible switch; action = only after a click.

1. Connections of the app#

#DestinationPurposeTriggerDefaultSent (roughly)Code
1Your forge servers (GitHub api.github.com, GitLab, Gitea, Forgejo; cloud or self-hosted)Sync of issues, pull requests, comments, checks; answers; repo setup, labels, settings checks; mergesSync interval, your actions, the orchestratoralways, per account you addThe token of that account, API requests for the enabled repos, your answers and commentscrates/core/src/forge/ (http.rs, github.rs, gitlab.rs, gitea.rs, setup.rs, ...)
2The host you type in the token wizardFind the base URL (https first, then http) and check the tokenToken wizard, "Check"actionBare server request without token; then the token checkcrates/core/src/forge/resolve.rs, forge::check_token
3Your forge servers via the system gitClone and update repos for workers (orchestrator)Orchestrator setup, worker startopt-in (orchestrator mode)Git protocol with the account's tokencrates/core/src/repo_clone.rs, orchestration/dispatch/
4The chat webhook you configure (Slack, Teams, Matrix)Chat notificationsNew question or event you enabledopt-in (Settings → Notifications → Chat)Message text with repo, title and link; the webhook URL stays in the keychaincrates/core/src/chat/send.rs
5api.github.com/repos/silvio-l/gitoodo/releases/latest (replaceable by GITOODO_UPDATE_URL at build time)Update check, direct builds only"Check for updates" in Settings → Aboutaction; store builds never checkOne GET, no identifiercrates/core/src/update.rs
6github.com/silvio-l/gitoodo/releases/download (replaceable by GITOODO_RELEASE_URL)Download the CLI build for a satellite host, checksum-verifiedInstalling or updating a satellite hostactionOne GET per filecrates/core/src/remote_version.rs
7Your satellite hosts via the system ssh/scpRun workers on other machinesHosts you add in Settings → Hostsopt-inCommands, the verified CLI build, repo workcrates/core/src/satellite_host.rs
8matomo.silvio-und-maik.de/matomo.php (the GbR's own Matomo, EU)Anonymous usage statisticsFirst round 60 s after start, then every 15 min; right after "on" is storedon by default since 2026-11-16; sent only after "Finish" on the last onboarding step stores the choice; switchable off there and in Settings → GeneralClosed event identifiers, counts, buckets and the visit context (see privacy.md); random install ID created when "on" is storedcrates/core/src/usage/ (client.rs, payload.rs, taxonomy.rs); loop src-tauri/src/usage.rs
9Your self-hosted Gitea-type servers, /api/forgejo/v1/versionTell Forgejo from Gitea for the statistics' forge typeOnce per account, only while the statistics are on; cachedfollows row 8One GET without token; only "Forgejo" or "Gitea" is keptcrates/core/src/usage/client.rs (is_forgejo)
10relay.silvio-und-maik.de/v1/feedback (the GbR's own relay behind Cloudflare; replaceable by VITE_FEEDBACK_RELAY_URL)Deliver feedback by mail to the GbR mailbox"Send" in the feedback dialog; queued messages are retried for up to 24 hactionThe message with the details you ticked, category, optional reply address, app version, public sender ID (gitoodo, test builds gitoodo-test) and a random message ID; no tokencrates/core/src/feedback.rs; loop src-tauri/src/feedback.rs

The orchestrator's background service (gitoodo CLI, dispatcher, satellite) additionally reads the Claude plan usage from api.anthropic.com/api/oauth/usage with the Claude login of the machine (crates/core/src/claude_oauth.rs). The coding agents it starts (Claude Code, Gemini, Codex) make their own connections under their own terms; Gitoodo does not proxy them.

Not found (negative result): no connection without one of the triggers above; no third-party SDK, no crash reporter, no advertising or attribution identifier.

Opened in the browser only (no app connection)#

Issue, pull request and check links of your forges, the project pages (GitHub repository, releases, changelog, documentation), support pages and contact links from Help. They open in your default browser; the app itself does not request them.

2. Usage statistics in detail#

  • Fail closed: without GITOODO_MATOMO_SITE_ID at build time (crates/core/src/usage/mod.rs, SITE_ID), nothing is recorded or sent. Development builds and forks therefore send nothing.
  • Site ID 17 ("Gitoodo App") only in distributed builds: scripts/build-local-mac.sh (and so scripts/release-mac.sh, which calls it) sets it for the signed Developer ID build; src-tauri/windows/package.ps1 sets it only for a package with the real store identity (not Gitoodo.LocalTest); the Mac App Store submission build passes it on the command line. An explicitly set value wins; GITOODO_MATOMO_SITE_ID= (empty, macOS) or -NoUsageStatistics (Windows) builds without statistics. npm run tauri dev, debug builds, the test access build and the CI gate never get it. The dimensions are listed in crates/core/src/usage/context.rs.
  • Retention: raw visit data is deleted on the instance after 180 days.
  • Hard stop: UI automation (GITOODO_UI_AUTOMATION), the test access build (test-access feature) and the browser demo (src/platform/browser.ts) never record, write or send, whatever the stored choice.
  • Choice gate: until a choice is stored ("Finish" on the last onboarding step, switch on by default, or the switch in Settings) the tracker only holds onboarding events in memory (at most 200); everything else is dropped. An install without a stored choice sends nothing; the core never assumes the default. "Off" drops them, deletes the install ID and the queue, and cancels a request in flight. Tests: crates/core/src/usage/tracker.rs.
  • Payload whitelist: each request carries only idsite, rec, apiv, send_image, _id, _idts, rand, url, cdt, e_c, e_a, e_n, e_v and dimension1-dimension12; no urlref, no uid, no cip, no token_auth. Test: crates/core/src/usage/payload.rs.
  • Queue: at most 500 events in usage.json, batches of 100 by bulk POST, events older than 23 hours dropped (Matomo would need a token for older times).
  • Store builds behave like direct builds and report their own variant (mas, msix); the request goes through the sandbox's outgoing network entitlement the app already has for forges.

3. Local only#

Loopback and local files only: the notification and tray integration, the keychain (macOS Keychain, Windows Credential Manager, Secret Service), the local log, usage.json, rating.json and the settings file.

Docs version: dev