You are not allowed to submit health records, payment card data, or other specially regulated categories of sensitive information to Cursor. This restriction applies even if the data concerns yourself.
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
This provision places contractual responsibility on users to ensure they do not input regulated data types such as medical records or financial account information into Cursor, which is significant for enterprise users and developers working with sensitive data.
Under this provision, users who submit HIPAA-regulated health information, PCI-DSS payment card data, or GLBA-regulated financial data to the Service are in breach of these Terms; enterprise teams integrating Cursor into development workflows involving such data categories should establish technical controls to prevent prohibited submissions.
How other platforms handle this
You must not pre-fetch, cache, index, or store any Content, except that you may store: (i) limited amounts of Content for the purpose of improving the performance of your Maps API Implementation, but only for a temporary period as specified in the Maps APIs Documentation; and (ii) any content that G...
You must not sell, license, or purchase User Data obtained from us. You must not transfer User Data obtained from us without our prior written permission except when: transferring to your service provider acting on your behalf and in compliance with this Policy; transferring as part of a merger, acq...
Please note that we do not knowingly sell the personal information of minors under 16 years of age without legally-required affirmative authorization. Please note that we do not knowingly sell the personal information of minors under 16 years of age.
Monitoring
Cursor has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"you may not:... (x) send or otherwise provide to Anysphere data or information that is subject to specific protections under applicable laws beyond any requirements that apply to "personal information" or "personal data" generally, such as for illustrative purposes, information that is regulated by the Health Insurance Portability and Accountability Act, the Payment Card Industry Data Security Standard, the Gramm-Leach-Bliley Act, and other U.S. federal, state or foreign laws applying specific security standards— Excerpt from Cursor's Cursor Terms of Service
REGULATORY LANDSCAPE: This provision directly references HIPAA, PCI-DSS, and GLBA as illustrative examples of regulated data categories prohibited from submission. It does not constitute a compliance safe harbor for Anysphere under these frameworks; rather, it contractually allocates risk to the user. HHS Office for Civil Rights enforces HIPAA; the FTC enforces the Safeguards Rule under GLBA; PCI-DSS is enforced through card network contractual obligations. This provision does not address whether Anysphere would notify affected parties in the event regulated data is inadvertently submitted. GOVERNANCE EXPOSURE: High for enterprise users in regulated industries. Healthcare organizations, financial institutions, and companies subject to sector-specific data security requirements must implement technical and procedural controls to prevent employees from submitting regulated data to Cursor. The contractual prohibition shifts liability to the user organization but does not mitigate the underlying regulatory exposure if a breach occurs. JURISDICTION FLAGS: US federal frameworks (HIPAA, GLBA, PCI-DSS) are explicitly named, and the clause references 'other U.S. federal, state or foreign laws,' which may encompass EU GDPR special categories of data, state health privacy laws (such as Washington's My Health MY Data Act), and Illinois BIPA for biometric data. EU/EEA enterprises should evaluate whether this restriction aligns with their obligations under GDPR Articles 9 and 10 regarding special category and criminal conviction data. CONTRACT AND VENDOR IMPLICATIONS: Enterprise procurement and legal teams must assess whether Cursor can be deployed in workflows that involve regulated data. If regulated data may be present in code repositories or development environments, technical guardrails (such as data masking or restricted access) should be implemented before deployment. This provision also means Anysphere has not agreed to serve as a HIPAA Business Associate, which precludes lawful use of Cursor for workflows involving protected health information absent separate agreement. COMPLIANCE CONSIDERATIONS: Legal and compliance teams in regulated industries should conduct a use-case audit to identify whether any Cursor deployment scenarios involve regulated data categories. Employee training should address the prohibition on submitting regulated data. IT teams should evaluate whether data loss prevention tools can be configured to detect and block prohibited data submissions through Cursor.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision places contractual responsibility on users to ensure they do not input regulated data types such as medical records or financial account information into Cursor, which is significant for enterprise users and developers working with sensitive data.
Under this provision, users who submit HIPAA-regulated health information, PCI-DSS payment card data, or GLBA-regulated financial data to the Service are in breach of these Terms; enterprise teams integrating Cursor into development workflows involving such data categories should establish technical controls to prevent prohibited submissions.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cursor.