1 min lesson
Turn claims into verifiable controls
Recall the main items in "Turn claims into verifiable controls", then connect each one to the work.
Step 1 of 2
Turn claims into verifiable controls
A privacy statement is useful only when an administrator can enforce it and a reviewer can map it to the actual feature. Record the configuration, data path, subprocessors, retention and deletion evidence used for approval.
- Enforce 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. at the team or organization level when the policy requires no training.
- Document AI requests, 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. as separate flows with their own subprocessors and retention terms.
- Test index deletion, account deletion and Cloud Agent cleanup instead of assuming one control removes every artifact.
Do not turn 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.'s no-training guarantee into a blanket claim that no system stores data. Check current documentation for the feature in scope. 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. require repository storage, while codebase indexing stores embeddings and metadata rather than plaintext code.