ETS6 Professional
Your privacy is important to us. It means we store your data safely and ensure it remains well protected. We also let you know what we do with your data when we use it respectfully so that we can provide you with a better service.
This Telemetry data statement states which data we may collect from you, how we may use that data, and with whom we may share it. We explain what we do to protect your privacy, how you have a say, and what checks are performed to ensure compliance with this statement.
This Telemetry data statement applies to the collection, management, use and sharing of your data by KNX Association. This Telemetry data statement must be viewed in combination with our terms and conditions of the Software License Agreement. We can change our Telemetry data statement at any time, and we shall make the most recent version available on our website. This Telemetry data statement was last reviewed and amended on September 20th 2021.
When is this statement applicable?
This Telemetry data statement is applicable when you use our software ETS6 Professional and all its editions (Demo, Lite, Home, Professional). By using our software, you give us permission to collect and use software usage data as described in this Telemetry data statement.
What data do we collect?
We distinguish different types of data. These different types of data allow us to analyze the software usage in order to improve the quality of our products and services:
Software version information: allows us to identify the software version of the respective software which is installed and running on the computer. This may include as well other software installed on the computer that may influence the operation of our software (e.g. Windows, Telemetry component, .NET Framework, Antivirus, etc.).
Machine information: allows us to identify the hardware of the computer on which the software is installed. This may include external hardware that is connected and used on that same computer that may influence the operation of our software (e.g. RAM size, amount of CPU cores, amount of screens and their resolution, etc.)
Software configuration: allows us to identify the configuration of our software and if its default configuration is kept (e.g. language, compatibility mode not activated, amount of project recovery points, etc.)
Software performance: allows us to identify the performance of our software (e.g. startup time, overall time the software has been running, etc.)
Software operations: allows us to identify the operations triggered on our software (e.g. add/remove project tags, project type definition, etc.)
KNX device configuration: allows us to accurately identify device capabilities, analyse system behaviour in context, detect inconsistencies or misconfigurations, and improve overall service quality.
Our software does not at any time send user data (e.g. name, email address, license number) or anything else that could allow us to identify you.
Our software does not at any time send sensitive data. Here you can see what is considered sensitive data.
Our software does not at any time send KNX device security-related data (e.g. FDSK, tool keys, authentication codes) or anything else that could allow anyone to compromise the security on a KNX installation.
Why do we collect this data?
We process software usage data for various reasons, in each case we only process data that is necessary to achieve our goal. We collect software usage data for the following purposes:
To identify potential performance improvements.
Our development teams go through a QA process before developing in an agile environment towards the end. This can be a lengthy and cumbersome process. We invest time by the time an application or piece of code reaches that process. Our development teams have been working on it for some time, and waiting until the last minute to identify a performance issue can result in rework and cause the product's debut to be delayed. There isn't enough time for delays to be reworked. Our development teams must get software performance right the first time, without fail, therefore we have to ensure that when an application enters the QA process, there will be significantly fewer adjustments required.
To better understand which features are used and how often.
Our software has been handling KNX devices and project data since early 90s, therefore it may contain functionality, which was introduced many years ago for a specific purpose. However, it is very critical for us to understand whether the current functionality is still used and answers the current needs of our users or not. Part of our mission is to provide effective and high quality KNX Tools, therefore it is essential to always improve our software's user experience, as system and technology extensions are continuously coming into the market.
To identify software misbehavior.
Even the most skilled IT professional can't predict the future precisely. Use cases, workflows and supported devices are extended continuously. Side effects in rarely used workflows might not be detected. That's why software execution should be evaluated on a regular basis and that's why software execution engineering is so vital.
Who is managing your data?
All software usage data is managed by KNX Association. The data is only accessible to those within KNX Association and its development partners who need access to it to perform their tasks.
We work with external data processors. This means, for example, that we temporarily pass data to third parties for certain tasks if we do not have the means to carry out these task ourselves. If we do this, we shall always ensure your data is treated confidentially and used securely. We always set this out in the contract we enter into with the data processors. For example, a processor shall never be allowed to use your data on his own initiative, and your data must be deleted as soon as a processor has completed his work.
We use anonymous, aggregated data for external reporting. This data can never be traced back to a specific individual.
At no time do we sell or rent your data to companies or individuals that are not part of our company or group. We regard your data as confidential information.
How do we protect the data?
We protect the software usage data and privacy as much as possible. Our employees are trained to deal with confidential data correctly. We also employ specialized people who are responsible for the security of our IT infrastructure. We also use various technical measures to protect any data we handle.
Our software implements components from various developers, which the terms of use do not fall within the scope of this Telemetry data statement. Read their policies regarding the protection of your personal data carefully.
Do you want to stop submitting this data;
You have the right to discontinue the sending of the software usage data. To do so, click the respective option from the software settings as explained here.
How long do we store your software data for?
We ensure appropriate organizational and technical measures to secure the collected software data. We may not store software data for longer than is necessary to achieve the purpose for which we collect it. The storage period can therefore differ per objective, and can sometimes be very short. After the applicable storage periods have expired, software data shall be completely deleted.
Do you have any questions?
If you have questions about our Telemetry data policy, we are always ready to offer a suitable answer. You can reach us by email, in writing, using the contact details from our website. This means you can also submit a complaint that we can process in the correct way as quickly as possible. If you are not satisfied with our response, you can also contact the government, and more specifically the Commission for the protection of privacy. The contact details can be found on their website.