Synth collects de-identified usage data to help create a better product and user experience.
Synth telemetry is opt-in; the user is explicity prompted at installation, asking if they would like to participate in de-identified data collection.
Below are a set of principles that guide the telemetry decisions made in Synth:
- It is made completely transparent that telemetry is going to be installed
- It is made completely transparent as to what data we collect
- No personally identifiable information is collected. (IP addresses are discarded at the Sink)
- Nothing is collected unless the user explicitly opts-in.
Synth uses a configuration file under the user configuration directory (e.g.
~/.config/synth/config.json on typical unix systems) as a marker for telemetry being enabled. This file
also contains the user's randomly generated unique
The user is prompted during the installation process about telemetry being enabled.
Users can check if telemetry is enabled by running
synth telemetry status.
Users can opt-out at any time by running
synth telemetry disable.
All the telemetry data is collected in a Posthog instance run by the maintainers of Synth.
If for whatever reason you would like the data associated with your UUID to be deleted, please contact
Synth's telemetry collects 6 fields:
distinct_id: A randomly generated UUID stored at
command: The command that was issued by the user. One of (
init | import | generate | telemetry::enabled | telemetry::disabled)
success: If the command issued succeeded or failed.
version: The version of Synth being used. For example
os: The host operating system, for example 'linux'
timestamp: The time at which the command was issued. For example
Below is a Synth schema generates telemetry events: