Update on Daybreak Blue data usage and API access

The full message they sent via e-mail:

Hello,

Thank you for using Daybreak Blue and for being part of our Trusted Access program. We are reaching out to notify you of two upcoming changes to Daybreak Blue that may impact you.

Use of Daybreak Trusted Access data

We are changing how your Daybreak Trusted Access data may be used. Daybreak use requires you to enroll in Advanced Account Security (AAS), which turns off the “improve the model for everyone” setting. However, from November 29, we may use content from Daybreak Blue sessions on personal accounts to improve our models, including to help strengthen safeguards against cyber misuse. We will use Daybreak Blue interactions for these purposes, even when the “improve the model for everyone” setting is off.

This change does not impact business or enterprise customers or non-Daybreak Advanced Account Security sessions or other use of ChatGPT. It also does not change our approach to data handling for Private Safety Processing (PSP) or Zero Data Retention (ZDR). You can learn more about data controls in ChatGPT here.

Access to Daybreak Blue via API

As part of our ongoing efforts to ensure Daybreak can only be accessed by approved users, we will no longer offer API access to Daybreak Blue for individuals starting November 20. From this date, the Responses API will return standard responses without reduced cyber refusals. Your API keys will not be revoked. This change does not impact business or enterprise customers.

Daybreak Blue for individuals will continue to be available via Codex using Sign In with ChatGPT (SIWC). If you wish to continue accessing Daybreak Blue via API, please move to a business or enterprise account.

We apologise for any inconveniences these changes may cause to your workflows.

Thank you,

OpenAI