OpenAI's "Data controls in ChatGPT" Help Center page now has a "Trusted Access on personal accounts" section: during sessions in Trusted Access programs such as Daybreak Blue, OpenAI may use interaction content to improve its models even when "Improve the model for everyone" is off, to strengthen safeguards against cyber misuse, while other activity still follows the user's setting. Emails that several users shared on X say the change takes effect November 29, and researchers including Sean Heelan criticized it for pulling unreported vulnerabilities and research into training data.

Key Takeaways

  • ✓Official wording: Trusted Access sessions such as Daybreak Blue on personal accounts may be used to improve models regardless of the "Improve the model for everyone" toggle
  • ✓The exception covers only Trusted Access sessions; other chats on the account still follow the existing setting
  • ✓Managed workspaces such as Business and Enterprise, and the API, are still not used for training by default
  • ✓Emails users shared on X say it takes effect November 29, and some users say individuals lose Daybreak Blue API access on November 20 (the official pages do not state either date yet)
  • ✓Sean Heelan's critical post drew 600+ likes and 100+ reposts, and several bug bounty hunters said they would reconsider using the program
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Background and the problem

Daybreak is OpenAI's Trusted Access for Cyber program, with tiers such as Daybreak Blue and Daybreak Red. Vetted security researchers get models with fewer refusals in ChatGPT and Codex for defensive work such as vulnerability and malware analysis. According to the OpenAI Help Center, individuals must enable Advanced Account Security and register at least one physical FIDO2 hardware key to qualify. The catch is that researchers often feed the model unreported vulnerabilities, target details and proofs of concept, so whether that content ends up in training data is a hard line for them.

Architecture and how it works

OpenAI's updated "Data controls in ChatGPT" page adds a "Trusted Access on personal accounts" section. During Daybreak sessions, OpenAI may use interaction content to improve its models even when "Improve the model for everyone" is off, to strengthen safeguards against cyber misuse. Activity outside Trusted Access sessions still follows the user's own setting. Meanwhile, the Advanced Account Security page still says conversations are not used to train OpenAI models while that setting is enabled, and OpenAI has not explained how the two documents fit together. Managed workspaces (Business, Enterprise, Edu) and the API Platform are still not used for training by default.

Benchmarks and measured results

This is a data policy story with no model scores involved, and OpenAI has published no related evaluations. The official pages do not give an effective date. Emails that several users posted on X say the change starts November 29, and some users also say individuals lose Daybreak Blue API access on November 20 while Codex via ChatGPT sign-in stays; both points come from user-shared emails. On the community side, security researcher Sean Heelan's critical post drew more than 600 likes and 100 reposts, calling it taking researchers' private work and predicting it would hurt Daybreak usage.

Practical guide for developers

Individuals using Daybreak Blue should assume anything in a Daybreak session may be used for training, and avoid pasting details of unreported vulnerabilities, client asset information or unsubmitted reports. Teams that need a stricter data boundary can look at organization-level Daybreak access: OpenAI says managed workspaces and the API are not used for training by default, and organization access has its own onboarding process. Check your training setting under Settings > Data controls in ChatGPT, and watch the Help Center pages for an official effective date and scope.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextOpenAI Discloses PHP Zero-Day Critical Flaws Found via GPT-5.6 Sol, Open-Sources Scanner and Pledges $1B Defense Fund
Read Now→