For developers · Privacy and data
Privacy policy: feedback and usage statistics
On this page
Single source for the privacy policy text of the app and the website (sections "Feedback" and "Usage statistics"). All outgoing connections of the app are listed in privacy-network-inventory.md. Publisher and controller: the GbR behind Gitoodo (contact: the GbR mailbox named in the imprint). Rationale for the feedback rules: Microsoft Store policy 10.5.2 (data is shared only after opt-in). The usage statistics are on by default by the maintainer's decision of 2026-11-16, in every build.
Principle#
Feedback is submitted only when you press Send. Nothing is published, and there are no automatic feedback prompts. After you submit, queued messages are retried automatically for up to 24 hours. Store builds may show the system's own rating request now and then; Settings → System turns it off or stops it for good. Sending is opt-in per message; nothing you chose for one message carries over to the next.
What is sent#
| Data | When |
|---|---|
| Your text and the category | Always, because it is the message itself |
| Technical details | Only if you tick it for this message (preview shown) |
| Logs | Only if you tick it for this message (preview shown) |
| Screenshots | Only if you attach them for this message (preview shown) |
| Reply address | Only if you enter one; off by default |
| App version | Always, so we know which build the message is about |
| Message ID | Always; random per message, lets retries arrive only once |
Tokens, hosts and accounts are never sent. You see a preview of exactly what will be sent before you press Send.
Path and processors#
The app sends the message to the GbR's own relay. The relay sits behind Cloudflare (traffic passes Cloudflare's network). The relay forwards it by email to the GbR mailbox. Processors: Cloudflare, the mail provider the relay uses to send, and the mail provider hosting the recipient mailbox (GbR).
Log and retention#
The relay stores no message content. It logs only metadata: sender ID (public application ID), time, reference ID, result, size and a daily-salted IP hash (not reversible, changes every day). Metadata is deleted after 14 days. For abuse protection and safe retries it also keeps, for at most 24 hours, rate-limit counters per salted IP hash and the message ID with its reference. The received email stays in the GbR mailbox until the matter is handled and is used only to answer you and improve Gitoodo.
The app keeps an unsent draft on your device. After you submit a message, temporary delivery failures place that message and its selected details in the local outbox. Retries stop after 24 hours. Finished outbox entries are removed after seven days while the app is running; when the app is closed, cleanup happens on its next start. The editable draft remains until successful delivery or until you clear it.
Reply contact#
A reply address is optional and off by default. Without it we cannot answer you. It is used only to reply to this message.
Website contact form#
The website (site/, privacy page section "Contact form") has its own form on the same relay,
with the browser sender gitoodo-web (gitoodo-web-test for local previews). Only when the
visitor presses Send does the browser post the message, the chosen category, the reply address if
entered, and the page's language and path (no query) to relay.silvio-und-maik.de; nothing else,
no technical details, logs or screenshots. Path, processors, log and retention are the same as
above, except that the logged sender ID is the fixed website sender, not an installation ID. To
block abuse the relay counts requests per HMAC-hashed IP address for one hour. In the browser the
form stores only the flag gitoodo.site.contact.greeted (greeting seen or closed) in
localStorage; the draft lives in memory while the page is open. Without JavaScript or if the
relay is unreachable, the page offers the GbR mailbox instead.
Your rights#
Access, correction, deletion, restriction, objection and complaint to a supervisory authority under GDPR. Write to the GbR mailbox and quote the reference ID shown after sending.
Usage statistics#
Gitoodo can send anonymous usage statistics so we can see how the app is used and improve it for the people who use it. The statistics are on by default, and you can switch them off at any time.
Default and switching off#
- The last onboarding step shows the switch "Help make Gitoodo better", on by default, with what is sent and what never is. You can switch it off right there; "Finish" stores your choice. Settings → General has the same switch at any time.
- Nothing is sent before "Finish" stores the choice. Installs without a stored choice (installs that finished onboarding before this feature, or an onboarding that was closed early) send nothing, and Settings → General shows the switch off for them; they are not switched on silently. Running the introduction again from Help shows the switch on and stores it at "Finish".
- Running the introduction again shows the stored choice; it never resets it to the default.
- The setup steps you go through before the last step are held in memory only. When "Finish" stores "on" they are sent with their original times; when it stores "off", or when the app quits first, they are dropped.
- Switching off (on the last onboarding step or in Settings → General) stops sending at once (a request on its way is cancelled), deletes the install ID and drops everything still queued. Switching on again starts with a new install ID.
- The choice is stored per installation in
usage.jsonin the app's config folder. It is not part of the settings export, import or backup.
What is measured#
Only fixed identifiers from one list in the code (crates/core/src/usage/taxonomy.rs), never free
text. A test checks every possible event against a parameter whitelist.
- Onboarding: which step was shown, left with next, skip or back, or closed (step name only); the token wizard page and the token check result per forge type; the error kind when a repo list could not load; which setup parts were done, skipped or failed.
- Use: which views, help entries and help center topics are opened; whether the introduction tour was finished or skipped and the weekly review was dismissed or switched off; that a question was forwarded (never to whom); slash command names of Gitoodo's own commands (an agent's commands count only as "agent"); answers by kind (card or comment, with or without AI help); the result of the system check; error kinds of failed commands and background services; counts of chat messages, started workers and merged pull requests.
- Milestones, once per install: first question seen, first answer sent, first worker started, first pull request merged, first chat message.
- An app start event and one "alive" event per day.
- Context of each visit: app version, build variant (direct macOS, Mac App Store, Windows installer, Microsoft Store, Linux), operating system and architecture, mode (direct or orchestrator), UI language, the forge types in use (Forgejo, Gitea, GitHub, GitLab), whether they are cloud hosts, self-hosted or both, the orchestrator agent type, the number of accounts and enabled repos as a range (for example "6-20"), the install week and the install age as a range of days.
Pages are synthetic addresses such as app://gitoodo/board; no referrer is sent.
What is never measured#
- Contents of issues, pull requests, comments, answers, questions or chats.
- Names of repos, accounts, organisations, labels, branches or people.
- Tokens, passwords, keys or webhook addresses.
- Addresses of your forge servers or other hosts (only "cloud", "self-hosted" or "mixed").
- Free text of any kind, including error messages (only the error kind).
Install ID#
A random 16-digit hexadecimal ID is created when the choice "on" is stored ("Finish" with
the switch on, or switching it on in Settings) and links the events of this
installation. It is stored only in usage.json, is deleted when you switch the statistics off and
is replaced by a new one when you switch them on again. It is not derived from the device, the
account or any other identifier, and it is a different ID from the sender ID of the feedback
relay: the two cannot be joined.
Forgejo check#
Forgejo and Gitea share one API. To tell them apart for the forge type, Gitoodo asks each
self-hosted Gitea-type server once, without a token, for /api/forgejo/v1/version and keeps only
the answer "Forgejo" or "Gitea". This happens only while the statistics are on; the server address itself
is never sent to the statistics server.
Path, processing and retention#
- Events go in batches, at the latest every 15 minutes, by HTTPS to the GbR's own Matomo
instance at
matomo.silvio-und-maik.de(server in the EU). No third party receives them. - Offline, up to 500 events wait locally in
usage.json; events older than 23 hours are dropped instead of being sent late. - The app sets no cookies. Matomo stores IP addresses only shortened (IPv4 by two bytes, IPv6 correspondingly); the full address is used only while the request is processed, for the country lookup.
- Raw visit data is deleted on the Matomo instance after 180 days; only aggregated reports remain. Because the install ID is random and deleted when you switch the statistics off, switching off ends any link between future and past events.
- Builds without a statistics site ID (development builds, forks), the test access build, UI automation runs and the browser demo record and send nothing.
Your rights for the statistics#
Switching off in Settings → General ends all sending. Access, deletion and objection under GDPR: write to the GbR mailbox.