Generated by a model from the captured document; not read by a person
MediumNeutral for users
Affected users
All usersPrivacy mode usersWorkspace administrators
Cursor revised its Privacy Mode data handling disclosures to clarify that while customer data will not be used for training by Cursor itself, AI model providers may store data temporarily if abuse detectors are triggered. The updated policy states that Cursor maintains zero data retention (ZDR) agreements with all providers, but adds that model providers may run risk classifiers and store data for investigation if terms violations are detected. The policy also removed the legacy Privacy Mode option and now requires admins to explicitly opt-in to enable non-ZDR models.
1 obligation expanded1 protection removed
Consumers: Your data may be kept longer than stated if the system detects potential policy violations.
Consumers: The legacy privacy setting is no longer available; workspace admins must actively enable non-ZDR models if needed.
Stay ahead of the changes
Track Cursor and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Generated by a model from the captured document; not read by a person
The updated terms clarify that Cursor maintains zero data retention agreements with all AI model providers and will not use customer data for training. However, the revised language now explicitly states that model providers may run risk classifiers to detect policy violations, and if your prompts or conversations trigger abuse detectors, your data may be stored temporarily for investigation and deleted according to the providers' retention policies. The policy removed the legacy Privacy Mode option; non-ZDR models now require explicit admin opt-in. You can review the specific retention policies of OpenAI and Anthropic through their documentation.
What you can do
→ Review your workspace's Privacy Mode settings to confirm they align with your data handling requirements.
→ If your workspace uses non-ZDR models, confirm that a workspace administrator has explicitly opted in to enable them.
→ Consult OpenAI and Anthropic's retention policies to understand how their abuse detection systems may affect your data.
Key Clauses Affected
Generated by a model from the captured document; not read by a person
Privacy Mode data handling
Clarified that customer data will not be used for training by Cursor, but model providers may temporarily store data if abuse detectors are triggered.
Zero data retention agreements
Established that Cursor maintains ZDR agreements with all providers, but added explicit exception for abuse detection and investigation.
Full clause-by-clause analysis available with Insight.
ⓘ
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
Wording edits to this record that do not change what it claims. Changes to a claim are published as corrections.
2026-10-11 · Feed summary edited · summary regenerated by summarize_events
Previous text Clarifies zero data retention with model providers but adds disclosure that abuse detectors may store data for investigation.
2026-10-11 · Impact summary edited · summary regenerated by summarize_events
Previous text The updated policy clarifies that Cursor maintains zero data retention agreements with all AI model providers and customer data will not be used for training by Cursor. However, the policy now explicitly discloses that model providers may run risk classifiers to detect policy violations, and if your prompts or conversations trigger abuse detectors, your data may be stored for investigation and deleted according to the provider's retention policies. The policy removed the previous blanket statement that code would never be trained on by Cursor or third parties, replacing it with more specific disclosure of abuse detection practices. You can review OpenAI and Anthropic's documentation directly for details on their specific retention policies.
2026-10-11 · Summary edited · summary regenerated by summarize_events
Previous text Cursor updated its privacy policy to clarify that in Privacy Mode, customer data will not be used for training by Cursor, and the company maintains zero data retention (ZDR) agreements with all AI model providers. However, the updated terms now explicitly state that model providers may run risk classifiers to detect policy violations, and if your prompts trigger abuse detectors, your data may be stored for investigation and deleted according to the provider's retention policies. This represents a shift from the previous language, which stated that code would never be trained on by Cursor or third parties, to a more detailed disclosure of abuse detection and retention practices.
2026-10-07 · Change line edited · change line rewritten to the 2026-10-07 template: no detection date, no sentence counts
Previous text Cursor updated their Cursor Data Use & Privacy Overview on June 10, 2026. Change detected: 4 sentence(s) added, 2 sentence(s) removed, 8 sentence(s) modified. Document contained 36 sentences after update.
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
For legal and compliance teams
Institutional Analysis
Generated by a model from the captured document; not read by a person
Assessment
Cursor revised its Privacy Mode disclosure to clarify data handling practices with AI model providers. The change establishes that zero data retention is standard across all providers, but adds explicit language permitting temporary data storage …
🔒Full institutional analysis
Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.
ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-X-002807.
Cursor removed the word 'indexing' from its description of backend functionality. The previous text stated the app makes requests to …
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
Stay ahead of the changes
Track Cursor policy changes
Get alerted when this policy changes again, including what changed and why it matters.