17 Total

Key Facts · in the document’s own words

How does Cursor communicate critical incidents to affected users?
“Critical incidents are communicated via email to affected users.”
Version CA-V-006766, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Cursor communicates critical incidents to affected users via email.
Does Cursor use any infrastructure in China?
“Cursor does not use or maintain any infrastructure in China. We do not use any companies headquartered in China as subprocessors, and to our knowledge none of our subprocessors do either.”
Version CA-V-006766, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Cursor does not use or maintain any infrastructure in China and does not use any companies headquartered in China as subprocessors.
What will Cursor not do when Privacy Mode is enabled?
“When enabled, we will not train on your data.”
Version CA-V-006766, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
When Privacy Mode is enabled, Cursor will not train on the user's data.
What does Cursor implement with its model providers to protect user data?
“We also implement technical controls and contractual requirements with our model providers to protect your data.”
Version CA-V-006766, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Cursor implements technical controls and contractual requirements with its model providers to protect user data.
How does Cursor evaluate and review subprocessors?
“Each subprocessor is evaluated under our vendor risk management program and re-reviewed annually.”
Version CA-V-006766, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Cursor evaluates each subprocessor under its vendor risk management program and re-reviews each subprocessor annually.
Does Cursor commit to penetration testing by reputable third parties at least annually?
“We commit to at-least-annual penetration testing by reputable third parties. An executive summary of the latest report is also available on request via our trust portal.”
Version CA-V-006766, captured Sept. 11, 2026 · live source ↗
Our reading, not the document’s words
Cursor commits to penetration testing by reputable third parties at least annually.
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.
Summary
Generated by a model from the captured document; not read by a person

This document describes how Cursor secures its systems and handles your data. The most user-facing features are Privacy Mode — which, when enabled, prevents Cursor from training on your data — and the ability to delete your account at any time from Settings. Cursor also commits to notifying you by email if a critical incident affects you.

Analysis

This document establishes Cursor's security and data-handling practices, including conditional restrictions on training data use (Privacy Mode disables training on user data), subprocessor controls (no China-based infrastructure or subprocessors, annual vendor risk re-review, contractual and technical requirements imposed on model providers), and operational security commitments (least-privilege access, multi-factor authentication, cybersecurity tooling, continuous log monitoring, and at least annual third-party penetration testing). Cursor commits to acknowledging vulnerability reports within 5 business days and notifying affected users of critical incidents via email. Users retain a self-service right to delete their account at any time from the Settings dashboard, and Privacy Mode is available across all plan tiers including free.

What this means for you

For an individual user, the most direct impact is that enabling Privacy Mode prevents Cursor from using your data for model training. This option is available to every user, including those on the free tier, and can be enabled without upgrading. You can also delete your account at any time directly from the Settings dashboard without needing to contact support. If a critical incident affects you, Cursor will notify you via email.

Institutional Analysis
Stay ahead of the changes

Institutional analysis available with Insight

Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.

2 important changes detected

6 versions captured · Latest change detected by ConductAtlas: August 2026

What changed Cursor removed the word 'indexing' from its description of backend functionality. The previous text stated the app makes requests to deliver 'API, indexing, update, and marketplace functionality.' The updated text removes 'indexing' from this list. This change clarifies which backend services the app actively requests, though the operational significance depends on whether indexing functionality was actually discontinued or simply removed from the disclosure.
Why this matters The updated security practices remove 'indexing' from the list of backend functionalities the app requests. This change clarifies the disclosed scope of backend operations, though the practical impact depends on whether indexing services were actually discontinued or simply removed from the disclosure statement.
View full change record →
What changed 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.
Why this matters 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.
View full change record →

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

Complete Provision Index

Every distinct legal provision identified in this document. Featured provisions appear above with analysis.

17 provisions
12 featured
7 clause types
Stay ahead of the changes

Monitoring

Cursor has updated this document before. Monitor includes alerts from a daily check, structured change summaries, and monitoring for up to 20 platforms.

Stay ahead of the changes

Governance Intelligence

Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.

Cross-platform context

See how other platforms handle Critical incident notification to affected users via email and similar clauses.

Compare across platforms →
Archival ProvenanceSource & Archival Record
This version captured September 11, 2026 00:56 UTC
Last successful capture October 15, 2026 00:46 UTC
Date stated by the document August 25, 2026 (as printed in this version)
Capture Method Automated scheduled archival capture
Document ID CA-D-000832
Version ID CA-V-006766
SHA-256 (extracted text, extractor v5) a764b6b3b8a250be7d787534e056805ee123bc0c7fc4f2cf3071eb354ab3a9aa
Archived bytes SHA-256 (anchor) 3390ea3e7e5a41d3238c2109f3116525496a116160e5d2361d6957358c6d03ea
✓ Snapshot stored ✓ Archived bytes anchored (verified Sept. 11, 2026)

Governance Monitoring

Monitor governance changes across the platforms you rely on.

Structured alerts for policy changes, governance events, and provision updates across 343 platforms.

Start monitoring → Compare plans