Privacy of BashSupport Pro
BashSupport Pro never sends metrics without your consent. A notification is displayed at startup to ask for your consent. If you don’t opt–in to metrics, then nothing will be send.
Metric data is a small piece of information to tell what’s happening and which features are used or unused. Data is send in the form of events. An event is send when something happens, e.g. when the Bash debugger was started.
Please note, that preview and beta versions of the plugin always send telemetry data.
No personal information is send.
This means that data like your hostname, your user name, or your own name are never send.
Your actions are not tracked. No unique IDs to identify you are send. Sentry usually sends the hostname, but this has been disabled for BashSupport Pro.
Data is send in the form of events. Each event has a name and a set of properties (name and value). The events are send to learn what’s happening on a global scale, but not to track actions of individual users.
Exception reports are also send to the Sentry application above. Only the information which you entered into the dialog is send. Please note, that the common properties shown above are also send with the error report.
The following section shows exactly what’s send. This list displays the data, which is used by the latest public release of BashSupport Pro.
I’m no aware of any other company offering such a list. Personally I strongly dislike tracking. I need some data to make sure BashSupport Pro is developing into the right direction — therefore I’m tracking software, not people. I try to be very open about what’s going on under the hood.
These are the properties which are send with every event.
|Timestamp when the event is send to the server.|
|The installed version of the BashSupport Pro plugin|
|Name of the used software platform, used internally by Sentry.|
|A string to tell if the plugin is a development or stable version|
|The vendor of the Java runtime used to execute the IDE.|
|Version of the Java runtime used to execute the IDE.|
|The name of the operating system you're using.|
|The version of the operating system you're using.|
|The product code of your IDE.|
|The major build number of your IDE.|
|The full build id of your IDE.|
|A boolean value to tell if the JetBrains Shell plugin is used with BashSupport Pro.|
|A boolean value to tell if the open-source BashSupport plugin is used with BashSupport Pro.|
|Boolean value if a license is found for the plugin.|
|Boolean value if the current license is for trial.|
|Number of remaining days if the current license is for a trial|
These are the events and properties which are send. The common properties are send with each event, but not listed again. You can expand the “Properties” sections to see the properties of a specific event.
|Event||Description and properties|
|app_starting||Fired when the IDE is starting and the BashSupport Pro plugin is initialized
|test_bats||Fired when a bats-core run configuration is executed
|debug_session_paused||Fired when a Bash debug session stopped at a breakpoint.|
|debug_session_resumed||Fired when a Bash debug session was resumed.|
|debug_session_started||Fired when a new debug session was started
|debug_session_stopped||Fired when a Bash debug session terminated, either successfully or with an error.|
|intention||Fired when an intention of BashSupport Pro was applied in a file
|new_file_action||Fired when a new shell script file has been created using BashSupport Pro's new file action
|quickfix||Fired when a quickfix of BashSupport Pro was applied in a file
|run_config_started||Fired when a run configuration is executed
|status||Aggregated numbers of often used features
|trial_end_notification||Fired when a notification was shown, which informs trial users that the trial expires soon.|
|unlicensed_action||Fired when a feature is executed, but no valid license was found. A stack trace is included in the event data.|