Provision record
OpenAI · OpenAI API Data Usage Policies [RETIRED: redirects to /enterprise-privacy/ (CA-D-000825)] · View original document ↗

Fine-Tuning Data Retention and Model Exclusivity

Medium severity High confidence Explicitdocumentlanguage Unique · 0 of 352 platforms
Get alerted the next time OpenAI changes these terms. Follow OpenAI →
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity OpenAI recorded 30 documented changes in the last 30 days.
Follow OpenAI →
Monitor governance changes for OpenAI Monitor emails you the same day this changes. The archive stays free.
Follow OpenAI →

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.

Document Record

What it is

The document states that fine-tuned models created using customer data are exclusive to the customer and are not shared or used to train other models, and that fine-tuning data is retained until the customer actively deletes the files.

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes that fine-tuning data has an indefinite retention period by default, persisting until the customer deletes the files, which differs from the 30-day default retention period applicable to standard API inputs and outputs.

Recent Activity

This document changed recently

Medium Jul 16, 2026

The updated policy now states that workspace admins 'can control' data retention rather than 'control' it, introducing subtle ambiguity about whether retention control is a guaranteed right or a permitted option. Additionally, the removal of the word 'workspace' before 'data' broadens the scope of data potentially subject to admin control beyond workspace-specific information. These changes could affect how enterprise customers understand the extent of their administrative authority over data retention practices.

View change record →
Medium May 28, 2026

The updated terms establish that workspace admins, rather than individual end users, control how long workspace conversation data is retained and authorize admins to view, access, export, and delete end user conversations. Previously, the policy stated that each user controlled whether their conversations were retained and that only end users could view their own conversations. The revised terms also permit OpenAI to retain deleted or unsaved conversations beyond the standard 30-day deletion window if retention is required by law or reasonably necessary to protect OpenAI's services or third parties from harm. Workspace users should review their organization's data governance policies to understand what access and retention practices their admins have implemented.

View change record →

Clause Stability Mostly Stable

1
Change
2
Months Monitored
Jul 9, 2026
First Seen
Jul 9, 2026
Last Seen
This clause has changed once in 2 months of monitoring.

Change history

added Jul 16, 2026

This new provision addresses a specific use case with distinct data handling practices, guaranteeing model exclusivity and customer-controlled data retention for fine-tuned models.

View full change record →

Consumer impact (what this means for users)

Under this provision, data submitted for model fine-tuning is retained on OpenAI systems indefinitely until the customer takes affirmative action to delete the files. Customers intending to limit fine-tuning data retention must actively manage and delete files through the platform.

What you can do

⚠️ These actions may provide transparency or partial mitigation but may not fully address the underlying issue. Effectiveness varies by jurisdiction and individual circumstances.
  • Delete Your Data
    Log in to the OpenAI platform, navigate to the fine-tuning section, and delete any fine-tuning files that are no longer required for active model use to trigger removal from OpenAI systems.

Cross-platform context

See how other platforms handle Fine-Tuning Data Retention and Model Exclusivity 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.

Follow OpenAI → Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
Yes, you can adapt certain models to specific tasks by fine-tuning them with your own prompt-completion pairs. Your fine-tuned models are for your use alone and never served to or shared with other customers or used to train other models. Data submitted to fine-tune a model is retained until the customer deletes the files.

Excerpt from OpenAI's API Data Usage Policies [RETIRED: redirects to /enterprise-privacy/ (CA-D-000825)]

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

(1) REGULATORY LANDSCAPE: This provision engages GDPR storage limitation principles under Article 5(1)(e), which requires that personal data be retained no longer than necessary for the stated processing purpose. Indefinite retention until customer-initiated deletion may require justification under the storage limitation principle if the fine-tuning data contains personal data. HIPAA minimum necessary and retention standards apply to API customers processing PHI through fine-tuning. The FTC has general authority over data retention representations. (2) GOVERNANCE EXPOSURE: Medium. The indefinite retention default creates a data governance obligation for organizations to track and manage fine-tuning file deletion as part of their data lifecycle management processes. Organizations that have submitted personal data through fine-tuning without a deletion workflow may have retention periods inconsistent with their stated data minimization policies. (3) JURISDICTION FLAGS: EU and EEA customers face heightened exposure if fine-tuning data contains personal data, as indefinite retention without a defined necessity period may not satisfy GDPR Article 5(1)(e). California customers should assess CPRA service provider obligations relative to fine-tuning data retention. Healthcare API customers should assess HIPAA retention standards applicable to PHI submitted through fine-tuning. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should ensure that executed DPAs or BAAs address fine-tuning data retention and deletion obligations, including whether OpenAI will delete fine-tuning data upon contract termination or account closure. Vendor assessments should include confirmation of the deletion process and timeline for fine-tuning files. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should establish a data lifecycle management procedure for fine-tuning files, including periodic review and deletion of files no longer needed for active model maintenance. Data processing records should document fine-tuning data as a distinct retention category with an active deletion obligation. Organizations should assess whether fine-tuning data submitted to date is consistent with their stated data minimization and retention policies.

Full institutional analysis

Regulatory citations, enforcement risk, and due diligence action items.

Applicable agencies

  • FTC
    The FTC has authority over data retention representations and practices applicable to business customers using AI fine-tuning services.
    File a complaint →

Provision details

Document information
Document
OpenAI API Data Usage Policies [RETIRED: redirects to /enterprise-privacy/ (CA-D-000825)]
Entity
OpenAI
Document last updated
May 12, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-013612
Document ID
CA-D-00789
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
1ae7d9fa2dca070b64ed5b07ad1ec3806fc650d1cfbfeddb552af548e6be6663
Analysis generated
July 9, 2026 03:33 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: OpenAI
Document: OpenAI API Data Usage Policies [RETIRED: redirects to /enterprise-privacy/ (CA-D-000825)]
Record ID: CA-P-013612
Captured: 2026-07-09 03:33:57 UTC
SHA-256: 1ae7d9fa2dca070b…
URL: https://conductatlas.com/platform/openai/openai-api-data-usage-policies-retired-redirects-to-enterprise-privacy-ca-d-000825/provision/CA-P-013612/fine-tuning-data-retention-and-model-exclusivity/
Accessed: July 26, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Governance intelligence across arbitration, AI governance, data rights, indemnification, and retention

Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.

Frequently Asked Questions

What does OpenAI's Fine-Tuning Data Retention and Model Exclusivity clause do?

This provision establishes that fine-tuning data has an indefinite retention period by default, persisting until the customer deletes the files, which differs from the 30-day default retention period applicable to standard API inputs and outputs.

How does this clause affect you?

Under this provision, data submitted for model fine-tuning is retained on OpenAI systems indefinitely until the customer takes affirmative action to delete the files. Customers intending to limit fine-tuning data retention must actively manage and delete files through the platform.

Is ConductAtlas affiliated with OpenAI?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by OpenAI.