2 min lesson
Privacy Mode and tenant isolation
Match each case in "Privacy Mode and tenant isolation" to the signal and response that fit it.
Step 1 of 2
Privacy Mode and tenant isolationthe retention promise has to be enforced, not just stated
Cursor's 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. commits to not retaining or training on customer code when the customer hasn't permitted it. That's a contractual and reputational promise and the engineering job is to make it structurally true rather than a policy people remember to follow.
Default to not persisting code/prompt content; persist only with an explicit, recorded permission.
Set hard TTLs on anything transient and verify deletion actually happens, not just that a flag flipped.
Keep training pipelines physically unable to read Privacy-Mode data, so a config slip can't leak it in.
Scope every query and storage path by tenant so one customer's data can't surface in another's context.
Carry the tenant boundary into logs, caches and any retrieval/index - these are the sneaky leak paths.
Test cross-tenant access as an abuse case, not just a unit test of the happy path.
The principle from section one applies to data, not just access: the safest data is the data you never kept. Standing access and standing data are the same liability in two shapes. Minimize both, time-box both and audit access to both.
"I treat logging as two jobs that fight each other. For detection I log identities, scopes and actions richly and alert on break-glass and anomalous access. For privacy I keep raw code and prompts out of those logs, 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. by defaulting to no retention with hard TTLs and carry the tenant boundary into every store, cache and index so one customer's data can never appear in another's context."