[btown]

There are some situations where I'd say opt-in telemetry, properly messaged and with transparency/user-visible logs about what is uploaded, is fine.

But your tool is specifically for handling highly sensitive credentials, and telemetry can be used as part of an attack surface. For your tool, any hint of telemetry, even opt-in, would be a massive red flag.

Having a feedback button that launches a plain old mailto: link might be a good balance to provide an additional mechanism to learn about users' pain points.

[andreacavagna]

This is why the project handle all data locally only.

Adding an opt-in for telemetry is largely used in App that handle high sensitive data, like VScode and Insomnia API are handling them. The only data to be collected is when the App is active and when the app is inactive.

But I understand tour point of view

> Having a feedback button that launches a plain old mailto: link might be a good balance to provide an additional mechanism to learn about users' pain points.

This could be a great addiction to the Issues mechanism of GitHub. We've already added a preformat way to open an issue with Leapp directly from the app. But I don't know if this is enough