Contents

• dbForge Edge
• Data storage and transmission policy

Data storage and transmission policy

Continuous improvement of user experience and fast troubleshooting are two of the primary goals set forth by Devart. For this purpose, dbForge Edge collects anonymous telemetry data regarding feature usage and error reports, as well as sends product activation data and conducts weekly checks for updates.

dbForge Studios do not collect any other data, including data from databases, database structure information, server names, IP addresses, T-SQL queries, etc. The collected data is strictly limited to what is described below.

The guide provides the following topics:

• Data collected and transmitted by dbForge Studio to the Devart server
• Data stored by dbForge Studio on the local machine
  • Data stored in the Windows Registry
  • Data stored in the file system

Data collected and transmitted by dbForge Studio to the Devart server

Note

The connection for the following data transmissions is encrypted and authenticated using TLS 1.2, ECDHE_RSA with P-256, and AES_128_GCM.

1. dbForge Studio anonymously collects and sends the following telemetry data to the Devart server:

• Product and license information
• Operating system details: version, user SID, and regional settings
• Hardware information: CPU details, screen resolution, memory capacity, etc.
• Types and versions of database servers
• Application launch and feature usage statistics
• Information on user preferences in application settings
• Error statistics

To disable telemetry, go to the Tools menu > Options > Environment > General and clear the Allow sending anonymous usage statistics checkbox.

2. dbForge Studio sends the following data to the application update service to conduct weekly checks for available product updates:

• Application identifier
• Application version

To disable weekly checks for updates, go to the Tools menu > Options > Environment > General and clear the Check for updates at startup once a week checkbox.

3. dbForge Studio sends the following data to the Devart server when you activate the product:

• Activation key
• Application identifier
• PC name
• Windows username

dbForge Studio can be activated on the Help menu > Activate Product.

4. You can send an error report when encountering an error. In this case, if you click Send Report, the following data will be sent to the Devart server:

• Current application status: loaded modules, open windows, documents, and projects
• License information: trial status and hardware ID
• Error information
• Environment information: operating system details, local settings, display device settings, and UAC status

Note

The abovementioned information will be shown in the error report dialog, so you will be able to check it before sending us the report.

Data stored by dbForge Studio on the local machine

The following data is stored on the local machine with dbForge Studio installed. This data is not sent anywhere, and Devart has no access to it.

Data stored in the Windows Registry

Note

Since dbForge Edge is a bundle comprising four individual products - dbForge Studio for SQL Server, dbForge Studio for MySQL, dbForge Studio for Oracle, and dbForge Studio for PostgreSQL - the data pertaining to each of these products will be stored in their respective hives in the Windows registry.

The Computer\HKEY_CURRENT_USER\SOFTWARE\Devart\dbForge Studio for [SQL Server]/[MySQL]/[Oracle]/[PostgreSQL] registry key stores various settings relevant to the dbForge Studio tool. They include configurations for applications, folders, paths, and other settings kept in the corresponding folders.

The Computer\HKEY_CURRENT_USER\SOFTWARE\Devart\dbForge Common Settings registry key stores connections and categories settings located in the corresponding folders of the specific tool.

Data stored in the file system

The local system drive contains the folder C:\Users\username\AppData\Roaming\Devart\dbForge Studio for [SQL Server]/[MySQL]/[Oracle]/[PostgreSQL] that stores various data related to the dbForge Studio tool. Within this directory, you can find the folders that store query execution history, document sessions, formatting profiles, and shortcut schemes. In addition, specific settings such as application log files, window and toolbar layout settings files, and application cache files are stored as separate files.

You can turn off the query execution history by going to the Tools menu and selecting Options. In the Options dialog that opens, navigate to Environment > Documents > Execution History and clear the Enable history checkbox. To remove the execution history, click Clear Execution History.

Want to Find out More?

• Previous
• Next