Map privacy across each data flow

Cursor's current privacy documentation separates AI requests, codebase indexing and Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition.. Each path handles code differently, so an architecture review must assess them separately.

Start with the current documented guarantees. Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. prevents Cursor and model providers from using code for training. AI requests still send prompts and code context through Cursor and relevant model providers. A no-training guarantee is not a complete data-flow description.