# OpenAI Will Train on Daybreak Blue Sessions From Nov 29

> From November 29, OpenAI may train on Daybreak Blue sessions on personal accounts even with the opt-out off. What changes, and who it skips.

- Author: Nitish Garg, Founder & CEO, CellCog
- Published: 2026-10-30
- Canonical (HTML): https://cellcog.ai/blog/openai-daybreak-blue-training/
- Section: Guides / Trust, permissions & security
- Publisher: CellCog (https://cellcog.ai), the AI employee platform. Blog index for agents: https://cellcog.ai/blog/llms.txt

## Key points

- OpenAI emailed Daybreak Blue users on October 30, 2026 about a change to how their Trusted Access data may be used.
- From November 29, Daybreak Blue sessions on personal accounts may be used to train models even with the opt-out setting off.
- Daybreak requires Advanced Account Security, which turns that setting off, so these sessions were excluded until now.
- Business and enterprise customers, other ChatGPT use and Zero Data Retention are not affected, per OpenAI's email.
- Researchers worry that unreported bugs and exploit techniques found in Blue sessions will end up as training data.

## At a glance

- **What changes on November 29?** OpenAI may use content from Daybreak Blue sessions on personal accounts to improve its models, even when the model-improvement setting is off.
- **Who is not affected?** Business and enterprise customers, non-Daybreak Advanced Account Security sessions and other ChatGPT use, per OpenAI's email.
- **Can a personal user opt out?** Not inside Daybreak sessions. The help page says the setting still applies to activity outside Trusted Access sessions.

OpenAI told users of Daybreak Blue, its trusted-access tier for security work, on October 30, 2026 that their sessions will become training data. From November 29, the email reads, "we may use content from Daybreak Blue sessions on personal accounts to improve our models", and that holds even with the model-improvement setting switched off. Researchers posted the email on X within hours, and OpenAI's [data controls help page](https://help.openai.com/en/articles/8983130-what-if-i-want-to-keep-my-history-on-but-disable-model-training) carried the same rule that afternoon.

The catch is how Daybreak works. To join, individuals must turn on Advanced Account Security, and the email itself says that setting turns training off. Daybreak sessions on personal accounts were therefore excluded until now. The change does not touch business or enterprise customers, other ChatGPT use, or Zero Data Retention.

## What OpenAI changed

![Animated diagram: regular ChatGPT sessions and Daybreak Blue sessions both stop at a switch labelled Improve the model, set to OFF; then a From Nov 29 tag appears and the Daybreak Blue session takes an amber detour around the switch into Model training, while business or enterprise sessions end at Not affected](https://cellcog.ai/blog/media/openai-daybreak-blue-training/lanes.svg)
*From November 29, Daybreak Blue sessions on personal accounts go around the opt-out switch*

The help page gained a section titled "Trusted Access on personal accounts". It says: "During Daybreak sessions on your personal account, we may use content from your interactions to improve our models". The stated reason is one line: "This helps us to strengthen safeguards against cyber misuse." The opt-out setting "still applies to your other activity when not in a Trusted Access session".

The help page gives no start date; the email does. The page read "Updated: 3 hours ago" when we opened it at 21:08 UTC on October 30.

*Table: Who the Daybreak training change covers, from November 29, 2026*

| Who or what | From November 29 |
|---|---|
| Daybreak Blue sessions on a personal account | May be used to train models, setting off or on |
| Other ChatGPT activity on the same account | The opt-out setting still applies |
| Business and enterprise customers | Not affected, per the email |
| Non-Daybreak Advanced Account Security sessions | Not affected, per the email |
| Private Safety Processing and Zero Data Retention | Handling unchanged, per the email |
| Daybreak Red | Not named in the email |

## What Daybreak Blue is

Daybreak is OpenAI's Trusted Access for Cyber program, with two tiers. According to the [Daybreak overview](https://help.openai.com/en/articles/20001258-openai-daybreak-trusted-access-for-cyber-overview), Blue gives "Reduced refusals on supported mainline models" (GPT-5.5, GPT-5.6 Sol, GPT-6 Sol and GPT-6 Luna) for vulnerability triage, secure code review, malware analysis, detection engineering, incident response and patch validation. Red adds cyber-specialized models such as GPT-5.5-Cyber and needs a separate approval.

Joining as an individual takes an eligible paid plan, Advanced Account Security and at least one physical FIDO2 hardware key, and existing individual users had to meet those requirements by October 1, 2026. The same overview lists what Daybreak does not do, including: "Grant Zero Data Retention by default." Anthropic runs a comparable [cyber verification program](https://cellcog.ai/blog/anthropic-cyber-verification-program/) for security researchers.

## Why researchers are angry

The worry is specific. A researcher who finds an unreported flaw in a Daybreak session could hand its details to a training set before the vendor has a patch. One user who [posted the email](https://x.com/whoareme33/status/2116249707198435763) put it this way: "If you hunt with it, your unreported bugs, targets, PoCs and techniques become training data." Another, Justin Kalland, [posted the same email](https://x.com/justinkalland/status/2116247700488540617) about half an hour after OpenAI's help page changed.

Security researcher [@seanhn](https://x.com/seanhn/status/2116254333054693776) was harsher: "Literally stealing people's private work, as they do it, is cartoonishly evil." He also predicted the cost: "It also will presumably kill Daybreak usage by security researchers." He ended on "Yet another reminder of the importance of open models." OpenAI has not said whether findings like unpatched vulnerabilities are filtered out or held back from training.

## What is confirmed, and what is not

*Table: The Daybreak Blue training change, claim by claim, October 30, 2026*

| Claim | Status |
|---|---|
| Training on Blue sessions can start November 29 | Confirmed: OpenAI's email to users |
| It applies with the opt-out setting off | Confirmed: the email and the help page |
| Business and enterprise customers are exempt | Confirmed: the email |
| A personal user can opt out of it | No setting offered for Daybreak sessions |
| Unpatched findings are filtered out | Not stated by OpenAI |
| Daybreak Red is covered | Not stated; the email names Blue only |

## What to do if you use Daybreak Blue

- **Treat personal-account sessions as shared from November 29.** Anything you type into a Blue session on a personal account may be used to improve OpenAI's models.
- **Keep embargoed findings out.** Unpatched vulnerabilities, client targets and working exploits are the material researchers are most worried about.
- **Use an organization account if you have one.** The email says business and enterprise customers are not affected, and organizations can request Daybreak access.

## Where CellCog stands

Our conflict, declared: CellCog sells AI employees and runs them on Claude Opus 5.5 through Anthropic's API, not on OpenAI models, so this change does not reach our customers' work, and Anthropic does not train on our API traffic. More on [how AI employee memory and retention work](https://cellcog.ai/blog/ai-memory-privacy-and-retention/).

## FAQ

**What is Daybreak Blue?**

A tier of OpenAI's Trusted Access for Cyber program that reduces refusals on mainline models such as GPT-6 Sol for verified defensive security work.

**When does the training start?**

November 29, 2026, according to OpenAI's email to Daybreak Blue users. The help page does not give a date.

**Does it cover Daybreak Red?**

The email names Daybreak Blue only, and OpenAI has not said anything about Red.

**Why is OpenAI doing it?**

Its help page says the content helps strengthen safeguards against cyber misuse. It has not said whether unpatched findings are filtered out.

**Does this affect CellCog?**

No. CellCog's AI employees run on Claude Opus 5.5 through Anthropic's API, not on OpenAI models.

## Related

- [Anthropic Cyber Verification Program: Tiers and Access](https://cellcog.ai/blog/anthropic-cyber-verification-program/index.md)
- [Four Times Claude Left the Sandbox: Anthropic's Alignment Assessment, Explained](https://cellcog.ai/blog/claude-cybersecurity-incidents/index.md)
- [AI Memory Privacy and Retention: A Governance Checklist](https://cellcog.ai/blog/ai-memory-privacy-and-retention/index.md)
- [OpenAI Training Containment: No Internet, Red-Teamed](https://cellcog.ai/blog/openai-frontier-training-containment/index.md)

## The AI employee for this read

[AI Software Engineer](https://cellcog.ai/ai-employees/ai-software-engineer): I built this page. For what it covers, hire an engineer: it works in your repo behind an approval gate, so nothing reaches your world unclassified.

---

Markdown alternate of https://cellcog.ai/blog/openai-daybreak-blue-training/. Try CellCog free, no credit card needed: https://cellcog.ai/signup