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 ChatGPT for Healthcare is designed to support HIPAA compliance and includes a restriction that external GPT sharing is not permitted within that service tier.
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 is relevant to healthcare organizations evaluating ChatGPT for Healthcare as a HIPAA-compliant deployment option. The prohibition on external GPT sharing is an operational restriction specific to this tier that healthcare IT and compliance teams should incorporate into their deployment governance.
Interpretive note: The phrase 'designed to support HIPAA compliance' is qualified and does not assert full HIPAA compliance; the scope of HIPAA coverage depends on BAA execution and the specific workflows deployed.
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 →This provision introduces a specialized healthcare product with HIPAA-compliant architecture and restricted sharing controls, addressing regulated industry requirements.
View full change record →Under this provision, ChatGPT for Healthcare is described as designed to support HIPAA compliance, and the agreement restricts external GPT sharing to contain data within the healthcare workspace. Healthcare organizations should confirm BAA execution and assess whether the workspace configuration meets their specific HIPAA compliance obligations.
Cross-platform context
See how other platforms handle ChatGPT for Healthcare HIPAA-Compliant Workspace and similar clauses.
Compare across platforms →Monitoring
OpenAI has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"ChatGPT for Healthcare is a secure workspace designed to support HIPAA compliance and built for healthcare organizations and their clinicians, administrators, and researchers. External GPT sharing is not supported for ChatGPT for Healthcare.Excerpt from OpenAI's Enterprise Privacy
(1) REGULATORY LANDSCAPE: HIPAA requires covered entities and business associates to implement safeguards to protect PHI. The description of ChatGPT for Healthcare as 'designed to support HIPAA compliance' is a commercial representation that does not automatically constitute HIPAA compliance. Healthcare organizations must confirm BAA execution and assess the technical and administrative safeguards in place. HHS Office for Civil Rights is the enforcement authority. (2) GOVERNANCE EXPOSURE: Medium. The representation that the workspace is 'designed to support' HIPAA compliance is qualified language that does not assert full compliance. Healthcare organizations should not rely on this characterization without conducting their own compliance assessment and executing a BAA. (3) JURISDICTION FLAGS: All US healthcare covered entities and business associates are subject to HIPAA. State health data privacy laws in California, New York, and other states may impose additional requirements beyond HIPAA that the workspace may not address. (4) CONTRACT AND VENDOR IMPLICATIONS: Healthcare procurement teams should confirm BAA execution, review the BAA's scope relative to the specific workflows deployed in the workspace, and assess whether the workspace's technical controls meet HIPAA Security Rule requirements. The prohibition on external GPT sharing should be confirmed in administrative controls. (5) COMPLIANCE CONSIDERATIONS: Healthcare compliance teams should document the HIPAA compliance assessment for ChatGPT for Healthcare deployments, maintain executed BAA records, and ensure that workforce training addresses the restrictions applicable to this service tier including the external GPT sharing prohibition.
This provision is relevant to healthcare organizations evaluating ChatGPT for Healthcare as a HIPAA-compliant deployment option. The prohibition on external GPT sharing is an operational restriction specific to this tier that healthcare IT and compliance teams should incorporate into their deployment governance.
Under this provision, ChatGPT for Healthcare is described as designed to support HIPAA compliance, and the agreement restricts external GPT sharing to contain data within the healthcare workspace. Healthcare organizations should confirm BAA execution and assess whether the workspace configuration meets their specific HIPAA compliance obligations.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by OpenAI.