Synth collects de-identified usage data to help create a better product and user experience.
You can opt-out of Synth's anonymous data collection at any time by running the command:
or deleting the file at
Synth is completely free and open-source. This means all the code that provide
us with telemetry information is accessible by anyone. You can find
telemetry.rs submodule of Synth in our public repository.
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 it is explicitly and clearly documented here.
Synth uses a configuration file under the user configuration directory (
~/.config/synth/config.json on typical unix systems) as a marker for
telemetry being enabled. This file also contains a randomly generated
identifier. We use this identifier to better understand how we can improve the
user experience for Synth.
You can check if telemetry is enabled by running
synth telemetry status.
You can opt-out at any time by running
synth telemetry disable.
All the telemetry data is collected in a Posthog instance run exclusively by the maintainers of Synth.
If you would like the data associated with your UUID to be deleted, please
Synth's telemetry collects 6 fields:
distinct_id: A randomly generated UUID stored at
command: The command that was issued by the user. This is a text field whose value is one of the following:
success: If the command completed in success.
version: The current semver of Synth. For example
os: The target platform for which the binary was built. This is the value of
CARGO_CFG_TARGET_OSenvironment variable under which
synthwas built in CI/CD. Currently, this is one of:
timestamp: The time at which the command was issued. For example
Below is the Synth schema of PostHog events posted by