Telemetry collection
We collect telemetry data by default. This data is used to improve our products in terms of performance, usability and functionality. In general, we collect the following data:
Interaction data: This data shows us how you use our application. For example, how many calls you handle with our application, which functions you use or how many browser tabs you are running.
Technical data: This data provides us with information about your browser and your internet connection. For example, we want to know which browser you are using or how long your network requests take.
How do we collect data?
We collect telemetry data in the format of simple pings. This means that we send a small amount of data to our servers. Pings consist of the following information:
| Name | Description | Example |
|---|---|---|
| Solution | Identifier for the product being used. | b+s Connects for ServiceNow |
| Company Identifier | Globally unique identifier to identify the Company using the b+s product. | busag |
| Company Name | Name of the Company using the b+s product. | Bucher + Suter AG |
| Deployment ID | Unique identifier, which identifies a deployment at least within the company. | 1bd...1975 |
| Deployment Name | This is used to differentiate between DEV, QA or PROD environments. | ven012345 |
| Instance Identifier | The Instance Identifier uniquely identifies an instance inside a deployment. | ID of a browser tab |
| User Identifier | Pseudonymised identifier, which identifies a user of the product, at least within the deployment. | 005...194f |
| Timestamp | Time reflecting when the event occurred. | 2020-05-15T16:50:08.520Z |
| Version | The version of the software being used. | 4.1.3 |
| Event | Text describing what happened in the application. | ApplicationStarted |
| Payload | Payload containing additional event specific data. | Duration in ms |
We use the browser's Beacon API to send the data to our backend. The transfer of data takes place with the encryption supported by your browser.
Why do we need to know the company?
If we are in a position where we need to delete data that we have collected from your company, we must be able to identify it. While it is technically possible to pseudonymize such requests, we also want to be able to contact you if the situation requires it. Recently, IT was shaken by a critical log4j vulnerability. Especially in such cases we would like to be able to draw conclusions about the affected company.
Why do we need a User Identifier?
Currently, our telemetry data consists of simple pings. However, in order to draw meaningful conclusions from the data, we need to know if the individual pings come from the same user. For example, performance problems can be related to the number of open browser windows. This is why we use a pseudonymised user identifier.
How long do we keep telemetry data?
The exact duration depends on the total usage of the application. Currently it can be assumed that telemetry data will be overwritten after one year. However, we reserve the right to archive aggregated and concentrated results from which no conclusions can be drawn about the sender company.
How do I opt out or delete telemetry data?
In very special cases it is possible not to send telemetry data. If this applies to your company, please contact our support.