Enterprise
Cursor Enterprise HIPAA BAA: Eligibility, Scope & Configuration
Cursor offers a HIPAA Business Associate Agreement (BAA) on the Enterprise plan to covered entities and business associates. Don't submit protected health information (PHI) until the Enterprise agreement and BAA are signed and the required setup is done, including Privacy Mode enabled and locked organization-wide. The HIPAA Implementation and Configuration Guide, part of the BAA, lists eligible services and models.
On this page
Who can get a HIPAA BAA from Cursor?
Cursor offers BAAs on the Enterprise plan to organizations that are covered entities or business associates under HIPAA. In HIPAA's terms, covered entities include health plans, clearinghouses and healthcare providers, and business associates are the vendors that handle PHI on their behalf. Prospects evaluating Enterprise can request a BAA too, so you don't need a signed contract before you ask.
Ask during evaluation, while the commercial terms are still open. It costs one line in an email to sales. If you ask after signature, the BAA's legal review and countersignature wait behind the other work of both legal teams, and PHI can't enter Cursor until they're done.
Cursor's guidance is to hold back PHI until the Enterprise agreement and BAA are signed and your organization has completed the required implementation steps. The published Eligible Services are covered for Enterprise customers with Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. enabled and locked organization-wide. A signed agreement with Privacy Mode not yet locked doesn't put your usage in scope.
This is covered hands-on in Teams and Enterprise Admin — 6 short Units, free to read.
Rather do it than read about it? Run 11 interactive Cursor walkthroughs in a simulated editor. Free, no account needed.
What does the Cursor BAA cover?
The BAA covers the Eligible Services and Eligible Models defined in the HIPAA Implementation and Configuration Guide, which is part of the agreement. You get the guide on request through the Trust Center, and it holds the current details. A BAA doesn't automatically make every Cursor product, configuration or workflow appropriate for PHI.
The guide sets scope in four parts. Two say where PHI may go. The other two say what your organization has to set up and enforce, and most of the work sits there.
- Eligible Services
- The Cursor product surfaces where PHI is permitted.
- Eligible Models
- The subset of available AI models that the BAA covers.
- Required controls
- Settings your organization must turn on, including Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. enabled and locked organization-wide.
- Customer responsibilities
- What your team must configure, and what it must instruct users to do.
Cursor's BAA doesn't automatically cover third-party services. Before PHI moves, Cursor's FAQ tells you to review your approved configuration, your model provider settings, your integration usage and the guide. Anything you connect, such as MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. servers, external APIs or ticketing systems, is yours to assess and configure.
Which Cursor services are covered by the BAA?
The services below are covered for Enterprise customers with Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. enabled and locked organization-wide, according to the Eligible Services list on Cursor's BAA page. The HIPAA Guide carries the latest version, so read the list as a summary and the guide as the authority.
- Desktop IDE, including Agent, Tab, Edit and local agent mode
- Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition.
- Cursor for iOS
- CLI
- Tab
- BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition.
- Automations
The services list is public, but the Eligible Models aren't on Cursor's public page. The HIPAA Guide lists the current ones. When you write an internal policy, name the guide as the source for models instead of copying the list, so the policy doesn't go stale when the list changes.
What must we configure before using PHI?
Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. is the one required control the public BAA page names. Enable it and lock it organization-wide so members can't turn it off. The other required controls and the customer responsibilities are in the HIPAA Guide, and your organization is responsible for setting them up.
Model access control is the setting that depends on the guide, because the guide names the Eligible Models. Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. doesn't depend on the guide. Enable and lock Privacy Mode first, then restrict models once you have the guide.
- 1Request the BAA from Cursor sales and sign it alongside the Enterprise agreement.
- 2Request access to the HIPAA Implementation and Configuration Guide in the Trust Center, and read it.
- 3Enable and lock Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. organization-wide.
- 4Restrict work to the Eligible Services and Eligible Models the guide lists.
- 5Train users to submit PHI only through Eligible Services and approved workflows.
The first two steps wait on people outside your team: Cursor's countersignature, and access to the guide, which Cursor grants on request.
Check personal API keys before rollout. Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition.'s zero data retention commitments apply to Cursor-routed models. With a developer's own provider key, retention follows that developer's agreement with the provider, not Cursor's, so an organization-wide Privacy Mode lock can be in place while that traffic sits outside it. Restricting personal API keys (BYOK) is a separate setting. A few models also need data retention with their provider, and those require admin approval before use.
How do we request a HIPAA BAA?
Contact Cursor sales at cursor.com/contact-sales and say you need a HIPAA BAA. Cursor's docs also ask you to say where you stand: evaluating Cursor, moving from a Teams plan, or already on Enterprise. Request security and compliance documents through the Trust Center at trust.cursor.com, including the HIPAA Guide and Cursor's SOC 2 Type II report.
If you're on a Teams plan today, you need to move to Enterprise to get a BAA. Cursor's FAQ tells Teams customers to raise the plan change and the BAA with sales together, so plan both on the same timeline.
Decide who owns the guide at the same time. If the person who signs the BAA doesn't administer Cursor, the guide can stop at legal, and the configuration step stalls there.
Send the guide to whoever administers model access control on the day it arrives.
How do we show the required controls were in place?
Audit logs are the record. They're an Enterprise feature, they capture each Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. change with its scope (a user or the team), and you can export them for whoever assembles the evidence.
Audit logs leave out prompts and generated code, so the dashboard can't tell you whether PHI reached a model outside the Eligible Models list. Cursor recommends hooks for logging development activity, and hooks are code your team writes and maintains.
Decide now whether you'll deploy that logging or record that you accepted the gap, so the question doesn't first come up during an incident.
What does a signed BAA not guarantee?
A BAA sets the legal framework for handling PHI with Cursor. It doesn't make every product configuration safe for PHI by default. Your organization stays responsible for configuring Cursor and instructing users in line with the BAA, HIPAA requirements and the HIPAA Guide.
Four obligations stay with your team after signing, and Cursor doesn't enforce them for you. We'd watch the third-party row most closely, because integrations often arrive after the rollout plan is written.
- Configuration
- Turn on the required controls from the HIPAA Guide before any PHI moves.
- Scope
- Route PHI only through the Eligible Services and Eligible Models the guide lists.
- Third parties
- Assess and cover each integration you connect to Cursor separately.
- User training
- Instruct users on PHI handling. The BAA doesn't replace internal policy.
Those rows are the customer half of a split Cursor documents in its security hardening guide: Cursor secures and operates the platform, and you decide how to configure and adopt it. Read the BAA as a scope statement, not a certificate. Write an owner's name against each row before the first ticket that touches PHI.
Frequently asked questions
Is the Cursor HIPAA BAA available on the Teams plan?
No. BAA support is available on Enterprise. If your organization is on a Teams plan, contact Cursor sales to discuss moving to Enterprise and requesting a BAA at the same time.
Do we have to be an Enterprise customer before we can ask for a BAA?
No. Enterprise customers and prospects evaluating Enterprise can both request one, so you can raise it during evaluation. Cursor says it typically applies to healthcare organizations and to vendors that act as covered entities or business associates.
Where do we get the HIPAA Implementation and Configuration Guide?
Request access in the Trust Center at trust.cursor.com. The guide is part of the BAA and holds the current Eligible Services, Eligible Models, required controls and customer responsibilities.
Can we use any Cursor model with a BAA in place?
No. Only the Eligible Models listed in the HIPAA Guide are covered by the BAA, and PHI sent to other models falls outside it. Restrict personal API keys as well: Privacy Mode's zero data retention commitments apply to Cursor-routed models, and with a developer's own provider key, retention follows that developer's agreement with the provider.
Where do we find Cursor's SOC 2 report for security review?
Request Cursor's SOC 2 Type II report through the Trust Center at trust.cursor.com. You ask for access there instead of downloading it, so send the request when the review opens.
What happens if a team member sends PHI through a non-eligible model?
That usage falls outside the BAA. Your organization is responsible for restricting access to Eligible Models and training users. Restricting which models the organization can use is an admin setting, so configure it instead of relying on training alone.
Sources & last verified
- Cursor - HIPAA Business Associate Agreements
- Cursor - Privacy and Data Governance
- Cursor - Trust Center
- Cursor - Enterprise
- Cursor - Security and Privacy Hardening
- Cursor - Compliance and Monitoring
Cursor ships frequently. Last updated October 28, 2026.