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 retain personal data for as long as necessary to provide our services, fulfill the purposes described in this Privacy Policy, comply with our legal obligations, resolve disputes, and enforce our agreements. The specific retention period for each category of personal data depends on the purpose fo...
We retain your personal information for as long as necessary to fulfill the purposes outlined in this privacy policy, unless a longer retention period is required or permitted by law. We may also retain and use your information to comply with our legal obligations, resolve disputes, and enforce our ...
Please note there are situations where Spotify is unable to delete your data, for example when: it's still necessary to process the data for the purpose we collected it for; we have an overriding interest in continuing to process the data, for example where we need the data to protect our services f...
Monitoring
Cursor has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 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
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance 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.