This analysis describes what Cursor's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that codebase indexing involves server-side processing and persistent storage of derived data (embeddings and metadata) rather than plaintext source code, creating a distinction between ephemeral request data and retained indexed artifacts.
Interpretive note: The document does not specify a retention period for stored embeddings and file metadata, creating ambiguity about how long this derived data is held.
Users who activate codebase indexing authorize Cursor to upload code segments for embedding computation and to store the resulting embeddings and codebase metadata in its database, while plaintext code is not retained beyond the individual request.
How other platforms handle this
We store information until it is no longer necessary to provide our services and WhatsApp Products, or until your account is deleted or becomes inactive, whichever comes first. This is a case-by-case determination that depends on things like the nature of the information, why it is collected and pro...
You may request deletion of your account at any time. When you request account deletion, we will delete or anonymize your personal information unless we are required to retain it by law, or unless we need to retain it for legitimate business purposes such as resolving disputes, enforcing our agreeme...
Slack (Sees no code data): We use Slack for internal communications. We may discuss logs of data for debugging purposes from users that are not using Zero-data retention mode. Google Workspace (Sees no code data): We use Google Workspace for collaboration. We may discuss logs of data for debugging p...
Monitoring
Cursor has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"If you choose to index your codebase, Cursor will upload your codebase in small chunks to our server to compute embeddings, but all plaintext code for computing embeddings ceases to exist after the life of the request. The embeddings and metadata about your codebase (hashes, file names) may be stored in our database.— Excerpt from Cursor's Cursor Data Use & Privacy Overview
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision establishes that codebase indexing involves server-side processing and persistent storage of derived data (embeddings and metadata) rather than plaintext source code, creating a distinction between ephemeral request data and retained indexed artifacts.
Users who activate codebase indexing authorize Cursor to upload code segments for embedding computation and to store the resulting embeddings and codebase metadata in its database, while plaintext code is not retained beyond the individual request.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cursor.