Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
The document states that OpenAI can execute a Business Associate Agreement with API customers who require HIPAA compliance coverage, enabling use of the API in contexts involving protected health information.
This analysis describes what OpenAI's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that API-based deployments handling protected health information may be eligible for BAA coverage, which is a prerequisite for using a third-party vendor under HIPAA. The provision specifies API deployments; compliance teams should confirm whether ChatGPT Enterprise or other product tiers are also within scope of the BAA.
Interpretive note: The provision specifies API customers; whether the BAA extends to ChatGPT Enterprise or other product tiers is not explicitly addressed in this document and should be confirmed with OpenAI directly.
The updated terms state that workspace admins 'can control' data retention rather than directly controlling it. This conditional phrasing may suggest that retention control is optional or contingent rather than a guaranteed capability. Enterprise customers relying on admin-driven data retention policies should clarify with OpenAI whether this change affects their ability to set specific retention timelines for workspace data.
View change record →The updated terms shift governance of conversation access and retention from end users to workspace administrators. Under the revised policy, workspace admins can now view, access, export, and delete any end user conversations within their workspace and control how long workspace data is retained. Additionally, OpenAI now reserves the right to retain deleted or unsaved conversations beyond the standard 30-day deletion window if retention is reasonably necessary to protect its services or any third party from harm, beyond prior language that limited retention extensions to legal requirements. Within an enterprise account, end users no longer have unilateral control over conversation visibility or deletion of their own conversations.
View change record →Narrowed scope from general 'customers' to specifically 'API customers' and removed mention of 'HIPAA-eligible services' in favor of direct BAA signing capability.
View full change record →Under this provision, healthcare organizations using OpenAI's API can request a BAA before processing protected health information. The provision is scoped to API customers; organizations using ChatGPT Enterprise should independently confirm BAA availability for that product tier.
How other platforms handle this
If you choose to reveal any personal information about yourself to other users, you do so at your own risk. We strongly encourage you to use caution in disclosing any personal information online.
When you are asked to provide information, you may decline to do so; but if you choose not to provide information that is necessary to provide some of our Services, you may not be able to use those Services.
Monitoring
OpenAI has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"For API customers who require a Business Associate Agreement (BAA) for HIPAA compliance, we are able to sign a BAA.Excerpt from OpenAI's Enterprise Privacy
(1) REGULATORY LANDSCAPE: This provision engages the Health Insurance Portability and Accountability Act (HIPAA), specifically the requirements for Business Associate Agreements under 45 CFR Part 164, Subpart E. The relevant enforcement authority is the U.S. Department of Health and Human Services Office for Civil Rights. Where covered entities or business associates transmit PHI through OpenAI's API without an executed BAA, they may be in violation of HIPAA's safeguard and business associate requirements. (2) GOVERNANCE EXPOSURE: High for healthcare organizations or any enterprise customer whose API use involves PHI. The document discloses BAA availability but does not describe the scope of permitted uses of PHI under the BAA, or whether OpenAI's model infrastructure satisfies HIPAA's technical safeguard requirements. Without a BAA in place, API use involving PHI is not permissible under HIPAA. (3) JURISDICTION FLAGS: All US-based covered entities and business associates are subject to HIPAA BAA requirements. State-level health privacy laws (such as Washington My Health MY Data Act or California CMIA) may impose additional obligations beyond HIPAA, and the BAA scope should be evaluated against those frameworks as well. (4) CONTRACT AND VENDOR IMPLICATIONS: Healthcare procurement teams should execute the BAA prior to any API deployment involving PHI. The BAA should be reviewed to confirm it addresses permitted uses, safeguard obligations, breach notification timelines, and sub-contractor flow-down requirements. Teams should also assess whether OpenAI's sub-processors are covered by equivalent BAAs, as required under HIPAA's business associate chain requirements. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should document BAA execution in their HIPAA vendor management records and conduct a risk analysis of OpenAI's technical safeguards prior to transmitting PHI. The scope of the BAA (API only vs. other products) should be confirmed in writing, and any use of fine-tuning or retrieval-augmented generation features involving PHI should be explicitly addressed in the agreement.
Regulatory citations, enforcement risk, and due diligence action items.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
This provision establishes that API-based deployments handling protected health information may be eligible for BAA coverage, which is a prerequisite for using a third-party vendor under HIPAA. The provision specifies API deployments; compliance teams should confirm whether ChatGPT Enterprise or other product tiers are also within scope of the BAA.
Under this provision, healthcare organizations using OpenAI's API can request a BAA before processing protected health information. The provision is scoped to API customers; organizations using ChatGPT Enterprise should independently confirm BAA availability for that product tier.
ConductAtlas has identified this type of provision across 295 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by OpenAI.