@@ -21,8 +21,10 @@ have fewer bugs, and we receive fewer bug reports on outdated versions.
2121Upon starting an application using the ` sharg::parser ` , it is determined whether the app was built in release
2222mode (we assume a user is running it) or in debug mode (we assume the developer is running it).
2323
24- We then send a web-request to our server with the following information:
24+ The user/developer is then asked whether they want to perform a version check. The default answer, which is also used
25+ if the terminal is not interactive, is to skip the version check.
2526
27+ If the user/developer agrees, we then send a web-request to our server with the following information:
2628 * The application name
2729 * The application version
2830 * The Sharg version that the application was built with
@@ -38,6 +40,8 @@ Additionally, we recommend registering your app with us (
[email protected] ).
3840
3941## Privacy Implications
4042
43+ ** No data is transmitted unless the user _ explicitly_ allows it.**
44+
4145Only the information listed above is transmitted; no data is gathered about the usage of the app, and, of course, no
4246information regarding your input/output files is transmitted. All our code is open source, and hence this can be
4347verified at any time.
@@ -63,3 +67,6 @@ variable `SHARG_NO_VERSION_CHECK` to any value.
6367Application developers may opt out of the version check for their app permanently (independent of user choice) by
6468passing ` sharg::update_notifications::off ` as the fourth argument to sharg::parser.
6569See the respective API documentation of the ` sharg::parser ` .
70+
71+ Note that ` sharg::update_notifications::on ` does not mean that the version check is performed, but rather that the
72+ application is allowed to perform the version check if the user chooses to do so.
0 commit comments