Provision record
Cursor · Cursor Data Use & Privacy Overview · View original document ↗

Risk classifier exception to ZDR retention

High confidence Common · 268 of 343 platforms

Key Facts · in the document’s own words

What may model providers run to detect policy violations?
“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...”
Version CA-V-006530, captured Sept. 9, 2026 · live source ↗
Our reading, not the document’s words
Model providers, including Cursor, may run risk classifiers to detect policy violations, and if a user's prompts or conversations trigger abuse detectors, that data may be stored for investigation.
Stay ahead of the changes
Track Cursor and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

Generated by a model from the captured document; not read by a person

This establishes an explicit exception to ZDR commitments: abuse-triggered data may be retained by model providers or Cursor outside the standard zero-retention framework.

Recent Activity

This document changed recently

Medium Jun 10, 2026

The updated terms clarify that Cursor maintains zero data retention agreements with all AI model providers and will not use customer data for training. However, the revised language now explicitly states that model providers may run risk classifiers to detect policy violations, and if your prompts or conversations trigger abuse detectors, your data may be stored temporarily for investigation and deleted according to the providers' retention policies. The policy removed the legacy Privacy Mode option; non-ZDR models now require explicit admin opt-in. You can review the specific retention policies of OpenAI and Anthropic through their documentation.

View change record →

Consumer impact (what this means for users)

Generated by a model from the captured document; not read by a person

If the reader's prompts or conversations trigger an abuse detector, that data may be stored for investigation by model providers or Cursor, notwithstanding any ZDR agreements.

How other platforms handle this

Kling AI

We may retain some of your Data even after you cease to use our Services, for instance if the Data is necessary to meet our legal obligations, such as tax and accounting requirements.

Teladoc

Where specific retention periods are required by law, we comply with those timeframes; otherwise, we apply the criteria above to determine how long to retain the information.

Postman

If the Services are made available to you through an organization (e.g., your employer), we retain your information as long as required by the administrator of your account.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
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...

Excerpt from Cursor's Data Use & Privacy Overview

Provision details

Document information
Document
Cursor Data Use & Privacy Overview
Entity
Cursor
Date stated by the document
Sept. 3, 2026
As printed in Cursor’s text (version CA-V-006530), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
May 11, 2026
Text quoted from version
CA-V-006530, captured Sept. 9, 2026
Record ID
CA-P-059533
Document ID
CA-D-000764
Evidence Provenance
Source URL
Wayback Machine
Extracted-text SHA-256 (version CA-V-006530)
9ffffd4b091b7a9f27a1169f3fb2c623eba5c87d0259311e145667ca7b1c37cc
Analysis generated
July 9, 2026 14:51 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-006530, captured Sept. 9, 2026 (checked Oct. 5, 2026)
Citation Record
Entity: Cursor
Document: Cursor Data Use & Privacy Overview
Record ID: CA-P-059533
Version: CA-V-006530
Captured: 2026-09-09 00:55:08 UTC
SHA-256: 9ffffd4b091b7a9f…
URL: https://conductatlas.com/platform/cursor/cursor-data-use-privacy-overview/provision/CA-P-059533/risk-classifier-exception-to-zdr-retention/
Accessed: Oct. 18, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Cursor's Risk classifier exception to ZDR retention clause do?

This establishes an explicit exception to ZDR commitments: abuse-triggered data may be retained by model providers or Cursor outside the standard zero-retention framework.

How does this clause affect you?

If the reader's prompts or conversations trigger an abuse detector, that data may be stored for investigation by model providers or Cursor, notwithstanding any ZDR agreements.

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 268 platforms. See the full comparison.

Is ConductAtlas affiliated with Cursor?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cursor.