During the continuous development of MuteDeck, we often review existing features and design for new features and options. By enabling the Send Anonymous Usage Stats option, you can help us understand how MuteDeck is used and lets us know which features matter most to you.

Disabled by default, MuteDeck will ask whether it can enable the collection of usage stats and send it to us when it first starts.

No data is collected or reported that can connect your identity to it. To be as transparent about what we collect, here’s what is collected and sent to mutedeck.com:


  1. Computer ID
    • Random generated string when your computer is installed. Here’s an example: 8B510C4A-BB24-5450-B1B0-BECC5F092DE6
  2. CPU Architecture
    • Whether MuteDeck is running on 32bit, 64bit, or another architecture.
  3. Kernel Type & Version
    • Shorthands for the type of system, like ‘winnt’ for Windows and ‘darwin’ for MacOS.
  4. Product Name & Version
    • Longer name for the type of system, like ‘Windows 11 Version 2009’ or ‘macOS Monterey (12.6).’
  5. MuteDeck Version
    • The version of MuteDeck that’s running.
  6. MuteDeck Licensed
    • Whether MuteDeck is licensed (but not the license itself.)


Events is a list of button presses that lets us know which buttons are being used the most. Per event, this is what is collected and sent to mutedeck.com:

  1. Event Date
  2. Event Type
    • This can be “mute”, “video”, “share”, “record”, or “leave.”
  3. Context
    • In which context the event type is run. This can be “system,” “zoom,” “webex,” or software that will be supported in the future.
  4. Via API
    • Tells us whether the event was triggered via MuteDeck’s API, which means it’s run via Stream Deck, Loupedeck, or another form of remote API. This can be “yes” or “no.”