OpenAI Extends Zero Data Retention to Frontier Models with Private Safety Processing
Eligible API customers keep control of content while automated systems look for cross-interaction risk patterns and return limited safety signals.
Key takeaways
OpenAI announced Private Safety Processing on August 19, 2026 to keep frontier-model safety monitoring compatible with Zero Data Retention for eligible API customers. Under the preview, customer content can remain on customer-controlled infrastructure, while automated systems analyze related interactions and return narrowly defined risk signals without giving OpenAI personnel the underlying prompts or responses. OpenAI is also developing hosted storage encrypted with customer-controlled keys. This is not an automatic setting for every API account. Teams should confirm organization and project eligibility, separate request content from administrative audit logs and other data surfaces, document legal or safety exceptions, and test the configuration with non-sensitive samples before sending regulated or confidential workloads.
Direct answer
This is not automatic ZDR for every API account. It is a preview designed to make cross-interaction safety checks compatible with ZDR for eligible customers.
Fact sources
OpenAI published the preview on August 19, 2026.
Automated systems may return limited risk signals without exposing underlying customer content to OpenAI personnel.
A September rollout and technical white paper are planned, while legal exceptions such as apparent CSAM reporting remain.
Six checks before a sensitive API workflow goes live
- Confirm organization and project eligibility.
- Map retention for every data surface.
- Verify storage and key ownership.
- Keep customer-side audit and incident records.
- Document legal and safety exceptions.
- Test with non-sensitive samples and obtain approval.
Why it matters
Long agent tasks can reveal risk across several interactions. ZDR addresses content control, but it does not replace access control, customer audit logs, incident response, or legal review.
Impact for ordinary AI users
Developers should treat ZDR as a verified organization-level control, not infer it from a product announcement. Sensitive traffic should wait until the exact project configuration is evidenced.
Related tools and tutorials
Start with one reversible task, verify version, permissions, cost, logs, and accepted output, then record the result in a team checklist.
AI software and tools · AI account and cost services · AI skill tutorials · AI frontier news
FAQ
Does every API account get ZDR automatically?
No. OpenAI describes eligible API customers.
Can OpenAI personnel read flagged prompts?
The preview says personnel receive limited signals, not underlying content.
Does ZDR remove administrative audit logs?
No. Platform audit logs are separate administrative metadata.
Source links
- OpenAI: Offering Zero Data Retention for frontier models (2026-08-19)
- OpenAI: Security and privacy
- OpenAI Help: Sharing feedback, evals, and API data
- OpenAI Help: Admin and Audit Logs API
What this means for everyday users
Record organization, project, ZDR evidence, data types, storage, key control, legal exceptions, audit logs, alert ownership, and review date.
Related reading
GitHub Copilot Metrics Add OpenCode and Other Clients: Requests Are Not Prompts
GitHub added totals_by_client to the Copilot usage metrics API on October 23, 2026. Enterprise and organization reports can now show model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, GitHub apps, cloud agents, code review, VS Code, JetBrains, and other clients. This article helps administrators build reliable one-day and 28-day reports without confusing model calls with user prompts. It explains request, session, token, model, and selection-mode fields; separates client traffic from agent-app jobs; and adds checks for unknown identifiers, empty arrays, permissions, and coverage. The result is a governance trend report, not an exact invoice or individual productivity score.
Bayer Shares Production Lessons From 22 Specialist Agents: HTTP Success Is Not Task Success
AWS published Bayer Crop Science’s Agentic Decision Engine case study on October 23, 2026. The production system runs 22 specialist agents over governed analytics workflows, models, logs, and visualization tools. This article turns the architecture into five reusable acceptance checks for enterprise agent teams: persist the state needed to resume work, define identity and authorization at every boundary, scope each agent’s tool catalog, distinguish transport success from task success, and release to a gated group before broader access. It also explains why Bayer’s adoption and resolution figures are evidence about one implementation, not promises for another organization. The focus is operational proof, least privilege, rollback, and observable outcomes rather than prompt polish.
GitHub Copilot in Teams Turns Notifications Into Pull Requests: What to Check Before Review
GitHub updated its Microsoft Teams app on October 23, 2026, so an issue notification in a channel, group chat, or private chat can become a Copilot task that investigates the problem, proposes a fix, and opens a pull request. This article helps development and product teams adopt the workflow without mistaking an automated pull request for shipped code. It explains the consolidated app, repository connection, the November 16 retirement of the legacy GitHub app, and the review boundary. A practical acceptance checklist asks teams to reproduce the issue, inspect changed files, run targeted tests, verify permissions, and keep merge and deployment as explicit human decisions.
IskayPet Connects SharePoint to a Managed Knowledge Base: Validate Permissions Before Answers
AWS published IskayPet’s corporate knowledge assistant case study on October 22, 2026. The system connects Amazon Bedrock Managed Knowledge Bases to existing SharePoint repositories and answers cited questions across retail operations, veterinary care, onboarding, and procurement in four languages and three countries. This article turns the case into a practical acceptance plan for knowledge owners. It checks source scope, inherited permissions, hybrid retrieval, duplicate and fragment removal, citation quality, feedback, and token cost before expansion. It also separates the customer’s reported production results from what another organization should expect. A managed retrieval stack reduces infrastructure work, but it does not remove content ownership, access reviews, evaluation datasets, or human verification of important answers.
Copilot in Visual Studio Adds PR Exploration, a BYOM Migration, and NuGet Fixes
GitHub summarized three September updates for Copilot in Visual Studio 2026 on October 22, 2026. The Git agent can explore an attached pull request and link back to comments and files. Bring Your Own Model remains in preview but now requires the new Agent experience, and previously configured Ollama models must be added again. NuGet Audit warnings can open Copilot Chat with the NuGet MCP server to propose dependency fixes. This article gives .NET developers a cautious upgrade checklist: preserve current settings, validate each feature independently, review package and lock-file changes, run targeted tests and vulnerability scans, and keep a rollback path. Summaries and suggested fixes remain review inputs, not verified outcomes.
Amazon Polly Upgrades Generative Speech: Validate 14 New Voices Without Breaking Existing Apps
Amazon Polly upgraded its Generative engine on October 22, 2026, adding 14 voices across nine locales and making generative Hindi and Finnish generally available. Existing voice names and API calls remain unchanged, so applications do not need a code migration, but generated audio can still change. This article gives creators, course teams, contact-center operators, and accessibility teams a reversible acceptance test. It uses one multilingual script to compare pronunciation, pauses, latency, loudness, and fallback behavior before increasing traffic. It also separates the larger voice catalog from a key limitation: generative voices still do not provide speech marks, so workflows that synchronize captions, highlighting, or animation must keep a compatible engine or another timing source.
Summary
Record eligibility, scope, exceptions, customer logging, and rollback before approving sensitive traffic. ZDR is a control that must be verified, not assumed.