The Qt Company has an increasing need to better understand, how Qt products and product features are used by both commercial customers and open-source users. Application data collection AKA telemetry can provide valuable information about designer and developer behavior, which can be used to improve our tooling, tool workflows, and user experience. The following rules define how The Qt Company collects and uses collected data. Our priority in data collection is to respect the privacy of all our users.
The rules apply to Qt designer and developer tools, such as Qt Installer, Qt 3D Studio, Qt Design, Studio, Qt Creator, and deploy Qt.

Data collection is an opt-in feature for Qt all users. Data collection has to be actively enabled. By default, there is no data collection in Qt tools.
Activated data collection may be de-activated by the user at any time in the tool-specific settings. Clear documentation and instruction how to de-activate the collection will be available in the tool.
Collected data will be transmitted to the data collection backend. User can examine all the collected data in an easily readable and actual transmission format, which may be the same (JSON).

Collected data can be divided into two groups:

  • Environment data
  • Statistical usage data

Environment data contains information about the Qt version, license, platform, compiler and so on. This data is static by nature and contains no information about the user activities.
Statistical usage data contains dynamic data about feature usage, usage frequencies, and usage times.
All collected data is anonymous or pseudonymized. No personal identifiable information, as defined by data protection laws and regulations, such as GDPR, is collected.

  • Data records are identified by a unique id, created with QUuid. No other machine id, network address, IP address or user id is collected.
  • No paths, folder or file names, Qt Creator kit names or project names are collected.
  • IP address, from which the collected data record originates, are not stored in the data collection backend.

Collected data contains only such data sources, which The Qt Company utilizes in one of the following use cases.


  • What new users do to start with Qt?
  • Do they find the essential features? Do they use them?
  • Do they use tutorials and examples? Which ones?
  • Are they stuck with some functionality? For example, open a project but never build that.
  • How behavior changes, when new on-boarding features are added?


  • Where do new Qt users give up?
  • Do they ever successfully use tools, create design, build a project?
  • How much time the same user puts into code analysis, debugging, profiling? How do the times change over time?


  • How do product usage patterns change?
  • What are most/least popular products/features?
  • Which platforms are used?
  • Which compilers are used?
  • Which targets are used?


  • Correlation of download and usage statistics
  • How collected data correlates to data collected in customer surveys?


  • What Qt users would need? What kind of offers, advice or other info?
  • It may be interesting for the community members to see, which platforms are most commonly used or which Qt tools and features Qt developers typically use.

Collected data will be stored into backends under full control of the Qt Company business infrastructure team. The team will create statistics reports for Qt employees, who need the data.

Collected data will be deleted from the backend after five years.
While The Qt Company is willing to delete data a user does not want to share any more, it should be understood that identifying a user-specific data is effectively impossible by the defined rules.

The Qt Company keeps this privacy statement up-to-date by making changes or additions time-to-time. The changed version will be published on