What Data We Collect

We try to collect the bare minimum amount of data that allows us to ensure that Syside tools are functioning correctly and are used fairly and according to the License Agreement.

This page explains what telemetry Syside tools collect, how they do it, what the telemetry is used for, and how you can disable it.

Usage Data

Usage data is only used to monitor whether Syside tools are being used fairly. This is achieved through our licensing implementation, which checks the license validity and sends heartbeats. This data collection cannot be deactivated by the user of Subscription or Free licenses.

We collect the following data:

  • Licence key.

  • IP address of the machine.

  • Time of the license check or a heartbeat. Syside sends out a heartbeat every 30 minutes.

  • Hashed machine ID.

  • Operating system.

This data is being used by us to monitor and enforce that only licensed users have access to Syside tools.

Offline Installation

No usage data is collected for Syside offline installations as described in Offline Installation. For further information about different licence types, refer to Licensing.

Crash Reports

Syside has the ability to automatically collect and send crash report logs back to Sensmetry. This automatic crash log reporting allows us to discover and fix critical bugs faster.

The crash reports are completely anonymous. We do not get any of your models or your Python scripts. We also trim any Language Server Protocol payloads to avoid leaking secrets, which enables you to use the trace level logging without worry.

The logs that are sent to Sensmetry are locally saved to %LOCALAPPDATA%\syside (on Windows) or ~/.local/state/syside (on macOS and Linux) for you to have a way to inspect what data is being sent. The logs are compressed using ZStandard compression, which should be supported by most modern decompressors, or you can also download the zstd tool.

Automatic crash reporting is enabled by default. If you wish, you can disable automatic crash reporting by:

  • Editor / Modeler: Either setting the syside.telemetry.crashReports setting to False or telemetry.telemetryLevel setting to Off, and restarting Syside.

  • Automator: Executing syside.debug.set_crash_report_upload(False) function.

  • Modeler CLI: Passing in --crash-reports ignore command line argument.

Offline Installation

By default, even offline installations of Syside will attempt to send automated crash logs. To prevent these attempts, explicitly disable crash log reporting using mechanisms described above.

On this page