Data collection

Number of active users (approximated), grouped by their type of action:

• other_actions — number of unique users that had NO action in Toolbox App and IDE Services Plugin (only used Web UI or API)

• tba_actions — number of unique users that had AT LEAST ONE action in Toolbox App (they touched Toolbox App, maybe Web UI, but not IDE Services Plugin)

• tbe_actions — number of unique users that had AT LEAST ONE action in IDE Services Plugin (they touched IDE Services Plugin, maybe Web UI, but not Toolbox App)

• tba_tbe_actions — number of unique users that had AT LEAST ONE action in Toolbox App and IDE Services Plugin (they touched Toolbox App and IDE Services Plugin, maybe Web UI)

• total — total number of unique users recorded

The numbers are approximated (bucketed), which means that transmitted values are not exact but fall within preset ranges. IDE Services doesn’t send the exact count, instead it reports the highest number in this sequence—0, 1, 2, 4, 8, 13, 21, 30, 40, 50, 75, 100, 200, 400, 800, 1600, 3200, 6400—that is less than or equal to the actual value. For example, if there are 15 users, IDE Services will report 13.

Daily

Enabled by default. Can be disabled by setting tbe.fus-server.allow-sending-usage-analytics: false

In the application.yaml file (value.yaml for Kubernetes setup)

General server information:

• Event ID (for actions described above)

• Country code

• Date (Year/Month/Day)

• Time (epoch)

• Organization identifier (a random UUID for recognizing organizations as separate entities; cannot be linked to any specific organization or customer)

Version of your IDE Services Server

License verification data.

Each IDE Services Server has a unique identifier which serves to associate your instance with the corresponding IDE Services license registered on your JetBrains Account.

This server identifier is sent to JetBrains:

• as part of the activation link when you initially activate your IDE Service instance;

• when your IDE Service license is refreshed either automatically or manually on the Configuration | License & Activation page.

Upon IDE Services activation.

Automatically, every 2 hours.

Manually, by hitting Refresh license on the License & Activation page.

Compulsory

Usage reports for billing purposes.

IDE Services automatically collects, aggregates, and sends reports containing the following consumption details of the IDE Services products:

• Number of users with IDE Provisioner enabled in at least one profile. The resulting consumption is the highest number of IDE Provisioner users in a single day within a month.

• Number of licenses used in each billing period (for pay-as-you-go billing model) or the number of licenses distributed in Floating mode (for prepaid billing model).

• Maximum number of concurrent Code With Me sessions in a single day within a month.

• Number of users with AI Enterprise enabled in at least one profile. The resulting consumption is the highest number of AI Enterprise users in a single day within a month.

Automatically sent every hour regardless of your billing model when your IDE Services instance is in online mode.

Manually, by submitting a generated usage report file to JetBrains if your IDE Services instance is in offline mode.

Always sent to JetBrains when in online mode, regardless of your billing model.

Mandatory manual submission for pay-as-you go billing model in offline mode.

Manual submission not required for prepaid billing model in offline mode.

IDE name and build number when querying plugin artifacts from JetBrains Marketplace and CDNs

In order to install plugins from JetBrains Marketplace, the correct distribution must be picked based on the currently running IDE.

When the user installs a plugin

Compulsory

Username (login email)

• No data transfer

Compulsory

IP addresses

• No data transfer

Compulsory

Machine ID

• No data transfer

Compulsory

OS hostname

• No data transfer

Compulsory

Product codes (for license usage statistics)

• Every 2 hours

Compulsory

Product versions (for license usage statistics)

• Every 2 hours

Compulsory

Product build numbers (for license usage statistics)

• Every 2 hours

Compulsory

Allocated licenses (for license usage statistics)

• Every 2 hours

Compulsory

Applications, such as IDEs distributed by your IDE Services instance, that include AI features can collect and send to JetBrains two types of data related to AI usage: behavioral data and detailed data.

When AI Enterprise is enabled allowing the use of AI features in your organization.

Behavioral data:

• Types of AI features used.

• Rates of acceptance for suggestions from different AI features.

• Performance data (such as the amount of time it took to generate AI suggestions).

• User feedback on the quality of results produced by different AI features.

Behavioral data does not include any personally identifiable data, or any source code files or fragments from the users’ projects.

Collected by JetBrains only when JetBrains AI is used as an AI provider.

If custom OpenAI models (OpenAI Platform, Azure OpenAI or Gemini) are used, no data is collected by JetBrains and is instead sent directly to the selected AI provider.

Collection of this type of data can’t be controlled centrally from your IDE Services. It is controlled on the user’s end by the application’s data sharing settings.

Enabled by default in applications’ EAP builds and disabled by default in release builds.

Detailed data:

• Complete information about interactions with large language models.

• Full text of inputs sent by the IDE to the large language model.

• Responses from the large language model.

• Source code snippets included in interactions.

If collected, detailed data will be stored by JetBrains only for a limited amount of time not exceeding one year.

Collection of this type of data can be controlled centrally from your IDE Services instance for each profile in the AI Enterprise tab.

If disabled in IDE Services, end users cannot override this setting in their applications. However, if enabled, end users can still opt out of detailed data collection within their applications.

Disabled by default.