Current documentation describes customer-side encrypted retention, protected automated review and setup for ZDR-approved organizations.
OpenAI previews Private Safety Processing with zero data retention
2026-08-18Verified announcementWATCH
OpenAI began a phased rollout of Private Safety Processing for approved API customers on September 22. Selected prompts and responses remain encrypted in customer-controlled AWS S3, Azure Blob or Google Cloud Storage and are reviewed automatically inside a protected runtime without human access. Official setup guides now cover all three clouds.
Official · DocumentationOpenAI · ZDR with Private Safety ProcessingOfficial · DocumentationOpenAI API data controls
Availability: Phased rollout began 2026-09-22 for approved API customers
What this means for you
Enterprise teams can now evaluate a concrete deployment path instead of a preview. ZDR still does not mean that content is stored nowhere: teams must assess customer-side retention, keys and cloud permissions. Keep WATCH until access is approved and an end-to-end deployment is independently validated.
Evidence & related material
OpenAI's data-controls documentation confirms PSP began phased rollout on September 22, while the Private Safety Processing guide documents customer storage setup for AWS, Azure and Google Cloud.
Subsequent changes
A scheduled review corrects PSP data handling and availability. Current documentation describes customer-side encrypted retention, protected automated review and setup for ZDR-approved organizations.
Earlier coverage said content was never stored or read and access was pilot-only. → Current documentation describes customer-side encrypted retention, protected automated review and setup for ZDR-approved organizations.
Private Safety Processing begins phased rollout with setup guides for three clouds
Technical details & scores
| Availability | Phased rollout began 2026-09-22 for approved API customers |
|---|---|
| Cloud Setup | AWS S3, Azure Blob Storage and Google Cloud Storage |
| Content Handling | Customer-controlled encrypted retention, up to 30 days, with protected automated review and no human access |
| Reviewed On | 2026-10-05 |
| Independent Validation | ✗ |
Technical impact 2
Engineering value 3
Adoption signal 3
Maturity 2
Verification cost 2
Risk 2