Cursor

Cursor Privacy Mode: telemetry, training and data retention

Does Cursor store or train on my code?

With Privacy Mode on, Cursor says customer data is not used for training and it has zero data retention agreements with its model providers, though providers may run abuse classifiers. With Privacy Mode off, Cursor may store and use codebase data, prompts and editor actions to improve its features. Privacy Mode is available on every plan.

Privacy Mode on

  • Your data is not used for training by Cursor.
  • Zero data retention agreements with model providers.
  • Exception: providers, including Cursor, may run risk classifiers and may keep data that triggers abuse detection.
  • File contents may be cached temporarily on Cursor's servers, encrypted with client-generated keys, and are not used for training.

Privacy Mode off

Cursor may use and store codebase data, prompts, editor actions and code snippets to improve its AI features and train models.

Good to know

  • Turn it on in Cursor's settings; team and enterprise admins can enforce it, and new members inherit the team setting.
  • Using your own API key does not bypass Cursor's backend: requests still go through it for prompt building.

Sources

Cursor: Data useCursor: Security

More on Cursor

Cursor standards supportAdd MCP servers to CursorCursor rules

Other guides

Cursor: allow all terminal commandsClaude Code: allow commands without promptsCodex CLI: approval and sandbox modesGemini CLI: YOLO mode, auto_edit and allowing specific shell commandsClaude Code telemetry and data retention: what is sent and how to turn it offGemini CLI: turn off usage statistics and telemetry

Get the weekly agent stack update

New official MCP servers, spec changes and harness releases, checked against the source. One email a week, no fluff.

Reviewed Oct 6, 2026. Settings change often; the linked vendor docs are the source of truth.