https://cursor.com · record 192 · read 2026-09-05 · rules/v1 · generated 2026-09-06 04:01 UTC
Facts
Trains on customer data
no
“We do not use Inputs or Suggestions to train our models, or permit third parties to use them for training, unless: (1) they are flagged for security review (in which case we may analyze them to improve our ability to detect and enforce our Terms of Service), (2) you explicitly report them to us (for example, as Feedback), or (3) you’ve explicitly agreed to their use for such training purposes.”
“At Customer’s written direction, Vendor shall delete or return all Personal Data to Customer as requested at the end of the provision of the Service, within thirty (30) days of such request, unless retention of the Personal Data is required by law, and upon request shall provide written certification thereof.”
“Anysphere processes your personal data for the purposes described in this Privacy Policy on servers located in various jurisdictions, including in the United States.”
“If Vendor appoints a new subprocessor or intends to make any changes concerning the addition or replacement of any subprocessor, it shall provide Customer with thirty (30) business days’ prior written notice by posting updates at trust.cursor.com/subprocessors, during which time Customer can object to the appointment or replacement on reasonable and documented grounds related to the confidentiality or security of Personal Data or the subprocessor’s compliance with Privacy Laws (and if Customer does not so object, Vendor may proceed with the appointment or replacement).”
Ledger proof for this record. seq 399 · key 2f898a895f05b7a0 · 2026-09-06T01:39:47.411Z hash c75d3fdb32ba0649b0609777b7a7e9be35b398a33beedfea7dbb96b8737cd0b8 prev 81da1f2cf6d8f0a05055724785fb8eb7975a111db4ee83e71c5d248e4dd80161 payload a9173376868b6d17b832cfb8ba22608a79bacae5b9ac369a6a1a8f04e1c856ff signature P5bYoDp05wDm4P4mj/UuEq71/O6QDebHq84QA7W0AM4eQRQqFExH+x3Y79La8MzQMDxd5PtHx27z9P3xHPuhAg== anchored 2026-09-06 at head seq 564 231a9dea0f93915bd7110e6786e00908325db3031635ace53c1023f850e0c49c Fetch /v1/keys; for each ledger entry recompute sha256(prev_hash|kind|ref_id|payload_hash|created_at ISO) and verify the Ed25519 signature over that hash. Anchors are committed to git; compare the anchored head with the chain.