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

API key requests routed through Cursor backend

High confidence Unique · 0 of 343 platforms

Key Facts · in the document’s own words

Where does Cursor route all requests?
“Even if you use your API key, your requests will still go through our backend! That's where we do our final prompt building.”
Version CA-V-006530, captured Sept. 9, 2026 · live source ↗
Our reading, not the document’s words
Cursor routes all requests through its backend, including those made with a user's own API key.
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

Users who supply their own API key may assume their requests go directly to the model provider, but this clause establishes that Cursor's backend remains an intermediary for all requests.

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

Regardless of whether a reader uses their own API key, their requests are routed through Cursor's backend infrastructure.

How other platforms handle this

Target

Before fulfilling access, correction, or deletion requests, Target requires that you submit information used to determine if we have information about you and verify your identity.

Wyze

If you are submitting a rights request as an authorized agent, you are required to submit proof of your authorization to make the request, such as a valid power of attorney or proof that you have signed permission...

Scale AI

We may request specific information from you to help us confirm your identity and process your request.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
Even if you use your API key, your requests will still go through our backend! That's where we do our final prompt building.

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-059546
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-059546
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-059546/api-key-requests-routed-through-cursor-backend/
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 API key requests routed through Cursor backend clause do?

Users who supply their own API key may assume their requests go directly to the model provider, but this clause establishes that Cursor's backend remains an intermediary for all requests.

How does this clause affect you?

Regardless of whether a reader uses their own API key, their requests are routed through Cursor's backend infrastructure.

Is ConductAtlas affiliated with Cursor?

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