This notice describes what data JetBrains collects, why, and the user controls
Version 1.6 of the Product Data Collection and Usage Notice, last updated July 7, 2026, says it describes what types of data (such as analytics) JetBrains collects, why it collects the data, and the controls users have when interacting with JetBrains products. It points to the JetBrains Privacy Notice for more detail on collecting data in general.
Supporting quotations
Version 1.6, last updated: July 7, 2026
we describe what types of data (such as analytics) we collect, why we collect it, and the controls you have when interacting with our products
More details on collecting data in general are available in our
Not stated here
The Privacy Notice is linked but not supplied, so what it adds on data collection in general is not analyzed here.
Data Access & Collection · Company commitment
JetBrains says requests for data use opt-in mechanisms and consent can be withdrawn
JetBrains states that any request for such data will be transparent, clearly communicated through opt-in mechanisms and subject to user control, with the ability to withdraw consent at any time.
Supporting quotations
Any request for such data will be transparent, clearly communicated through opt-in mechanisms, and subject to user control, with the ability to withdraw consent at any time.
Qualifications & exceptions
Section 3 of the same notice lets JetBrains collect analytics by default, with an opt-out, from individual developers on a non-commercial license, so opt-in is not the rule for every user.
Not stated here
"Such data" follows the description of "what types of data (such as analytics)"; the notice does not say whether it means every category listed in section 1.
Section 1 says four primary categories of data, then lists six lettered items
Section 1 says that, to improve its products and build its next-generation AI features, JetBrains may collect four primary categories of data. The list that follows is lettered a) to f) and has six items: anonymous telemetry, operational and product metadata, event-based data, behavioral data collection, web-based product trackers, and detailed code-related data. The source does not say which four are the primary categories.
Supporting quotations
To improve our products and build our next-generation AI features, we may collect four primary categories of data:
a) Anonymous telemetry:
f) Detailed code-related data:
Qualifications & exceptions
"May collect" is a permission to collect, not a statement that every category is collected from every user or product.
Not stated here
Which four of the six listed items are the "primary" categories.
JetBrains may collect anonymous statistics about how you use IDE features
Anonymous telemetry is described as generalized, anonymous statistics about the user's interactions with IDE features. It includes feature usage insights such as time spent on the project or mouse clicks.
Supporting quotations
generalized, anonymous statistics about your interactions with IDE features
feature usage insights such as time spent on the project or mouse clicks
Qualifications & exceptions
The examples are introduced with "such as", so they are illustrations, not a complete list.
Section 3 sets consent rules for analytics by license type, and section 4 describes collected analytics as pseudonymized or aggregated.
Not stated here
The notice does not define "anonymous" or say how the statistics are anonymized.
Users of products under the JetBrains AI Terms of Service have operational metadata collected
If a user uses any products under the JetBrains AI Terms of Service, JetBrains collects pseudonymized operational and product metadata, such as API call counts and error rates, and uses it for product improvement. The license table in section 3 adds that JetBrains may collect this operational and product metadata by default on the basis of its legitimate interest in improving its services.
Supporting quotations
If you use any products under the JetBrains AI Terms of Service, JetBrains collects pseudonymized operational and product metadata, such as API call counts and error rates.
This data is used for product improvement.
We may collect operational and product metadata as specified above by default based on our legitimate interest to improve our services.
Qualifications & exceptions
Applies if you use products under the JetBrains AI Terms of Service.
The data is described as pseudonymized, not anonymous.
Not stated here
The JetBrains AI Terms of Service are linked but not supplied.
The API call counts and error rates are examples ("such as"), so the full range of metadata is not stated.
Pseudonymized session data is collected with masking and is not used to train AI
JetBrains may also collect pseudonymized session data, which it uses for product improvement. It says it applies extensive masking protection of session fields so that the collected data does not include direct personal identifiers, source code, uploaded files or user prompts, and that it does not train its AI on this data.
Supporting quotations
We may also collect pseudonymized session data.
This data is used for product improvement, and we apply extensive masking protection of session fields, so the collected data does not include any direct personal identifiers, source code, uploaded files or user prompts.
We do not train our AI on this data.
Qualifications & exceptions
The identifier exclusion is for "direct" personal identifiers.
"May collect" is a permission, not a statement that every user's sessions are collected.
Not stated here
The notice does not say what masking is applied or how session fields are chosen.
The notice does not say whether indirect identifiers can remain in pseudonymized session data.
Data Access & Collection · Company practice
The JetBrains AI service can collect behavioral data to analyze usage and train feature-control models
The JetBrains AI service can collect behavioral data to analyze product usage, improve product features, and train machine learning (ML) models that control the behavior of different product features, for example controlling the automatic activation of ML features.
Supporting quotations
The JetBrains AI service can collect this data to analyze product usage, improve product features, and train machine learning (ML) models that control the behavior of different product features (for example, controlling the automatic activation of ML features).
Qualifications & exceptions
"Can collect" is a permission stated for the JetBrains AI service.
Not stated here
The notice does not list what behavioral data consists of.
JetBrains may collect and store cookies and similar trackers in web-based products
When users use JetBrains web-based products, JetBrains may collect and store trackers such as cookies. The notice points to a separate page for more detail.
Supporting quotations
We may collect and store trackers such as cookies when using web-based products.
Qualifications & exceptions
Applies when using web-based products.
"Such as" makes cookies an example of trackers, not the whole category.
Not stated here
The linked website products cookie page is not supplied, so the specific trackers and purposes are not analyzed here.
Data Access & Collection · Company practice
Detailed code-related data can include full inputs to and responses from large language models, with source code
Detailed code-related data collection includes general IDE usage, such as terminal usage (command runs) or edit history, and uses analytics from the user's AI feature usage. It includes complete data about interactions with large language models: the full text of inputs the IDE sends to the model and its responses, including source code snippets. JetBrains says the collected data may contain personal, business or project-specific information.
Supporting quotations
This data collection includes general IDE usage, such as terminal usage (command runs) or edit history, and utilizes analytics from your AI features usage.
This means the full text of inputs sent by the IDE to the large language model and its responses, including source code snippets.
The data collected may contain personal, business, or project-specific information.
Qualifications & exceptions
Collection of this data depends on the license type and consent or admin settings set out in section 3.
Detailed code-related data collection is described as possible, not as happening for every user.
Not stated here
The notice does not list every kind of "general IDE usage" it includes beyond terminal usage and edit history.
Cross-references
contrast (model-proposed): Collected analytics are pseudonymized or aggregated and not directly linked to your account — Section 1 says detailed code-related data may contain personal, business or project-specific information; section 4 says collected analytics do not directly link to an account. The notice does not say whether section 4 covers detailed code-related data.
Data Access & Collection · Restriction or exception
Detailed code-related data is not collected from commercial users without prior explicit, informed consent
JetBrains says it does not collect detailed code-related data from its commercial users unless explicit, informed consent has been obtained in advance. It also says it has a safeguard that disallows data sharing for organizations unless there is explicit permission at company level.
Supporting quotations
We do not collect Detailed code-related data from our commercial users unless explicit, informed consent has been obtained in advance.
We have a safeguard in place that disallows data sharing for organizations unless there's an explicit permission on a company level.
Qualifications & exceptions
The consent condition is for "commercial users"; the table in section 3 treats individual developers on a non-commercial license differently, with collection by default and an opt-out.
For organizations the safeguard turns on explicit permission at company level.
Not stated here
"Commercial users" is not defined.
"Data sharing" for organizations is not defined, for example whether it means sharing with JetBrains or with others.
Data sharing preferences, once configured, apply to all installed JetBrains products
JetBrains says that once the user configures these data sharing preferences they apply to all JetBrains products installed.
Supporting quotations
Note that these data sharing preferences, once configured, apply to all installed JetBrains products.
Qualifications & exceptions
Applies once the preferences are configured.
Not stated here
"These data sharing preferences" follows the description of detailed code-related data; the notice does not say whether the same cross-product rule covers other analytics settings.
Detailed code-related data can be collected in most listed IDEs as of version 2025.3.1
The table lists, for each JetBrains IDE, the version as of which detailed code-related data can be collected. CLion, DataGrip, DataSpell, GoLand, PhpStorm, Rider, RubyMine, RustRover and WebStorm are each listed at 2025.3.1. The unified distributions of IntelliJ IDEA and PyCharm are also listed at 2025.3.1, with the note that when switching to Community, detailed data sharing is disabled and can't be enabled.
Supporting quotations
Detailed code-related data can be collected in the JetBrains IDEs as of the following versions:
IntelliJ IDEA (unified distribution) 2025.3.1; when switching to Community, detailed data sharing is disabled and can't be enabled
PyCharm (unified distribution) 2025.3.1; when switching to Community, detailed data sharing is disabled and can't be enabled
CLion 2025.3.1
DataGrip 2025.3.1
DataSpell 2025.3.1
GoLand 2025.3.1
PhpStorm 2025.3.1
Rider 2025.3.1
RubyMine 2025.3.1
RustRover 2025.3.1
WebStorm 2025.3.1
Qualifications & exceptions
The table says what can be collected as of a version; whether data is collected depends on the license type and consent or admin rules in section 3.
For the IntelliJ IDEA and PyCharm unified distributions, switching to Community disables detailed data sharing.
Not stated here
The table gives a starting version and does not state an end version for any IDE.
Data Access & Collection · Restriction or exception
Legacy Community IDEs are listed as disabled, and several other products as not applicable
In the version table, the legacy Community versions of IntelliJ IDEA and PyCharm are listed as "Disabled, can’t be enabled". The legacy IntelliJ IDEA (Ultimate) and PyCharm Professional versions, Fleet, and ReSharper and ReSharper C++ are listed as "Not applicable".
Supporting quotations
IntelliJ IDEA (Ultimate) [legacy version] Not applicable
IntelliJ IDEA (Community) [legacy version] Disabled, can’t be enabled
PyCharm Community [legacy version] Disabled, can’t be enabled
PyCharm Professional [legacy version] Not applicable
Fleet Not applicable
ReSharper, ReSharper C++ Not applicable
Qualifications & exceptions
Rows marked legacy refer to the legacy versions; the unified distributions are listed separately at 2025.3.1.
Not stated here
The notice does not explain what "Not applicable" means in this table, for example whether those products do not collect this data or are not covered.
Data Access & Collection · User right or choice
Analytics are collected with explicit consent unless the license table below says otherwise
Section 3 says that unless specified below, JetBrains collects the analytics described above with the user's explicit consent, and that the user can always check and change preferences in the product settings. The table that follows sets the rule by user category and license type.
Supporting quotations
Unless specified below, we collect analytics specified above with your explicit consent.
You can always check and change your preferences in the product settings.
Qualifications & exceptions
"Unless specified below" means the table rows and notes for non-commercial individual developers, free Community IDEs, remote development mode and Code With Me can differ.
Not stated here
"Analytics specified above" is not defined; the notice does not say whether it covers every category in section 1, such as web trackers or detailed code-related data.
Individual developers on a non-commercial license may have analytics collected by default, with an opt-out
In the license table, for the individual developer on a non-commercial license, JetBrains says it may collect the analytics described above by default based on its legitimate interest, and that the user may opt out in the product settings.
Supporting quotations
Individual developer Non-commercial license
We may collect analytics as specified above by default based on our legitimate interest. You may opt out in the product settings.
Qualifications & exceptions
Applies to the non-commercial license row only.
The stated basis is JetBrains' legitimate interest.
The user can opt out in the product settings.
Not stated here
The column is headed "Detailed code-related data collection" but the cell speaks of "analytics as specified above", so the notice does not say whether the default includes detailed code-related data. Section 1 f) says detailed code-related data is not collected from commercial users without consent, and is silent about non-commercial users.
contrast (model-proposed): JetBrains says requests for data use opt-in mechanisms and consent can be withdrawn — The general statement that requests for data use opt-in mechanisms sits beside a table row that lets JetBrains collect analytics by default, with an opt-out, from individual developers on a non-commercial license. The notice does not reconcile the two.
Individual commercial, trial and Early Access Program users: collection starts only with explicit consent
In the license table, for individual (commercial), Trial or Early Access Program users, JetBrains says it starts collecting analytics only with the user's explicit consent, and the user can check and change preferences in the settings at any time.
Supporting quotations
Individual (commercial), Trial, or Early Access Program
We start collecting analytics only with your explicit consent. You can check and change your preferences anytime in the settings.
Qualifications & exceptions
Applies to the license types named in the row: individual (commercial), Trial, or Early Access Program.
Preferences can be checked and changed at any time in the settings.
Not stated here
The table shows the "Individual developer" label only on its first row of this group; this card relies on the license type text in the row, not on that label.
The cell speaks of "analytics" under a "Detailed code-related data collection" column, so the exact data covered is not stated.
Data Access & Collection · Restriction or exception
Organizational license: explicit consent, and detailed code-related data only if a company admin allows it
In the license table, for organizational licenses, JetBrains says it starts collecting analytics only with the user's explicit consent. For detailed code-related data it asks for explicit consent only if the company admin has allowed such collection, and it says collecting detailed code-related data is disallowed by default and can only be enabled by a company admin. The user can check and change preferences in the settings. Section 1 describes a safeguard that disallows data sharing for organizations unless there is explicit permission at company level.
Supporting quotations
Organizational license
We start collecting analytics only with your explicit consent. In case of detailed code-related data collection, we ask for your explicit consent only if the company admin has allowed such data collection.
Additionally, collecting Detailed code-related data is disallowed by default and can only be enabled by a company admin.
We have a safeguard in place that disallows data sharing for organizations unless there's an explicit permission on a company level.
Qualifications & exceptions
Applies to organizational licenses.
Detailed code-related data collection is off by default and is enabled only by a company admin.
The user's explicit consent is described as being asked for only if the admin has allowed collection.
Not stated here
The notice does not say whether the user's consent is still needed once a company has enabled collection at company level; the Company row says the company-level setting applies to all end users and cannot be adjusted individually.
Data Access & Collection · Restriction or exception
Free Community versions of IntelliJ IDEA and PyCharm have data collection disabled
In the license table, for the free Community versions of IntelliJ IDEA and PyCharm, data collection is disabled and cannot be enabled, because the Community edition has no setting to turn data collection on. The version table says the same for detailed data sharing when a unified distribution is switched to Community.
Supporting quotations
Free Community versions of IntelliJ IDEA and PyCharm
Data collection is disabled and can’t be enabled. The Community edition doesn’t include a setting to turn data collection on.
when switching to Community, detailed data sharing is disabled and can't be enabled
Qualifications & exceptions
Applies to the free Community versions of IntelliJ IDEA and PyCharm.
Not stated here
The next row covers "free community licenses" with explicit consent; the notice does not say how that row relates to these free Community IDEs.
Free community licenses: collection starts only with explicit consent
In the license table, for free community licenses (open-source, students, classroom, content creators, user groups, and the Developer Recognition Program), JetBrains says it starts collecting analytics only with the user's explicit consent, and the user can check and change preferences in the settings at any time.
Supporting quotations
Free community licenses (open-source, students, classroom, content creators, user groups, and Developer Recognition Program)
We start collecting analytics only with your explicit consent. You can check and change your preferences anytime in the settings.
Qualifications & exceptions
Applies to the free community license programs named in the row.
Not stated here
The cell speaks of "analytics" under a "Detailed code-related data collection" column, so the exact data covered is not stated.
Data Access & Collection · Permission or license
A company can opt in to detailed code-related data by contract, and the setting applies to all its end users
In the license table, for companies on an organizational license, JetBrains says a company can opt in to detailed code-related data by signing a contract with JetBrains. When enabled at company level, the setting applies to all end users and cannot be adjusted individually. The row points to a page for more details and to join the waitlist.
Supporting quotations
The company can opt in to detailed code-related data by signing a contract with JetBrains.
When enabled at the company level, this setting applies to all end users and cannot be adjusted individually.
For more details and to join the waitlist,
Qualifications & exceptions
Requires a signed contract with JetBrains.
When enabled at company level it applies to all end users and cannot be adjusted individually.
Not stated here
The linked data collection program page is not supplied, and the contract terms are not in this notice.
The notice does not say whether the user's explicit consent described in the organizational license row is still asked for after a company opts in.
Data Access & Collection · Restriction or exception
In remote development mode the IDE does not offer the option to enable data collection
For all license types, when working in remote development mode the IDE does not offer the option to enable data collection.
Supporting quotations
All license types When working in remote development mode, the IDE does not offer the option to enable data collection.
Qualifications & exceptions
Applies to all license types, in remote development mode.
Not stated here
The row sits under a "Detailed code-related data collection" column but says "data collection"; the notice does not say whether it covers all analytics or only detailed code-related data.
Data Access & Collection · Restriction or exception
Code With Me: hosts follow their license rules, guests have data collection disabled
For all license types, in Code With Me the host behaves as a regular IDE setup and the standard rules for the relevant license type apply. For a guest, data collection is disabled, and there is no toggle to enable it in the IDE's settings menu.
Supporting quotations
All license types
Host: Behaves as a regular IDE setup, and all the standard rules associated with the relevant license type apply.
Guest: Data collection is disabled. There is no toggle to enable it in the IDE’s settings menu.
Qualifications & exceptions
Different for host and guest.
Not stated here
The row says "data collection"; the notice does not say whether it covers all analytics or only detailed code-related data.
Data Access & Collection · Company practice
Products under the JetBrains AI Terms: marketing analytics need consent; operational metadata is collected by default
In the license table, for products under the JetBrains AI Terms of Service, JetBrains says that for marketing purposes it only starts collecting analytics with the user's consent. It says it may collect operational and product metadata, as described above, by default on the basis of its legitimate interest in improving its services.
Supporting quotations
For marketing purposes, we only start collecting analytics with your consent.
We may collect operational and product metadata as specified above by default based on our legitimate interest to improve our services.
Qualifications & exceptions
Applies to products under the JetBrains AI Terms of Service.
Marketing analytics need consent; operational and product metadata is by default, based on legitimate interest.
Not stated here
The JetBrains AI Terms of Service are linked but not supplied.
The row has no license type, and the notice does not say how it combines with the other rows when a user is in both.