232 APPS TRACKED · 227 CLAUSES ON FILE · 38 WITH NO CLAUSE TO QUOTE
← Cursor · AI Addendum

This is an extract from an archived copy, fetched 23 September 2026. Cursor didn't author this page for us. It's a snapshot we captured from https://cursor.com/data-use. We hold the whole page and publish this part of it: the sentence a verdict rests on, with the text either side, so you can see it hasn't been lifted out of an exception.

SHA-256
AD25A417…7714

The passage, in context

Paragraph 4 of 7

If you have any questions or feedback, please email us at hi@cursor.com . And for more information about how we collect, use, disclose, and process your personal data, see our full Privacy Policy .

Here's how your data is handled based on the privacy settings you choose in Cursor:

If you enable " Privacy Mode " in Cursor's settings: Customer Data will not be used for training by Cursor. Cursor maintains zero data retention (ZDR) agreements with all providers, and AI model providers will not store or train on your data. However, please note that subject to their policies, model providers (including Cursor) may run risk classifiers to detect violations of terms and usage policies, and if your prompts or conversations trigger abuse detectors your data may be stored for investigation and deleted in accordance with their retention policies. Non-ZDR models will be designated as such or require an admin to opt-in to enable the model for your workspace. See documentation from SpaceXAI , OpenAI , Anthropic and Meta for more details about their retention policies.

If you choose to turn off "Privacy Mode": we may use and store codebase data, prompts, editor actions, code snippets, and other code data and actions to improve our AI features and train our models. Some of our inference providers may temporarily access and store model inputs and outputs to improve our inference performance; this data is deleted after use.

Other notes:

Even if you use your API key, your requests will still go through our backend! That's where we do our final prompt building.

We temporarily cache file contents on our servers to reduce latency and network usage. The files are encrypted using unique client-generated keys, and these encryption keys only exist on our servers for the duration of a request. All cached file contents are temporary, never permanently stored, and never used as training data when privacy mode is enabled.

Checking the rest of it

The complete page is kept here and isn't republished. It's Cursor's copyrighted document, and an extract is what a reader needs to check a quotation. The SHA-256 above is of that whole snapshot: fetch the page yourself, hash it, and you can tell whether ours has been altered without having to trust us.

If you work for Cursor, or you are researching this and need the full capture, ask us for it and we will send it. If you believe a quote here is wrong or out of date, send us the paragraph. The correction gets published beside the clause.