Change record
CA-C-002808
Cursor Security Practices
Entity
Date detected
June 10, 2026
Effective date
June 10, 2026
Severity
Low
Direction
Positive
Taxonomy
Ai training rights
Changes
+4 sentences added · 4 sentences modified

Impact Summary

Low Positive for users
Affected users
All users Pro subscribers Team members

Cursor updated its Privacy Mode documentation on June 10, 2026 to clarify how the feature operates. The updated language separates the availability of Privacy Mode (available to all users, free or Pro) from its default status (enabled by default for team members, inherited by new joiners). New language explicitly states that when Privacy Mode is enabled, Cursor will not train on user data, and adds that technical controls and contractual requirements with model providers protect user data. The practical effect is clearer disclosure of what Privacy Mode does and how it applies to team settings.

Stay ahead of the changes
Track Cursor and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF

What this means for you

The updated terms clarify how Cursor's Privacy Mode functions and when it applies. When enabled, the policy now explicitly states that Cursor will not train on user data, and that technical controls and contractual requirements with model providers protect data. For teams, new members automatically inherit the team's Privacy Mode settings. This is a clarification of existing functionality rather than a new operational restriction or expanded authority.

What you can do

Enable Privacy Mode in personal or team settings to prevent Cursor from training on your code data

For team administrators: Verify that Privacy Mode is enabled by default for your team and that new members inherit this setting

Key Clauses Affected

Privacy Mode training restriction

Updated terms explicitly state that Cursor will not train on user data when Privacy Mode is enabled.

Privacy Mode team inheritance

New team members automatically inherit the team's Privacy Mode settings rather than requiring individual configuration.

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

Evidence Verification

✓ Verified
Previous Version
04fdef38e1310e6e3f564f845b67974206f1aa38bccc1515a1fa667a4f1c5d27
May 12, 2026 05:45 UTC
✓ Verified
Current Version
bcded6ddc5a82d30a160ab5952f4306aaddb934753246d9f95ecb548f3a7a4b0
June 10, 2026 00:57 UTC
✓ Verified
Change Detected
June 10, 2026 00:57 UTC
Analysis Methodology
✓ Verified
Source Document
https://cursor.com/security
Citation Record
Entity: Cursor
Document: Cursor Security Practices
Record ID: CA-C-002808
Captured: 2026-06-10 00:57:07 UTC
URL: https://conductatlas.com/change/2026-06-10-cursor-cursor-security-practices-2808/
Accessed: July 28, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
For legal and compliance teams

Institutional Analysis

Assessment

Cursor revised its Privacy Mode documentation to provide explicit assurances that training will not occur when the feature is enabled, and to clarify how settings propagate within teams. The changes appear to be clarifications of …

🔒 Full institutional analysis

Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.

Unlock the full institutional analysis — Insight

ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-C-002808.

Full Changes

View complete diff →

Document Context

Version history → Policy drift analysis → Document page →
Document
Cursor Security Practices
Entity
Cursor
Captured
June 10, 2026
Source URL
https://cursor.com/security
Other changes to Cursor Security Practices
Next change Jul 16, 2026
Cursor added a new documentation reference titled 'Security and Privacy Hardening' to its list of security best practices in the …
Low Neutral
View full version history →
More from Cursor
Jul 16, 2026 Low
Cursor Security Practices

Cursor added a new documentation reference titled 'Security and Privacy Hardening' to its list of security best practices in the …

Jul 16, 2026 Low
Cursor Data Use & Privacy Overview

Cursor's privacy policy was updated in an update detected on July 16, 2026, with changes to how it describes data …

Jun 10, 2026 Medium
Cursor Data Use & Privacy Overview

Cursor updated its privacy policy to clarify that in Privacy Mode, customer data will not be used for training by …

Related Analysis
Platform Analysis · June 12, 2026
OpenAI Changed Its Privacy Policy 4 Times in One Week. Here Is What Actually Changed.

Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.

Get the research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.

Stay ahead of the changes

Track Cursor policy changes

Get alerted when this policy changes again, including what changed and why it matters.

All Cursor changes →