So, I naively used Cursor “out of the box” with privacy mode disabled and agent set to “auto”. I am on the Pro plan. I used Cursor to update Typescript types throughout my codebase and am now trying to understand how much of my codebase is “out there” and what can be done about it?
Specifically, I am trying to understand:
- What services processed the codebase?
- What and where our codebase or information about is stored?
- What we can do about removing any stored info or code related to our codebase?
The following is what I got from Cursor’s ai email response robot. Is there somebody at Cursor I can speak with to better understand the response? Is my codebase just out there and visible for others to see at this point? It does sound like it is not just floating out there in plain text, and perhaps limited info was even sent to 3rd party providers . I am hoping to get confirmation of this and direction on next steps either from somebody at Cursor, or from somebody who has dealt with this.
Can somebody at Cursor determine how much of my codebase was even sent to them in the first place? This would be very helpful to know!
Obviously, I have learned my lesson and now know Privacy Mode exists!
Here is the response I got from the auto-email, but it still doesn’t really help address the actual impact in simple terms. **
Services that processed the code:**
-
Cursor’s servers (AWS in the US)
-
Third-party AI providers (OpenAI, Anthropic, Google, and/or xAI via “auto” model)
-
Turbopuffer (Google Cloud in the US) for embeddings storage
What’s stored and where:
-
Mathematical embeddings (vector representations) stored in Turbopuffer
-
Obfuscated file paths and line numbers
-
Plaintext code “ceases to exist after the life of the request” - only embeddings remain
-
Prompts and limited telemetry may have been shared with model providers
Data removal options:
-
Automatic: Indexed codebases delete after 6 weeks of inactivity
-
Immediate: Delete the Cursor account (complete removal within 30 days)
Third-party providers: You don’t need to contact them separately - they handle API requests per their standard data retention policies.
