Guides
How to read telemetry claims
Read the documented behavior by purpose and default. “Off by default”, “opt out”, and “not documented” describe different facts, and open source does not imply no telemetry.
Scope: a concise editorial field note, not a universal recommendation, security audit, or guarantee.
Name the network action
Separate usage reporting, crash reports, update checks, device discovery, remote feature calls, website analytics, and traffic to a provider. Each can have a different destination, purpose, trigger, and setting.
A program can be quiet about usage reporting while still checking for updates or contacting a discovery service. That is not a contradiction, it is a more precise description.
Read the setting carefully
“Off by default” means a feature starts disabled for a new installation. “Opt out” means a feature may start enabled or be available until you decline it. “Not documented” means the reviewed material did not establish the behavior.
Do not turn any of these phrases into a broader guarantee. They describe a documented configuration or an evidence gap, not every connection the software can make.
Use disclosures as a map
Syncthing documents discovery, update checks, relay use, and optional usage reporting as separate parts of its behavior. Thunderbird documents interaction and technical telemetry together with opt-out information. Compare the details, not just a privacy label.
Open source is about the freedoms to use, study, modify, and share software. Those freedoms are important, but they do not by themselves answer what network traffic exists.
Practical checklist
- Separate usage, crash, update, discovery, and provider traffic.
- Record whether each feature is off by default or opt out.
- Mark claims that are not documented as unknown.
- Do not infer telemetry behavior from the license alone.
Sources checked
These first-party or authoritative sources ground the note. Checked 2026-08-11.