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 access to stored business conversations is limited to authorized OpenAI employees for engineering support, abuse investigation, and legal compliance, and to third-party contractors bound by confidentiality and security obligations for abuse and misuse review.
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 defines the human access controls applicable to stored business data across ChatGPT Business, ChatGPT for Teachers, and the API Platform. The disclosure of third-party contractor access for abuse review is operationally relevant for organizations with data residency, confidentiality, or vendor management obligations.
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 transparently defines who can access business data and for what purposes, with explicit limitations on contractor access and confidentiality requirements.
View full change record →Under this provision, stored business conversations may be accessed by authorized employees and specialized third-party contractors under defined conditions. The document states that contractor access is limited to abuse and misuse review and that contractors are bound by confidentiality and security obligations.
Cross-platform context
See how other platforms handle Authorized Employee and Contractor Access to Business Data 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.
"Our access to conversations stored on our systems is limited to (1) authorized employees that require access for engineering support, investigating potential platform abuse, and legal compliance and (2) specialized third-party contractors who are bound by confidentiality and security obligations, solely to review for abuse and misuse.Excerpt from OpenAI's Enterprise Privacy
(1) REGULATORY LANDSCAPE: Third-party contractor access to personal data processed on behalf of enterprise customers engages GDPR Article 28(4), which requires that processors impose equivalent data protection obligations on sub-processors. The disclosure of third-party contractor access may require review of executed DPAs to confirm sub-processor authorization and obligations are adequately addressed. HIPAA sub-contractor BAA requirements are relevant for healthcare customers. (2) GOVERNANCE EXPOSURE: Medium. The provision identifies third-party contractors as accessing stored conversations but does not identify the contractors by name or disclose their locations. EU and UK organizations should confirm that DPAs include a current sub-processor list and that appropriate transfer mechanisms are in place for any cross-border sub-processor data access. (3) JURISDICTION FLAGS: EU and UK organizations should confirm that sub-processor arrangements are disclosed and authorized in executed DPAs, including international transfer mechanisms for sub-processors located outside the EEA. Healthcare organizations should confirm that third-party contractor access is covered by the BAA. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should request the current sub-processor list from OpenAI and assess sub-processor locations, confidentiality obligations, and security standards. DPAs should include provisions for customer notification of sub-processor changes. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should maintain records of OpenAI's disclosed sub-processor arrangements and monitor for updates. Privacy impact assessments should address third-party contractor access as part of the overall data processing risk assessment.
This provision defines the human access controls applicable to stored business data across ChatGPT Business, ChatGPT for Teachers, and the API Platform. The disclosure of third-party contractor access for abuse review is operationally relevant for organizations with data residency, confidentiality, or vendor management obligations.
Under this provision, stored business conversations may be accessed by authorized employees and specialized third-party contractors under defined conditions. The document states that contractor access is limited to abuse and misuse review and that contractors are bound by confidentiality and security obligations.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by OpenAI.