Skip to content

Privacy and Code Signing

Tobias Vorwachs edited this page Oct 27, 2026 · 3 revisions

Privacy and code signing

Privacy

Mumcord has no telemetry and sends no automatic crash reports. Its network connections (your Mumble server, optional link previews and external images, optional chat history sync with other Mumcord clients) are listed in plain language in the privacy statement, which is also summarised in the first-start wizard.

  • Privacy statement: PRIVACY.md
  • Link previews and external images share one switch (on by default, never for private or LAN addresses).
  • History sync, sharing of full-size images and positional audio can each be switched off in settings.

Code signing

  • Code signing policy: CODE_SIGNING.md
  • macOS: builds from 0.4.1 on are signed with a Developer ID and notarized by Apple, so Gatekeeper shows no warning.
  • Windows: builds are still unsigned and show a SmartScreen warning on first start; see Installation.
  • The release workflow signs (Windows) and signs plus notarizes (macOS) only when the maintainer has configured the needed credentials; without them a build stays unsigned.
  • Check a download with the SHA256SUMS file that comes with every release.

Mumcord is licensed under the AGPL-3.0.

Clone this wiki locally