What data does Cursor collect?
Types of data collected
Cursor collects telemetry data such as which features you use, how often you use them, and any errors or crashes that occur. This helps the team prioritize improvements. The data is typically anonymized and doesn't include your actual code or personal files.
Additionally, Cursor may collect system information like operating system, hardware specs, and extension usage to diagnose compatibility issues. If you use AI features, your code snippets may be sent to the model provider for processing, but this is separate from telemetry and is governed by their privacy policy.
- Usage statistics: feature clicks, command usage, session duration.
- Performance metrics: load times, error rates, crash logs.
- System info: OS, hardware, Cursor version.
- AI interactions: code snippets sent for processing (if using AI features).
How data is used and protected
The collected data is used to fix bugs, improve user experience, and guide development. Cursor states that telemetry data is anonymized and aggregated. For AI features, code is sent to third-party providers (like OpenAI) under their terms; Cursor recommends reviewing those policies if you have concerns.
You can disable telemetry in settings to opt out of most data collection. However, some data may still be sent for essential functions like update checks.
Common mistakes
- Believing that Cursor collects your entire codebase; telemetry is limited to usage and system data.
- Confusing telemetry with AI data processing; they are separate, and AI features send code to model providers.
- Assuming all data collection can be disabled; some essential data may still be transmitted.
