This article is about our commercial products such as Claude for Work and the Anthropic API. For our consumer products such as Claude Free, Pro, Max and when accounts from those plans use Claude Code, see here.
For Claude Enterprise features to be covered under a Business Associate Agreement (BAA), the Primary Owner of the organization must activate HIPAA compliance in the HIPAA-ready Claude Enterprise organization settings under “Data and privacy” and accept Anthropic's BAA. Standard Claude Enterprise plans do not include BAA coverage without action from a Primary Owner. For Claude Code (local mode) and Claude Cowork (local mode) to be covered, the Primary Owner must also apply the HIPAA configuration to both products. See Use Claude Code (local mode) and Claude Cowork (local mode) on a HIPAA-ready Enterprise plan.
Anthropic provides a BAA covering our HIPAA-ready services, such as use of our first-party API, Claude in Microsoft Foundry, or Enterprise plans. Claude Enterprise Primary Owners can accept the BAA directly when activating HIPAA compliance in the organization settings under “Data and privacy.”
Important: To use the 1P API with PHI, your organization’s Primary Owner will need to sign a BAA and then reach out to your Anthropic contact or our Sales team to get this turned on.
For clarity, the BAA only covers the single organization that accepted it, and excludes features such as Claude Console, Cowork in the cloud, or features currently in beta such as Claude in Office, Claude Design, Claude Slides, and Claude Docs. As part of the BAA, customers of Anthropic’s HIPAA-ready services are subject to certain configuration requirements and limitations on what features/integrations are available.
Not all API features are covered. See the Implementation Guide for the full list of eligible and non-eligible features.
Important: Covered Models require 30-day data retention and aren't available with zero data retention (ZDR) enabled unless Anthropic has expressly authorized it for your organization. With the HIPAA configuration applied to Claude Code (local mode) and Claude Cowork (local mode) on a HIPAA-ready Enterprise plan, members can use Covered Models in both products under the BAA. Claude Code can't use Covered Models while your organization has ZDR for Claude Code, unless Anthropic has expressly authorized it for your organization.
Below is a breakdown of what’s covered under the BAA, by feature and product surface. This article covers:
Claude Enterprise features
Claude Code and Claude Cowork features
API features
Messages API features
Product BAA coverage by surface
See Manage local session data for what Claude Code stores on a member's computer and how to delete it. For Cowork, see Manage Cowork data on each computer.
What’s covered under Anthropic’s BAA
Claude Enterprise features
Claude Enterprise Feature | Availability |
Chat | ✅ Covered as Eligible Services under Anthropic BAA* |
Projects (in chat) | ✅ Covered as Eligible Services under Anthropic BAA* ⚠️ Applies to projects in chat only. Does not include projects in other products, which are not covered, even if accessible in your organization. |
Artifacts (in chat) | ✅ Covered as Eligible Services under Anthropic BAA* ⚠️ Applies to artifacts in chat only. Does not include published artifact pages or artifacts in Cowork (local mode) or Code (local mode), which are not covered, even if accessible in your organization. |
File creation & code execution | ✅ Covered as Eligible Services under Anthropic BAA* ⚠️ Excluding network access and use of external websites |
Voice | ✅ Covered as Eligible Services under Anthropic BAA* |
Web Search | ✅ Covered as Eligible Services under Anthropic BAA* |
Research | ✅ Covered as Eligible Services under Anthropic BAA* |
Skills | ⚠️ Available to use but not covered under Anthropic's BAA. Administrators who enable this feature are responsible for ensuring their workforce uses it in compliance with applicable legal obligations. Off by default in organizations that have enabled HIPAA. An Owner can turn on Skills in Organization settings > Plugins & skills, in the "Policy" tab. The "Skills and plugins" table in this article lists each kind of skill. |
MCPs / Connectors | ⚠️ Available to use but sending data to 3rd parties via this feature isn’t covered under Anthropic’s BAA. Administrators who enable these features are responsible for ensuring their workforce uses them in compliance with applicable legal obligations. |
Enterprise Search / “Ask Your Org” | ⚠️ Available to use but sending data to 3rd parties via this feature isn’t covered under Anthropic’s BAA. Administrators who enable this feature are responsible for ensuring their workforce uses it in compliance with applicable legal obligations. |
Claude in Chrome | ⚠️ Available to use but sending data to 3rd parties via this feature isn’t covered under Anthropic’s BAA. Administrators who enable this feature are responsible for ensuring their workforce uses it in compliance with applicable legal obligations. Off by default in organizations that have enabled HIPAA. An Owner can turn on Claude in Chrome in Organization settings > Claude in Chrome. |
Cowork in Claude Desktop | ✅ Covered as Eligible Services under Anthropic BAA*, with the HIPAA configuration applied to Claude Code (local mode) and Cowork (local mode)
⚠️ Without that configuration, available to use but not covered under Anthropic's BAA |
Cowork in the cloud | ⚠️ Available to use but not covered under Anthropic's BAA
❌ Not available with the HIPAA configuration applied to Claude Code (local mode) and Cowork (local mode) |
Dispatch | ⚠️ Available to use but not covered under Anthropic's BAA
❌ Not available with the HIPAA configuration applied to Claude Code (local mode) and Cowork (local mode) |
Claude for Microsoft 365 | ⚠️ Available to use but some features are in beta and not covered under Anthropic’s BAA. Administrators who enable this feature are responsible for ensuring their workforce uses it in compliance with applicable legal obligations. |
Claude Design [beta] | ❌ Not available yet for HIPAA-ready organizations |
Claude Slides [beta] | ❌ Not available yet for HIPAA-ready organizations |
Claude Docs [beta] | ❌ Not available yet for HIPAA-ready organizations |
*Covered under versions of the BAA accepted after 12/2/25
Claude Code and Claude Cowork features
Use these tables to check whether you can use a Claude Code or Cowork feature to process protected health information (PHI).
The tables apply to a Claude Enterprise organization that has the HIPAA configuration applied. The HIPAA configuration is an organization setting that brings Claude Code (local mode) and Cowork (local mode) under your Business Associate Agreement (BAA) with Anthropic. "Local mode" means a session that runs on a member's own computer, in one of these places:
Claude Code in the terminal
Claude Code in the Code tab of Claude Desktop
Cowork in Claude Desktop
Note:
If your organization hasn't applied the configuration, see Coverage without the HIPAA configuration.
If you want to apply the configuration, see Use Claude Code (local mode) and Cowork (local mode) on a HIPAA-ready Enterprise plan.
If you need the contractual list of Eligible Services, see the Implementation Guide for HIPAA Entities on the Anthropic Trust Center.
Each table has two columns for every feature. "Availability" says whether members can use the feature. "Coverage under your BAA" says whether your BAA covers it. Check both, because a feature can be available and still not be covered.
Important: Process PHI only with a feature marked ✅ Covered.
Availability and coverage values
Some cells in the "Availability" column add a condition, or name the settings page where an Owner of your organization turns the feature on. Every cell starts with one of these values:
Available: Members can use the feature without any action from an Owner. A feature inside Cowork or the Code tab becomes available after an Owner turns on Cowork or the Code tab.
Off until an Owner turns it on: The feature is off by default. An Owner can turn it on in Organization settings.
Not available: The feature is off, and no setting turns it on.
Every cell in the "Coverage under your BAA" column starts with one of these values:
✅ Covered: Your BAA covers the feature, so members can use it to process PHI. Covered means only that your BAA applies. Whether to allow a feature, such as bypass permissions mode, is your organization's decision.
⚠️ Not covered: Members can use the feature, right away or after an Owner turns it on, but your BAA doesn't cover it. Keep PHI out of it.
❌ Not available: The feature isn't available while the HIPAA configuration is applied, so the question of coverage doesn't come up.
Some features that aren't covered are available without any action from an Owner, such as the VS Code and JetBrains extensions and local MCP servers. If you're an Owner, tell members to keep PHI out of every feature marked both Available and Not covered in the tables below.
Where members run Claude Code and Cowork
The table lists the three places that count as local mode, and the other ways members can run Claude Code.
Feature | Availability | Coverage under your BAA |
Claude Code in the terminal | Available to members whose seat includes Claude Code | ✅ Covered, when members sign in with their Claude Enterprise account and Claude Code connects directly to Anthropic, not through a cloud provider or gateway |
Claude Code in the Code tab of Claude Desktop | Off until an Owner turns on Desktop in Organization settings > Claude Code | ✅ Covered |
Cowork in Claude Desktop | Off until an Owner turns it on in Organization settings > Cowork | ✅ Covered |
Claude Code extensions for VS Code and JetBrains | Available. These sessions get the HIPAA configuration | ⚠️ Not covered. The extensions run on a member's computer, but Claude Code (local mode) includes only the terminal and the Code tab |
Claude Code through Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry | Available. These sessions run without the HIPAA configuration | ⚠️ Not covered. Claude Code (local mode) is covered only when Claude Code connects directly to Anthropic, not through a cloud provider or gateway |
Claude Code through an LLM gateway or a custom base URL | Available. These sessions run without the HIPAA configuration | ⚠️ Not covered |
Claude Code with a Claude Console API key, when the Claude Console organization has zero data retention (ZDR) enabled | Available. These sessions run without the HIPAA configuration | ✅ Covered through ZDR, not through the HIPAA configuration |
Claude Code with a Claude Console API key, when the Claude Console organization doesn't have ZDR enabled | Available. These sessions run without the HIPAA configuration | ⚠️ Not covered |
Cloud and remote features
The table lists the features that run a session in the cloud or control a session remotely. None of them are available while the HIPAA configuration is applied.
Feature | Availability | Coverage under your BAA |
Claude Code cloud sessions, whether started from Claude Code on the web, Claude Desktop, or | Not available | ❌ Not available |
Claude Code in the Claude mobile app | Not available | ❌ Not available |
Cowork in the cloud, which members start on the web or in the Claude mobile app | Not available | ❌ Not available |
Claude Code Remote Control, which continues a local session from a phone or browser | Not available | ❌ Not available |
Computer access, which lets sessions and scheduled tasks that run in the cloud use a linked computer's files, apps, and browser | Not available | ❌ Not available |
Dispatch, the Cowork agent that runs tasks in the background | Not available | ❌ Not available |
Routines, which run on a schedule in the cloud | Not available | ❌ Not available |
Claude Code Review, which reviews GitHub pull requests | Not available | ❌ Not available |
Claude Security, the managed service that monitors repositories | Not available | ❌ Not available |
Self-hosted environments, which run cloud sessions on your own infrastructure | Not available | ❌ Not available |
Session sharing links | Not available | ❌ Not available |
Tools, models, and memory in a session
The table lists what Claude and members can use inside a Claude Code (local mode) or Cowork (local mode) session.
Feature | Availability | Coverage under your BAA |
Web search | Available in Claude Code. In Cowork, off until an Owner turns on Web search in Organization settings > Capabilities | ✅ Covered |
Web fetch, where Claude retrieves a URL | Not available | ❌ Not available |
Computer use, where Claude controls the screen | Not available | ❌ Not available |
Built-in browser in Cowork and the Code tab | Not available. The Code tab's Preview pane still opens local development servers | ❌ Not available |
Screenshot capture into Cowork | Not available | ❌ Not available |
Developer mode in Claude Desktop | Not available | ❌ Not available |
Covered Models, such as Claude Fable 5. These are the models that need 30-day data retention | Available. Not available in Claude Code while your organization has zero data retention (ZDR) for Claude Code, unless Anthropic has expressly authorized it for your organization | ✅ Covered |
Voice dictation, transcription, voice mode, and read-aloud | Available | ✅ Covered |
Fast mode in Claude Code, in research preview | Off until an Owner turns it on in Organization settings > Claude Code. Applying the configuration doesn't change this setting | ⚠️ Not covered |
Dynamic workflows, which run many subagents from a script | Off until an Owner turns it on in Organization settings > Claude Code | ✅ Covered |
Scheduled tasks in Cowork and the Code tab, which run on the member's computer | Available | ✅ Covered |
Auto memory in Claude Code, and project memory in Cowork | Available. Memory stays on the member's computer until someone deletes it, and it isn't synced to the member's account | ✅ Covered |
Permission modes
The table lists the modes that let Claude act with fewer approvals from the member.
Feature | Availability | Coverage under your BAA |
"Automatically approve" mode in Cowork | Off until an Owner turns it on in Organization settings > Capabilities | ✅ Covered |
Bypass permissions mode in the terminal and the Code tab | Available, unless managed settings turn it off | ✅ Covered |
"Skip all approvals" mode in Cowork | Not available | ❌ Not available |
Connectors, MCP servers, and desktop extensions
The table lists the features that connect Claude to other tools. Your BAA doesn't cover any of them, even after an Owner turns them on.
Feature | Availability | Coverage under your BAA |
Connectors, including Google Drive, Gmail, Google Calendar, and custom connectors | Off until an Owner turns each one on in Organization settings > Connectors | ⚠️ Not covered |
The built-in GitHub integration | Off until an Owner turns it on in Organization settings > Connectors | ⚠️ Not covered |
Local MCP servers, which a member configures on their own computer | Available, unless managed settings or the Claude Desktop policy turn them off | ⚠️ Not covered |
Desktop extensions | Off until an Owner adds each one to the Desktop extension allowlist in Organization settings > Connectors | ⚠️ Not covered |
Claude in Chrome | Off until an Owner turns it on in Organization settings > Claude in Chrome | ⚠️ Not covered |
Claude's suggestions of connectors to add | Not available | ❌ Not available |
Claude's suggestions of skills and plugins | Off until an Owner turns on Skills | ⚠️ Not covered |
Skills and plugins
The table lists each kind of skill and plugin. Several rows depend on one setting named Skills, which an Owner turns on or off in Organization settings > Plugins & skills, in the "Policy" tab.
Skill and plugin security scanning isn't available while the HIPAA configuration is applied. Review each skill and plugin before you provide it to members.
Feature | Availability | Coverage under your BAA |
Skills that ship with Claude Code | Off until an Owner turns on Skills | ⚠️ Not covered |
Skills in a member's Claude account, uploaded by the member or provided by the organization | Off until an Owner turns on Skills | ⚠️ Not covered |
Organization plugin marketplace | Off until an Owner turns on Skills | ⚠️ Not covered |
Skills and plugins stored on the member's computer | Available in the terminal and the Code tab, unless managed settings turn them off. In Cowork, off until an Owner turns on Skills | ⚠️ Not covered |
Creating skills in Claude and Cowork | Off until an Owner turns on Skills and User-created skills in the "Policy" tab | ⚠️ Not covered |
Skill sharing with one member or the whole organization | Off until an Owner turns on skill sharing in the "Policy" tab | ⚠️ Not covered |
Skill sharing with a group | Off until an Owner turns on Share with groups in the "Policy" tab | ⚠️ Not covered |
Record a skill in Cowork, where Claude watches the screen | Not available | ❌ Not available |
Other Claude products
The table lists Claude products other than Claude Code and Cowork. Your BAA doesn't cover any of them.
Feature | Availability | Coverage under your BAA |
Claude Tag, which works in Slack | Not available | ❌ Not available |
Claude Design (claude.ai/design) | Off until an Owner turns it on in Organization settings | ⚠️ Not covered |
Claude Science, in beta | Off until an Owner turns it on in Organization settings | ⚠️ Not covered |
Export, sharing, and feedback
The table lists features that send session content out of Claude Code or Cowork. None of them are available while the HIPAA configuration is applied. OpenTelemetry export stays available (see Monitoring and audit).
Feature | Availability | Coverage under your BAA |
Publishing and sharing artifacts, including public links | Not available | ❌ Not available |
Session transcript export from Claude Desktop | Not available | ❌ Not available |
Uploading files from a Claude Code session to a member's Claude account | Not available | ❌ Not available |
Feedback, bug reports, ratings, and surveys | Not available | ❌ Not available |
Crash and error reports to third-party tools | Not available | ❌ Not available |
Monitoring and audit
The table lists the ways your organization can review sessions and usage.
Feature | Availability | Coverage under your BAA |
Claude Code (local mode) and Cowork (local mode) sessions in the Compliance API | Available when the Compliance API is turned on for your organization. Sessions are readable for up to 30 days. Claude Code sessions aren't captured while your organization has ZDR for Claude Code | ✅ Covered |
OpenTelemetry export to your own monitoring tools | Available. By default, Cowork events include session content. Content capture shows how to leave it out | ⚠️ Not covered. The data you export is your organization's responsibility |
Claude Code usage analytics | Not available | ❌ Not available |
Usage reports in the terminal: /usage, /stats, and /insights | Available | ✅ Covered |
Coverage without the HIPAA configuration
The table shows what your BAA covers in an organization that has enabled HIPAA but hasn't applied the HIPAA configuration. Members can still use Claude Code and Cowork in that organization where an Owner has them turned on.
Product | Coverage under your BAA |
Claude Code in the terminal and in the Code tab of Claude Desktop, with ZDR for Claude Code | ✅ Covered through ZDR. ZDR is available for qualified accounts only |
Claude Code, without ZDR for Claude Code | ⚠️ Not covered |
Cowork | ⚠️ Not covered |
API features (on a HIPAA ready API org)
API Feature (on a HIPAA Ready API Org) | Availability |
Messages API | See table below |
Token Counting API | ✅ Covered as Eligible Services under Anthropic BAA* |
Models API | ✅ Covered as Eligible Services under Anthropic BAA* |
Org Management API | ✅ Covered as Eligible Services under Anthropic BAA* |
Compliance API | ✅ Covered as Eligible Services under Anthropic BAA* |
Batch API | ❌ Not covered under Anthropic BAA and not accessible for HIPAA-Ready API users |
Files API [beta] | ❌ Not covered under Anthropic BAA and not accessible for HIPAA-Ready API users |
Skills API [beta] | ❌ Not covered under Anthropic BAA and not accessible for HIPAA-Ready API users |
Code Execution | ❌ Not covered under Anthropic BAA and not accessible for HIPAA-Ready API users |
Computer Use [beta] | ❌ Not covered under Anthropic BAA and not accessible for HIPAA-Ready API users |
Web Fetch | ❌ Not covered under Anthropic BAA and not accessible for HIPAA-Ready API users |
External MCP | ⚠️ Available to use but sending data to 3rd parties via this feature isn’t covered under Anthropic’s BAA. Administrators who enable these features are responsible for ensuring their workforce uses them in compliance with applicable legal obligations. |
Data retention periods within a HIPAA-Enabled API Organization are described in Anthropic’s public documentation.
Messages API features
The Messages API is covered as an Eligible Service under your BAA. The following Messages API features are covered under your BAA. Messages API features not listed below are not covered under your BAA.
Messages API Feature | Availability |
Prompt Caching | ✅ Covered as Eligible Services under Anthropic BAA* |
Structured Outputs | ✅ Covered as Eligible Services under Anthropic BAA* |
Memory | ✅ Covered as Eligible Services under Anthropic BAA* |
Web Search | ✅ Covered as Eligible Services under Anthropic BAA* |
Bash tool | ✅ Covered as Eligible Services under Anthropic BAA* |
Text Editor tool | ✅ Covered as Eligible Services under Anthropic BAA* |
*Covered under versions of the BAA accepted after 4/1/26
Product BAA coverage by surface
In this table, "the HIPAA configuration" is the configuration that the Primary Owner applies to Claude Code (local mode) and Cowork (local mode). Applying it is a separate step from enabling HIPAA. See Use Claude Code (local mode) and Cowork (local mode) on a HIPAA-ready Enterprise plan.
CLAUDE ENTERPRISE(limited to features listed below) |
|
Core chat features | BAA coverage status |
Chat | ✅ Eligible under BAA |
Projects (in chat) | ✅ Eligible under BAA ⚠️ Applies to projects in chat only. Does not include projects in other products, which are not covered, even if accessible in your organization. |
Artifacts (in chat) | ✅ Eligible under BAA ⚠️ Applies to artifacts in chat only. Does not include published artifact pages or artifacts in Cowork (local mode) or Code (local mode), which are not covered, even if accessible in your organization. |
File creation & code execution | ✅ Eligible (excl. network / ext. sites) |
Voice | ✅ Eligible under BAA |
Web search | ✅ Eligible under BAA |
Research | ✅ Eligible under BAA |
Integrations (3rd-party data flows) | BAA coverage status |
MCPs / Connectors | ⚠️ 3P data flows not covered by Anthropic BAA |
Enterprise Search ("Ask Your Org") | ⚠️ 3P data flows not covered by Anthropic BAA |
Claude in Chrome | ⚠️ 3P data flows not covered by Anthropic BAA |
Skills | ⚠️ Available but not covered under BAA |
Claude Code | BAA coverage status |
Claude Code with a Claude Console API key | ✅ Eligible only with ZDR enabled |
Claude Code in the terminal (via Claude Enterprise sign-in) | ✅ Eligible with the HIPAA configuration applied
✅ Eligible with ZDR enabled (for qualified accounts) |
Claude Code in the Code tab of Claude Desktop | ✅ Eligible with the HIPAA configuration applied
✅ Eligible with ZDR enabled (for qualified accounts) |
Claude Code cloud sessions, whether started from Claude Code on the web, Claude Desktop, or | ❌ Not covered under BAA |
Claude Code Review (beta) | ❌ Not covered under BAA |
Claude Code Security (beta) | ❌ Not covered under BAA |
Claude Code Computer Use (beta) | ❌ Not covered under BAA |
Claude Code Remote Control (beta) | ❌ Not covered under BAA |
Claude Code in the Claude mobile app | ❌ Not covered under BAA |
Claude Code extensions for VS Code and JetBrains | ⚠️ Available but not covered under BAA |
Claude Code through an LLM gateway or a custom base URL | ⚠️ Available but not covered under BAA |
Claude Code through Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry | ⚠️ Available but not covered under BAA |
Cowork | BAA coverage status |
Cowork in Claude Desktop | ✅ Eligible with the HIPAA configuration applied |
Cowork in the cloud | ❌ Not covered under BAA |
Other beta features | BAA coverage status |
Claude Design (beta) | ❌ Not covered under BAA |
Claude Slides (beta) | ❌ Not covered under BAA |
Claude Docs (beta) | ❌ Not covered under BAA |
CLAUDE PLATFORM (1P API) |
|
Native 1P API features | BAA coverage status |
Messages API (prompt caching, structured outputs, memory, web search, bash tool, text editor tool) | ✅ Eligible under BAA |
Token Counting, Models, Org Management, Compliance APIs | ✅ Eligible under BAA |
Batch API, Files API, Skills API, Code Execution, Computer Use, Web Fetch | ❌ Not covered under BAA |
External MCP | ⚠️ 3P data flows not covered by Anthropic BAA |
ZDR-Eligible (covered under BAA with ZDR) | BAA coverage status |
Claude Code with a Claude Console API key | ✅ Eligible only with ZDR enabled (for qualified accounts) |
CLAUDE IN MICROSOFT FOUNDRY |
|
API features (with the HIPAA configuration enabled) | BAA coverage status |
Claude API through Microsoft Foundry (Anthropic-hosted or Microsoft-hosted) | ✅ Eligible under BAA. Some features, such as the Compliance API, are not available in Foundry. For a list of unavailable features, see Claude in Microsoft Foundry. |
Please see our Trust Portal for more information about our compliance commitments.