Product Data Collection and Usage Notice

JetBrains · agreement dated July 7, 2026 · Official agreement

Read the agreement

36 of 36 cards

Data Access & Collection · Context

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.

Cross-references

Data Access & Collection · Context

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.
Also annotated in the same passage (6)

Data Access & Collection · Company practice

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.
Also annotated in the same passage (1)

Data Access & Collection · Company practice

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.
Also annotated in the same passage (2)

Use & Processing · Restriction or exception

Operational metadata is not used for marketing without consent and not used to train AI

For operational and product metadata, JetBrains says that unless the user gives consent it does not use this data for any marketing activities, and that it does not train its AI on this data. The license table repeats the marketing point for products under the JetBrains AI Terms of Service: for marketing purposes JetBrains only starts collecting analytics with the user's consent.

Supporting quotations

Unless you provide us with your consent, we do not use this data for any marketing activities.
We also do not train our AI on this data.
For marketing purposes, we only start collecting analytics with your consent.

Qualifications & exceptions

  • The marketing exclusion lifts if the user provides consent.
  • The AI-training exclusion is stated with no consent exception.
  • Limited to the operational and product metadata described in item b).

Not stated here

  • Section 2 lists marketing and training "our own AI models" among the purposes of collection; the notice does not map those purposes to each category beyond these exclusions.

Cross-references

Also annotated in the same passage (2)

Data Access & Collection · Company practice

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.
Also annotated in the same passage (1)

Use & Processing · Restriction or exception

Behavioral data is not used to train code or text generation models and excludes personal data and source code

JetBrains says behavioral data is not used for training ML models that generate code or text, or for other types of data from which outputs can be extracted. It also says behavioral data does not include any personally identifiable data or any source code files or fragments from the user project.

Supporting quotations

It is not used for training ML models that generate code or text, or for other types of data from which outputs can be extracted.
Behavioral data does not include any personally identifiable data or any source code files or fragments from the user project.

Qualifications & exceptions

  • Stated for behavioral data (item d) only.

Not stated here

  • The phrase "or for other types of data from which outputs can be extracted" is not defined, and its grammar does not make clear whether it adds a second kind of excluded model training or a second kind of excluded data.
Also annotated in the same passage (1)

Data Access & Collection · Company practice

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

Also annotated in the same passage (5)

Use & Processing · Permission or license

Detailed code-related data can be used for product improvement and to train AI models

JetBrains says detailed code-related data can be used for product improvement and for training AI models. This differs from operational and product metadata and event-based data, for which JetBrains says it does not train its AI.

Supporting quotations

Detailed code-related data can be used for product improvement and training AI models.

Qualifications & exceptions

  • "Can be used" is a permission; the notice does not say every record is used for each purpose.

Not stated here

  • Section 1 f) does not say whose AI models are trained; section 2 names training "our own AI models" as a purpose.
Also annotated in the same passage (5)

Retention & Deletion · Company practice

Detailed code-related data is retained for one year

JetBrains says it applies a one-year data retention period to detailed code-related data.

Supporting quotations

We apply a 1-year data retention period for this data.

Qualifications & exceptions

  • Stated for detailed code-related data ("this data") only.

Not stated here

  • The notice does not state retention periods for the other categories; the Privacy Notice is not supplied.
  • The notice does not say what happens when the one-year period ends, or whether the year runs from collection.
Also annotated in the same passage (5)

Data Access & Collection · User right or choice

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.
Also annotated in the same passage (1)

Data Access & Collection · Restriction or exception

Detailed data is not currently collected in China

JetBrains says it does not currently collect detailed data in China.

Supporting quotations

Detailed data is not currently collected in China.

Qualifications & exceptions

  • "Currently" makes this a statement about present practice, not a permanent commitment.
  • Stated for "Detailed data", which follows the detailed code-related data description.

Not stated here

  • The notice does not say how collection is determined to be "in China" (for example by user location, account or installation).
Also annotated in the same passage (1)

Data Access & Collection · Context

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.
Also annotated in the same passage (1)

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.

Use & Processing · Company practice

JetBrains lists five purposes for which it collects only the data necessary

JetBrains says its primary goal is to provide tailor-made, data-based tools and that it collects only the data necessary for five purposes: product analytics, model evaluation, security and audibility, training its own AI models, and marketing.

Supporting quotations

Our primary goal is to provide you with tailor-made, data-based tools.
we collect only the data necessary for the following purposes: product analytics, model evaluation, security and audibility, training our own AI models, and marketing.

Qualifications & exceptions

  • Limited to "only the data necessary" for the listed purposes, as JetBrains describes it.
  • Section 1 narrows some categories: operational and product metadata and event-based data are not used to train AI, and operational and product metadata is not used for marketing without consent.

Not stated here

  • The notice does not map each purpose to each data category.
  • "Security and audibility" appears as written in the source; the notice does not explain "audibility".

Cross-references

Also annotated in the same passage (1)

Legal Rights & Agreement Rules · Company commitment

JetBrains says data you share is handled in full compliance with EU data protection laws

JetBrains says it respects both individual and corporate privacy policies and that any data a user shares will be handled responsibly and in full compliance with EU data protection laws.

Supporting quotations

We respect both individual and corporate privacy policies.
Any data you share will be handled responsibly and in full compliance with EU data protection laws.

Qualifications & exceptions

  • The commitment names EU data protection laws; this passage does not mention other jurisdictions.

Not stated here

  • The notice does not name the JetBrains entity responsible for the data or say how this commitment applies to users outside the EU.
  • "Individual and corporate privacy policies" is not defined.
Also annotated in the same passage (1)

Data Access & Collection · Company practice

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.

Cross-references

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.

Cross-references

Also annotated in the same passage (1)

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.

Cross-references

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.
Also annotated in the same passage (2)

Legal Rights & Agreement Rules · Context

The Privacy Notice has more on rights and how to file a complaint

JetBrains says its Privacy Notice provides more details on user rights and how to exercise them, including how to file a complaint.

Supporting quotations

provides more details on your rights and how you can exercise them, including how to file a complaint.

Not stated here

  • The Privacy Notice is linked but not supplied, so the rights and complaint process it describes are not analyzed here.

Security & Safeguards · Company commitment

JetBrains says it designs safeguards to protect user information and the intellectual property in code and usage data

JetBrains says it strives for the highest security and privacy standards and that its processes are designed with robust safeguards to protect user information. It recognizes that code and usage data are sensitive and may contain confidential information, and says its data handling and security protocols are designed to protect the user's intellectual property throughout the data lifecycle.

Supporting quotations

We continue to strive for the highest security and privacy standards. Our processes are designed with robust safeguards to protect your information.
We recognize that code and usage data are sensitive and may contain confidential information. Our data handling and security protocols are designed to protect your intellectual property throughout the data lifecycle.

Qualifications & exceptions

  • Worded as efforts and design aims ("strive", "designed to"), not as guarantees.

Not stated here

  • The notice does not describe specific safeguards beyond the bullets that follow.

Security & Safeguards · Company commitment

Access to raw data is restricted, and attempts to de-identify users are strictly prohibited

JetBrains says access to raw data is highly restricted to authorized personnel, and that it strictly prohibits any attempts to de-identify users.

Supporting quotations

Access to raw data is highly restricted to authorized personnel.
We strictly prohibit any attempts to de-identify users.

Qualifications & exceptions

  • Access to raw data is limited to authorized personnel.

Not stated here

  • "Raw data" and "authorized personnel" are not defined.
  • The notice does not say who is bound by the de-identification prohibition or how it is enforced.

Retention & Deletion · Company commitment

Collected data remains stored within the European Economic Area

JetBrains says the collected data remains stored within the European Economic Area (EEA).

Supporting quotations

The collected data remains stored within the European Economic Area (EEA).

Qualifications & exceptions

  • Stated about where the collected data is stored.

Not stated here

  • "The collected data" is not limited to a category; the notice does not say which categories it covers.
  • The notice does not say whether the data can be accessed or transferred from outside the EEA, or where processors operate.

Legal Rights & Agreement Rules · Procedure

Questions go to an AI platform email address; a Trust Centre and an FAQ hold more detail

For questions about data collection, JetBrains gives an email address to reach out to. It points to its Trust Centre for more detail on how it protects data, including its certifications, and to a frequently asked questions page about detailed code-related data collection.

Supporting quotations

In case of any questions regarding data collection, please reach out to
More details on how we protect data, including our certifications, are available in our
Frequently asked questions about detailed code-related data collection

Not stated here

  • The Trust Centre and the FAQ page are linked but not supplied, so the certifications and FAQ answers are not analyzed here.