Is Notion AI HIPAA Compliant? Yes, on an Enabled Workspace

Yes. Notion AI can process PHI, provided it is running inside a Notion Enterprise workspace with HIPAA compliance enabled and Notion's BAA signed.

This answer has changed, and a lot of published guidance has not caught up — including, until this audit, ours. The widely repeated claim is that Notion signs a BAA for the workspace and carves AI out of it. Notion's own documentation does not say that. Its AI security documentation says the opposite, and its HIPAA article draws the exclusion somewhere narrower and more specific.

Getting this wrong in the cautious direction has a cost too. A practice that believes AI is categorically off-limits either forgoes it entirely or, more often, uses it anyway on the quiet assumption that the rule is overcautious — which is the worst of both, because then nobody is governing the setting that actually matters.

Where the line actually falls

Notion's HIPAA framework has two layers, but the line between them is not core-versus-AI.

The workspace. Eligibility to sign Notion's BAA requires the Enterprise Plan. Notion states HIPAA compliance is available free of charge on that plan; an admin enables it at Settings → Workspace settings → HIPAA compliance. Once enabled and the BAA is signed, the workspace may hold PHI.

Notion AI. Covered on the same basis. Notion's AI security documentation states that Notion AI "enables HIPAA compliance by utilizing LLM provider's zero-retention APIs and allows for the processing of protected health information (PHI)." For Enterprise workspaces Notion describes zero data retention with its LLM providers; non-Enterprise workspaces sit under a retention window Notion describes as 30 days or fewer.

Beta Services. This is the actual exclusion. Notion's HIPAA article states that "Any Beta Services are not covered by the BAA and therefore may not be used or deployed in a manner that processes protected health information." That is a moving boundary — what counts as beta changes as features ship — which makes it an ongoing governance question rather than a one-time configuration decision.

The workspace-level PHI limits apply to AI use as they do to everything else. Notion may not be used to communicate with patients, plan members, or their families or employers. PHI may not appear in workspace or organization names, teamspace names, file names, account or user profile, or the names of user groups. Support requests and their attachments must contain no PHI.

The setting that deserves your attention

The zero-retention basis is not unconditional. Notion states that certain AI-powered features may require the use of data-retaining LLMs, and that where they do, Notion will make workspace settings available so administrators can turn those on.

That is the control worth writing into policy. It is an administrator decision and it is reversible, and Notion's stated HIPAA support for Notion AI rests on the zero-retention configuration — so turning on a data-retaining LLM changes the configuration that support is described against. Notion's material does not say doing so is itself a violation, and neither do we. What it does mean is that the change deserves its own review with Notion before PHI passes through the feature, rather than being waved through as a product setting or banned on a hunch. Nothing about it announces itself as a compliance event — it appears as a settings toggle that unlocks a feature someone wanted.

So the governance question is not "is AI allowed." It is: who can flip that setting, do you know its current state, and would you notice if it changed.

Why the old answer was plausible

The reasoning that produced the wrong answer is worth keeping, because it is still the right reasoning for other products.

Notion AI does not run its own models. It sends prompts and context to third-party LLM providers, which means at least one more vendor in the chain. For that chain to carry PHI, the coverage has to reach all the way down — and for a long time, in most embedded-AI products, it did not. Vendors shipped AI features on top of a HIPAA-eligible core and carved them out of the BAA precisely because the downstream contracts were not in place.

What changed is that Notion put them in place, and says so. The mechanism it cites is the LLM providers' zero-retention APIs: the data is processed and not retained, and Notion contracts on that basis for Enterprise workspaces.

The generalisable lesson is not "AI features are excluded." It is that embedded AI inherits its coverage from contracts you cannot see, so the question to ask of any vendor is what the current documentation says rather than what the architecture implies. Microsoft 365 Copilot, Gemini in Google Workspace and Salesforce's Einstein and Agentforce services each answer this question in their own documentation, and each answer moves.

Common mistakes

Assuming the old answer still holds. The most common error is now the one this page used to make: treating AI as categorically outside the BAA. It leads practices to either lose the tool or use it without governing it.

Not knowing whether HIPAA compliance is actually enabled. The Enterprise Plan makes you eligible to sign the BAA. Signing the BAA and switching HIPAA compliance on in workspace settings are separate acts. A workspace can be on Enterprise, with AI in daily use, and never have been enabled.

Leaving the data-retaining-LLM setting ungoverned. Notion exposes it to administrators for features that require it. If no one owns that toggle, no one will notice when it changes.

Using Beta Services with PHI. This is the exclusion that is actually in the document, and it is the one nobody checks, because beta features arrive looking like ordinary features.

Letting PHI into names rather than content. Notion's limits prohibit PHI in workspace, teamspace, file, profile and user-group names. AI output pasted into a page title, or a file named after a patient, breaks the rule in a place no policy document thinks to look.

Treating connections as covered because the workspace is. Existing app connections stay enabled when HIPAA compliance is switched on. Notion tells admins to review them. Anything a connection reaches is governed by that other product's terms, not Notion's BAA.

How to Manage Notion in a HIPAA-Compliant Environment

Two approaches work, depending on operational needs.

Approach 1: Hard separation by workspace

The cleanest model for many practices is to maintain two Notion workspaces.

• Clinical workspace. Notion Enterprise with BAA. Notion AI disabled at the workspace level. Used for any content that may contain PHI — clinical workflows, patient communications, care coordination notes.
• Operations workspace. Standard Notion (or Enterprise without HIPAA scope). Notion AI enabled. Used for non-clinical work — marketing, engineering, internal documentation that does not involve patient data.

The boundary is enforced by workspace separation. Workforce training reinforces what goes where.

Approach 2: Single workspace with AI hard-disabled

For smaller practices that do not need the operational flexibility of two workspaces:

• Single Notion Enterprise workspace with BAA.
• Notion AI disabled at the workspace level for all users.
• Audit log review confirms AI features are not enabled by individual users.
• Policy and training prohibit any use of AI features within the workspace.

This approach works but requires ongoing diligence. A workspace admin who toggles AI back on, or a user who finds a workaround, can reintroduce exposure.

Approach 3: Don't use Notion for PHI at all

Many practices conclude that Notion is best kept on the operations side of the boundary entirely. PHI lives in the EHR, the practice management system, and HIPAA-built collaboration tools. Notion is reserved for non-clinical work where AI features can be used freely.

This is the simplest answer for practices without operational pressure to use Notion clinically.

Where Notion AI Fits in Your Compliance Program

The Notion AI question generalizes to a broader pattern: AI features in SaaS products that have HIPAA-eligible cores. The same boundary exists in many tools — Microsoft 365 Copilot, Google Workspace Gemini features, Salesforce Einstein GPT, and others. Each requires the same evaluation: Is the AI feature inside or outside the BAA? That evaluation, run across the common categories rather than one product, is which tools can hold patient information.

The compliance program needs explicit policy on AI feature usage in covered workspaces, training on the boundary, and configuration controls that disable AI features where the policy requires it.

Patient Protect records the AI tools your practice enters, tracks the state of each vendor's BAA, and keeps the documentation of what you decided about them. It does not reach into those platforms to inspect their configuration — that review stays yours to run.

Frequently Asked Questions

Does Notion sign a BAA?

Yes — eligibility to sign it requires the Enterprise Plan, and Notion states HIPAA compliance is free of charge on that plan. Free, Plus and Business are not eligible. The BAA does not carve out Notion AI; the exclusion it states is for Beta Services.

Can I use Notion AI on non-PHI content within a HIPAA workspace?

Operationally, the boundary is hard to enforce. A "non-PHI" page can drift into PHI territory through edits, copy-paste, or accidental inclusion. The cleanest approach is to disable AI features on the HIPAA workspace entirely or maintain a separate workspace for AI use.

What about Notion AI Connectors with HIPAA-eligible source systems?

The connector pulls content from the source into the AI processing flow. Even if the source system is HIPAA-eligible, the AI provider in the chain is not under a BAA. The connector path is uncovered.

Are there any HIPAA-eligible AI features in Notion?

As of mid-2026, no. Notion AI as a category is excluded from the BAA. If Notion adds a separately-contracted "AI for healthcare" tier in the future, that would be a different product question — but it does not exist today.

Can I use ChatGPT or Claude directly in a HIPAA-compliant way?

Some AI providers offer direct API access with BAAs on enterprise tiers — Anthropic for Claude, OpenAI for ChatGPT Enterprise, with specific Zero Data Retention configurations. Those direct BAAs do not extend to AI features in third-party SaaS products like Notion. If you need HIPAA-compliant AI, contract directly with the AI provider on their enterprise tier and run the workflow through that contract.

Does this same concern apply to Microsoft 365 Copilot and Google Gemini?

Yes — the same architectural pattern applies. Each of those AI products has its own coverage status that must be evaluated separately from the underlying productivity suite's BAA. Many AI features are excluded from the standard BAAs of their parent products. Verify per product before using AI features in HIPAA workflows.

---

Patient Protect tracks your full compliance program — including AI feature coverage, BAA scope, and workspace configurations — starting at $39/month.