No. Is ChatGPT HIPAA compliant on any plan you can buy today? It is not, because OpenAI does not sign a business associate agreement for its consumer tiers. HIPAA regulates organizations and contracts, not models. And if you type your own health information into your own account, HIPAA never applied.
TL;DR: Key takeaways
- There is no HIPAA compliant ChatGPT on the consumer shelf. Free, Plus and Go, Team, and Enterprise are not sold with a business associate agreement (BAA).
- HIPAA binds health plans, clearinghouses, providers, and their contracted vendors. It does not bind you, typing your own symptoms into your own account.
- What protects consumers instead is the vendor's privacy policy and the Federal Trade Commission, which has already fined a health platform $1.5 million.
- Turning off model training and using temporary chat lowers exposure. It does not create legal coverage.
- If protected health information (PHI) already went into regular ChatGPT, treat it as a potential breach and tell your privacy officer the same day.
Is ChatGPT HIPAA compliant? Not in any version you can sign up for today
Is ChatGPT HIPAA compliant? No. As of this writing, OpenAI does not offer a business associate agreement on its consumer plans (Free, Plus and Go, Team, or Enterprise), and without that signed contract no product can be covered. No AI model is HIPAA compliant on its own: HIPAA regulates organizations and contracts, so compliance depends on a signed BAA plus how the product is configured, restricted, and logged.
The one route where a BAA is even on the table is the healthcare-specific lineup OpenAI launched in January 2026. That lineup is new, its terms are the most volatile fact on this page, and you should verify availability for your own product and tier before relying on it.
Now the reframe that matters more than the verdict: for most people typing into their own account, HIPAA was never the law in play.
People also ask
Yes. Liability attaches to the organization, not the individual. Under the January 28, 2026 inflation adjustment , HIPAA civil monetary penalties run from a Tier 1 minimum of $145 per violation to a Tier 4 minimum of $73,011 per violation, with an annual cap of $2,190,294 per violation category. Each record can count separately, which is how small incidents become large numbers.
Not usually, and the honest answer is a principle rather than a vendor ranking. Compliance follows the contract, not the model. No consumer chatbot from any vendor is sold under a BAA, and neither is ChatGPT HIPAA compliant in its consumer tiers. If a vendor tells you its enterprise or cloud offering can be covered, get that in writing naming your exact product.
HIPAA binds your clinic and its vendors, not you and your keyboard
The law reaches exactly two groups, both defined at 45 CFR §160.103: covered entities (health plans, health care clearinghouses, and providers who transmit health information electronically for standard transactions) and business associates, meaning anyone who creates, receives, maintains, or transmits PHI while performing a function on behalf of a covered entity. That phrase carries the whole weight. A company that happens to receive health-related text from a member of the public is not a business associate.
HHS has already worked this through for apps. Its health app use scenarios guidance finds no business associate relationship when a person fills an app with their own data on their own initiative, with no contract behind it.
So when you paste your own symptoms into your own ChatGPT account, HIPAA does not apply, and OpenAI is not violating it. That is not a loophole. It is the architecture of the statute.
What protects you instead is OpenAI's privacy policy, which functions as an enforceable promise, plus the FTC. The 2024 amended Health Breach Notification Rule explicitly covers health apps and similar technologies not subject to HIPAA. And that enforcement is real: the FTC secured a $1.5 million civil penalty against GoodRx in 2023 for disclosing prescription and health-condition data to Facebook and Google.
Hold the contrast in your head. A consumer chatbot owes you a privacy policy. A telehealth app that is contractually covered owes you HIPAA. Between visits, a health companion app like August AI can help you log symptoms and ask plain-language questions, as an adjunct to care rather than a substitute for it, and never as the thing that decides.
People also ask
Not usually. The HHS Office for Civil Rights takes complaints about covered entities and their business associates. With no BAA in place, OpenAI is neither, so OCR has no jurisdiction over your personal chats. The FTC is the right venue for a consumer complaint about a non-HIPAA health tool, under the FTC Act and the Health Breach Notification Rule.
No. Deletion removes the thread from your view and starts a retention clock; copies may persist in backups, safety systems, and subprocessor logs for a period. More importantly for a clinic, deletion does not undo a disclosure that already happened. If PHI went in, the compliance obligation exists regardless, and deleting the thread destroys the evidence your privacy officer needs.
The real problem is not the chatbot. It is where your words go next
Does ChatGPT share your data? Mechanically, yes, in the ordinary ways a cloud product does. On consumer tiers the defaults allow conversations to be used to improve models, retained for a period, and reviewed by humans for safety and troubleshooting. Subprocessors and infrastructure vendors touch that data while running the service, which is precisely the downstream chain a BAA is written to govern.
The honest answer to does ChatGPT share your data is that it depends on your tier, your settings, and what you connected it to. Which brings up the error I see most often: turning off model training and switching to temporary chat genuinely reduces exposure, and you should do both. It does not create HIPAA coverage. Necessary, not sufficient.
Then there is the quieter risk. Connectors let ChatGPT reach into Gmail, Google Drive, a shared clinic inbox, or an EHR-adjacent tool and read what is there. Nobody has to paste anything. A connector pointed at a mailbox full of referral letters is a disclosure waiting to happen, and it will not look like one in anybody's audit log.
People also ask
Yes, potentially. On workspace plans, the organization owns the account, sets retention, and can have administrative access to conversation data. Assume anything typed into a work account is visible to your employer, the same as work email. Personal health questions belong in a personal account on a personal device, on your own time.
No. A consumer chatbot has no connection to your clinician's EHR or to your health plan, and your chats do not flow into either. The exceptions are ones you create: connecting the tool to accounts holding your records, or pasting its output into a patient portal message. Advertising and data-sharing practices are a separate concern governed by the privacy policy.
ChatGPT Health's "enhanced privacy" is a product promise, not a legal one
Is ChatGPT Health HIPAA compliant?
Is ChatGPT Health HIPAA compliant? No. An individual consumer cannot obtain a business associate agreement on ChatGPT Health no matter which privacy settings they choose, because a BAA is a contract between a covered entity and its vendor, and a patient using a personal account is neither.
Claims about enhanced privacy, isolation, and encryption are product-design assertions. They can describe genuine engineering and still have zero legal effect on whether HIPAA applies, because HIPAA turns on who you are and what you signed, not on how the storage layer is built.
What the product does change for a patient is the default handling of your own data, which is worth something. It does not create a regulated relationship. Keep it separate in your mind from the clinician and enterprise healthcare editions launched in January 2026, which are sold to organizations and are the only place a contract is even discussable.
People also ask
Sometimes, and the dividing line is identifiers. Asking for a generic appeal-letter template with no patient details is not a disclosure of PHI, though your employer's policy may still prohibit it. Pasting in a name, date of birth, visit date, or diagnosis makes it a disclosure to a vendor with no BAA, which is the violation.
Only a signed business associate agreement can make an AI tool compliant
A ChatGPT business associate agreement is the only legal mechanism that pulls OpenAI inside HIPAA for your organization's use. Everything else is hygiene.
| Product or tier | Can a BAA cover it? |
| Free | No. Permanently excluded. |
| Plus / Go | No. Permanently excluded. |
| Team | Not offered. |
| Business | Not offered. |
| Enterprise | Not offered as a consumer-facing term. Ask in writing before assuming. |
| Edu | No. It is not a healthcare SKU. |
| API / platform | Do not assume. Get the answer in writing for your account. |
| ChatGPT for Healthcare | Possible. Confirm for your exact SKU. |
| ChatGPT for Clinicians | Possible. Confirm for your exact SKU. |
| ChatGPT Health (consumer) | No. Not available to an individual. |
The BAA is signed by the organization, not by an individual clinician, and it must name the specific product and tier actually in use. A BAA covering an API account does not cover the browser tab someone logged into with a personal address.
Here is what most pages will not tell you: a signed BAA is a floor, not a finish line. Without role-based access controls, audit logging that someone actually reads, minimum-necessary limits on what gets sent, and workforce training that names this tool specifically, you have a contract and a compliance problem at the same time. Get BAA availability confirmed in writing by OpenAI for your exact SKU rather than inferring it from a marketing page. The 2026 lineup is weeks old in regulatory terms.
Removing the patient's name is not de-identification
Deciding to de-identify PHI before using ChatGPT is the right instinct, but the bar is an HHS standard, not a judgment call. Two methods qualify: Safe Harbor, and formal Expert Determination by a qualified statistician.
Safe Harbor means removing all 18 enumerated identifier categories, and having no actual knowledge that what remains could identify someone. That is names; geography smaller than a state; all dates tied to the individual, including admission, discharge, visit, and birth dates; phone, fax, and email; Social Security, medical record, health plan, and account numbers; certificate and license numbers; vehicle and device identifiers and serial numbers; URLs and IP addresses; biometrics; full-face photographs; and any other unique code.
The ones clinicians leave in are predictable: visit dates, the city, ages over 89, the MRN sitting in the header of the pasted note, a device serial number, a photo, and verbatim free-text quotes that are distinctive enough to name the person on their own.
Concretely, a note stripped of the name that still reads "34-year-old in Bozeman, seen March 3, confirmed rare autoimmune diagnosis" is not de-identified data. It is PHI with the easiest field deleted.
De-identification is also not a cure-all. It removes the HIPAA question. It does not remove your employer's acceptable-use policy, your vendor contracts, or state privacy law, several of which sweep wider than HIPAA does.
A compliant AI workflow in six steps, including if PHI already went in
A HIPAA compliant ChatGPT does not exist as something you buy; what exists is the gap between a tool and a workflow, and these six steps close it.
- Decide which reader you are. Acting for a covered entity means HIPAA applies to what you type. Using your own account for your own health means it does not.
- Confirm in writing whether a BAA covers the exact product and tier before any clinical use. No BAA means no PHI, full stop.
- Turn off model training and use temporary chat. Say out loud what this is: risk reduction, not compliance.
- Audit and disconnect connectors that reach clinical email, cloud storage, or anything adjacent to the EHR, until each one has been reviewed.
- De-identify to the Safe Harbor standard before pasting, then read the output too. Models restate the specifics you fed them.
- If PHI already went in, treat it as a potential breach. Stop using the thread. Do not quietly delete it, because it is evidence. Notify your privacy or compliance officer the same day, document what was disclosed and when, and let them run the Breach Notification Rule risk assessment and make the notification decision. Do not self-clear it.
If you are a patient rather than a clinician, none of that applies to you. You need no BAA and no workaround. Decide what you are comfortable sharing, keep identifiers out of prompts you would not post publicly, and if you are unsure how urgent something is, the free August AI Symptom Checker is a reasonable first triage step. When what you need is care rather than information, for example an online ADHD evaluation, that happens inside a provider relationship where HIPAA does apply from the first intake form.
Some symptoms should never go to a chatbot first
Nothing in this article's privacy advice should delay emergency care. If you are deciding between typing and calling, call.
Call 911 or go to an emergency room now if:
- You have chest pain or trouble breathing.
- You have sudden numbness, slurred speech, or facial drooping, which are stroke signs.
- You have severe bleeding.
- You are having thoughts of suicide. Stop typing and call 911 or 988. AI chat cannot examine you or dispatch help.
Book a visit within the next week if:
- You have been triaging the same symptom with a chatbot for days and it is not improving.
- You have a new lump or an unexplained change in weight.
- The chatbot keeps telling you to see a doctor. That is the answer, not a placeholder.
Talk to a clinician before you start if:
- An AI response tells you to stop a prescribed medication, change a dose, or disregard your care team. Confirm with your prescriber first. These tools produce confidently wrong medical guidance, and they do it in the same tone they use when they are right.
For the middle tier, August's $39 online urgent care visit connects you with a US-licensed clinician who can evaluate symptoms and prescribe when they judge it appropriate. The clinician decides. A video visit cannot examine you in person, order imaging on the spot, or manage an emergency, so anything in the first tier belongs in an ER.
The bottom line
Is ChatGPT HIPAA compliant? No, and that answer will not change because of a setting you toggle. It changes only when an organization signs a BAA naming a specific product and then builds access controls, logging, and training around it. If you are a clinician, the sequence is simple: no contract, no PHI, and de-identify to the Safe Harbor standard when you do use it. If you are a patient, the question was aimed at the wrong law. HIPAA restricts your providers and their vendors. Your protection comes from the privacy policy you agreed to, the FTC behind it, and your own judgment about what to type.
Disclaimer: This article is for informational purposes only and does not constitute medical advice. Always consult a qualified healthcare provider for diagnosis and treatment decisions. If you are experiencing a medical emergency, call 911 or go to the nearest emergency room immediately.
Frequently Asked Questions
Yes. Liability attaches to the organization, not the individual. Under the January 28, 2026 inflation adjustment, HIPAA civil monetary penalties run from a Tier 1 minimum of $145 per violation to a Tier 4 minimum of $73,011 per violation, with an annual cap of $2,190,294 per violation category. Each record can count separately, which is how small incidents become large numbers.
Not usually, and the honest answer is a principle rather than a vendor ranking. Compliance follows the contract, not the model. No consumer chatbot from any vendor is sold under a BAA, and neither is ChatGPT HIPAA compliant in its consumer tiers. If a vendor tells you its enterprise or cloud offering can be covered, get that in writing naming your exact product.
Not usually. The HHS Office for Civil Rights takes complaints about covered entities and their business associates. With no BAA in place, OpenAI is neither, so OCR has no jurisdiction over your personal chats. The FTC is the right venue for a consumer complaint about a non-HIPAA health tool, under the FTC Act and the Health Breach Notification Rule.
No. Deletion removes the thread from your view and starts a retention clock; copies may persist in backups, safety systems, and subprocessor logs for a period. More importantly for a clinic, deletion does not undo a disclosure that already happened. If PHI went in, the compliance obligation exists regardless, and deleting the thread destroys the evidence your privacy officer needs.
Yes, potentially. On workspace plans, the organization owns the account, sets retention, and can have administrative access to conversation data. Assume anything typed into a work account is visible to your employer, the same as work email. Personal health questions belong in a personal account on a personal device, on your own time.
No. A consumer chatbot has no connection to your clinician's EHR or to your health plan, and your chats do not flow into either. The exceptions are ones you create: connecting the tool to accounts holding your records, or pasting its output into a patient portal message. Advertising and data-sharing practices are a separate concern governed by the privacy policy.
Sometimes, and the dividing line is identifiers. Asking for a generic appeal-letter template with no patient details is not a disclosure of PHI, though your employer's policy may still prohibit it. Pasting in a name, date of birth, visit date, or diagnosis makes it a disclosure to a vendor with no BAA, which is the violation.
