Cursor collects data about how you use the service — including logs and interaction data — and can share anonymized versions of this data with third parties. Your actual code and AI outputs are excluded from this.
Cursor collects and internally analyzes technical logs and behavioral data about your use of the platform, and shares anonymized versions of this data with third parties — the scope of 'Usage Data' and the effectiveness of de-identification are not independently verified in this document.
Cross-platform context
See how other platforms handle Usage Data Collection and Disclosure and similar clauses.
Compare across platforms →While Content is excluded, Usage Data includes behavioral and interaction logs that could reveal sensitive information about your development patterns, workflows, and tooling — and this data is shared with third parties in aggregated form.
1. REGULATORY FRAMEWORK: This provision engages GDPR Article 6(1)(f) (legitimate interests) as the likely lawful basis for Usage Data processing, and Article 89 for anonymized/aggregated data processing. CCPA §1798.140(o) defines 'personal information' broadly and may encompass Usage Data depending on its identifiability. The FTC Act Section 5 applies to representations about de-identification — the FTC has stated that de-identified data that can be re-identified remains personal data subject to privacy representations. The EU AI Act (Recital 47) addresses data used to improve AI systems. 2.
Compliance intelligence locked
Regulatory citations, enforcement risk, and due diligence action items.
Watcher: regulatory citations. Professional: full compliance memo.