Privacy & Security
Guide to Cursor’s privacy settings, data handling, and code indexing with Privacy Mode option
Cursor is built with privacy and security at its core. We have built Cursor from the ground up to give you the peace of mind that your code and data is private and secure.
Quick Links
To learn more about Cursor’s privacy and security practices, please see the following links:
Privacy Policy
Read our comprehensive privacy policy to understand how we handle your data
Security Overview
Learn about our security practices and how we protect your code
Trust Center
View our Trust Center for security practices, SOC2 certification, and penetration testing reports.
Privacy FAQs
What is Privacy Mode?
Cursor offers three privacy options to give you full control over how your code is handled:
You can read more about Privacy Mode here.
Are requests always routed through the Cursor backend?
Yes! Even if you use your API key, your requests will still go through our backend. That’s where we do our final prompt building.
Does indexing the codebase require storing code?
It does not! 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 ceases to exist after the life of the request.
The embeddings and metadata about your codebase (hashes, obfuscated file names) are stored in our database, but none of your code is.
You can read more about this on our security page.