# Is Cursor HIPAA compliant? Yes — on Enterprise, with Privacy Mode locked - Tool: Compliance - Last updated: August 2026 ## TL;DR Yes, conditionally — and most write-ups get this wrong. Cursor does sign a HIPAA Business Associate Agreement, but only for Enterprise customers, only with Privacy Mode enabled and locked organization-wide, and only across a list of Eligible Services and Eligible Models that lives in a guide behind the Trust Center. Third-party model providers, MCP servers and your own API keys sit outside it. Getting an existing team into that configuration and cleaning up what was pasted before takes us 6–10 weeks. ## Frequently asked questions ### We're on Teams. Can we get a BAA there? No. Cursor answers this one in its own FAQ: "BAA support is available on Enterprise. If your organization is currently on a Teams plan, contact sales to discuss moving to Enterprise and requesting a BAA." Teams does give you Privacy Mode on by default, which is a real control, but it is not the agreement. Budget for the plan move before you budget for anything else. ### Privacy Mode is on. Isn't that the same thing? No, and the relationship runs the other way from how people usually describe it. Privacy Mode is not a substitute for the BAA — Cursor makes it a precondition of it, and specifically "Enable and lock Privacy Mode organization-wide". Enabled but not locked is not the configuration the Eligible Services list is prefaced with. It is also not absolute: Cursor states that model providers may run risk classifiers and that if your prompts trigger abuse detectors your data may be stored for investigation. ### Which models can we actually use with PHI? We cannot tell you, and no public Cursor page can either. Cursor gates PHI on a model basis as well as a surface basis, and says the HIPAA Guide lists the current Eligible Models. That guide is behind a Trust Center access request. No model is publicly named as HIPAA-eligible anywhere on cursor.com. Practically, this means the trap is not the surface — the Desktop IDE is an Eligible Service — but the model picker inside it. Get the guide, then build an allowlist that matches it, then treat a new model in the picker as a change that needs approval. ### One of our engineers uses their own Anthropic key in Cursor. Does the BAA cover that? No. Cursor says "ZDR doesn't apply when you use your own API keys. In that case, your data handling follows your provider's privacy policy." Bring-your-own-key sits outside the covered set, and Cursor also states it has no data-residency support. Whatever went through that key was governed by that account's terms with that provider, which is unlikely to include a BAA. The same applies to a custom model reached through a base URL override or a third-party gateway. ### Can we run Cloud Agents on a repo that has real records in its test fixtures? Cloud Agents are on the Eligible Services list, so with the BAA in place and Privacy Mode locked, the surface itself is in scope. But it is the one feature where Cursor stores your code — encrypted copies of the repositories the agent works on, kept while the agent runs and deleted after it completes — and Cursor's own line is that if your security policy prohibits code storage, don't enable Cloud Agents. So the honest answer is that the fixtures are the problem, not the agent. Fix the fixtures first. ### What about @Web, MCP servers and Grok Bot? All three are outside the editor's perimeter. Cursor describes @Web and user-configured MCPs or connectors as separate services, each with its own region, and says third-party services and integrations are not automatically covered by its BAA. Grok Bot is described as running on a separate product surface with its own data flows and is not among the Eligible Services, so Privacy Mode in the editor does not govern it. In a coding-agent workflow this is where a leak most plausibly happens, because the agent can call these without anyone deciding in the moment that a call was about to occur. ### Is Cursor HIPAA certified? Nothing is. There is no government HIPAA certification for a product or a company. What exists is a signed Business Associate Agreement with each vendor that touches protected health information, plus the safeguards you implement and document yourself. Cursor names SOC 2 Type II on its security page, as a report available on request — a useful thing to ask for, and not a substitute for the agreement. --- Source: https://www.rapidevelopers.com/compliance/is-cursor-hipaa-compliant © RapidDev — https://www.rapidevelopers.com/compliance/is-cursor-hipaa-compliant