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

Impact Summary

Generated by a model from the captured document; not read by a person
Low Positive for users
Affected users
All users Pro subscribers Team members

Cursor revised its Privacy Mode documentation to clarify how the feature works and what protections it provides. The updated language states that when Privacy Mode is enabled, Cursor will not train on user data, and implements technical controls and contractual requirements with model providers to protect data. The change also specifies that new team members inherit their team's Privacy Mode settings by default, rather than requiring individual configuration.

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.
Share 𝕏 Share in Share 🔒 PDF

What this means for you

Generated by a model from the captured document; not read by a person

The updated terms clarify that Privacy Mode, available to both free and Pro users, prevents Cursor from training on user data when enabled. The revised language explicitly states that Cursor implements technical controls and contractual requirements with model providers to protect data. New team members now automatically inherit their team's Privacy Mode settings rather than requiring manual configuration.

What you can do

→ Enable Privacy Mode in your Cursor settings if you want to prevent training on your code data

→ Verify that your team's Privacy Mode settings are configured as intended for new team members

Key Clauses Affected

Generated by a model from the captured document; not read by a person
Privacy Mode data training restriction

Explicitly states that when enabled, Cursor will not train on user data

Privacy Mode team member inheritance

New team members now automatically inherit their team's Privacy Mode settings

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
Record history

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 Privacy Mode settings, default status for teams, and adds explicit statement that training will not occur when feature is enabled.
2026-10-11 · Impact summary edited · summary regenerated by summarize_events
Previous text
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.
2026-10-11 · Summary edited · summary regenerated by summarize_events
Previous text
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.
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 Security Practices on June 10, 2026. Change detected: 4 sentence(s) added, 4 sentence(s) modified. Document contained 48 sentences after update.
Citation Record
Entity: Cursor
Document: Cursor Security Practices
Record ID: CA-X-002808
Version: CA-V-003612
Captured: 2026-06-10 00:57:07 UTC
URL: https://conductatlas.com/change/2026-06-10-cursor-cursor-security-practices-2808/
Accessed: Oct. 27, 2026
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

This change is a clarification and operational improvement to Cursor's Privacy Mode feature documentation. It does not introduce new data practices but rather clarifies existing protections and streamlines team onboarding. No new regulatory obligations appear …

🔒 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-X-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 Aug 29, 2026
Cursor removed the word 'indexing' from its description of backend functionality. The previous text stated the app makes requests to …
Low Neutral
View full version history →
More from Cursor
Oct 12, 2026 Medium
Cursor Privacy Policy

Cursor updated its Privacy Policy date from September 29, 2026 to October 11, 2026. The policy also revised its payment …

Oct 1, 2026 Medium
Cursor Privacy Policy

Cursor's Privacy Policy removed its explicit statement that it does not 'sell' or 'share' personal data for cross-contextual behavioral advertising …

Aug 29, 2026 Low
Cursor Security Practices

Cursor removed the word 'indexing' from its description of backend functionality. The previous text stated the app makes requests to …

Related Analysis
Privacy · May 8, 2026
Meta Removed 438 Sentences From Its Privacy Policy. Here Is What Disappeared.

ConductAtlas detected a major restructuring of Meta’s privacy policy that removed detailed consumer rights disclosures and relocated them t…

Privacy · May 7, 2026
TikTok Rewrote Its Privacy Policy After a $600M EU Fine

ConductAtlas tracked the restructuring, new disclosures, and entity changes that followed the largest privacy fine in EU history.

Privacy · April 16, 2026
23andMe Is Bankrupt. What Happens to Your DNA Now?

Your genetic data may be transferred to a new owner as a business asset. Here is what the Terms of Service actually say and what you can do…

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.

All Cursor changes →