MouseMux Telemetry and network data insights

Share

The information below explains what type of data (telemetry) is sent and received by the MouseMux program and what other network data is transferred:

  • Each time MouseMux is started, it will try to see if there are updates by contacting the mousemux update server - it will download a JSON file containing update information and may start doing updates by downloading individual packages.

  • MouseMux will send crash dumps (.dmp) and log files once it detected a crash has occurred.

  • MouseMux will send telemetry data to a matomo database and a countly database, the data being sent has an ID which is generated by hashing the computer name combined with a hash of the username. This final hash (a number) is used to identify the computer on which MouseMux is running. For paid version telemetry can be switched off all together which means no data will be sent. If collecting data during runtime it will collect the following information:

Data...................................... Comments....................................................................................
app.start Count event of number of times the app has started
app.license The license type and number used
app.running Timed event How long the app was running
app.exit.okay Event whether the app exited okay
app.init.boot Timed event on how long startup took
ui.* UI actions (button presses, refresh, etc)
user.button.switch Event that primary button was switched
user.screen.lock Event that the cursor was locked to a screen
user.paint.draw Event that on screen painting was started
user.paint.clear Event that on screen painting was cleared
user.paint.save Event that on screen painting was saved
user.paint.color Event that user chose new paint color
user.macro.record Event that user started macro recording
user.macro.play Event that user started macro playback
user.macro.save Event that user saved a macro recording
user.macro.load Event that user loaded a macro recording
user.speed.emu.load Event that user loaded an acceleration table
user.speed.emu.save Event that user saved an acceleration table
user.cursor.change Event that user changed cursor theme, with name
user.name.change Event that user changed their name
user.action.trigger Event that user started owning process
user.speed.change Event that user changed acceleration value
user.wheel.set Event that user changed their wheel configuration
user.startup.time Timed event on mouse mapping occurence
user.add.{number} Event that mouse was added and user became active
user.movesize Event user did a custom (multiplex) move/size
user.active Timed event on how long a user was active
user.program.enter Name of executable that user started interacting with
user.program.leave Name of executable that user stopped interacting with
udev.info.full Event mouse hardware was detected (type and manufacturer)
user.speed.emu.save Event that user saved an acceleration table
mdev.calibration Timed event on how long mouse calibration took