OpenAI introduces Private Safety Processing
On August 19, OpenAI released a preview of a system that recognizes abuse patterns across several linked sessions without retaining user content. The idea is that only a narrowly defined safety signal is passed on, without exposing the prompts and responses themselves, which keeps the zero data retention guarantee for paid API customers in force. The target is attackers who split a request across several conversations to avoid detection. The approach is the opposite of Anthropic's policy, which keeps data for 30 days with controlled human review; if you are choosing a vendor for a project with sensitive client data, that difference is worth understanding before you sign. Wider rollout and a technical paper were announced for September.
On August 19, OpenAI released a preview of a system that recognizes abuse patterns across several linked sessions without retaining user content.
What it solves
Attackers split a request across several separate conversations to avoid detection, so each part looks harmless on its own. Catching that means someone has to observe several conversations together, which collides directly with the promise that content is not kept.
How the two are reconciled
The system passes on only a narrowly defined safety signal, without exposing the prompts and responses themselves. The zero data retention guarantee for paid API customers stays in force.
Why it concerns contractors
If you are choosing a vendor for a project with sensitive client data, the retention policy is a line the contract has to reflect. Anthropic keeps data for 30 days with controlled human review, while OpenAI puts non-retention forward as an advantage. Neither is better in itself; it depends on what the client asks you to sign.
What is still coming
Wider rollout and a technical paper were announced for September. Until then this is an announcement, not proof.
Sources
Related
How to label AI content under Article 50, and which part of it is not your job
Article 50 of the EU AI Act has applied since August 2, 2026, and it binds anyone serving people in the Union, wherever the server is. Most of the panic is about the machine-readable marking requirement, which for a site owner who calls somebody else's API is somebody else's obligation. Here is what is actually yours: a chatbot that says what it is, published text that either carries a name or carries a label, and a deepfake that admits it.
Evropska komisijaverified
Pew puts a number on it: 35% of pages published after ChatGPT show AI authorship
Pew Research ran nearly half a million pages from Common Crawl through a detector. Among pages published after November 2022, more than a third came back with significant signs of AI writing, and .com domains showed it at ten times the rate of .edu and .gov.
TechCrunchverified
Gemma passes a billion downloads and 100,000 derived models
On August 20, Google announced that the Gemma family of open models has passed a billion downloads. In two years the community has published more than 100,000 derived models, and the most recent Kaggle competition drew more than 1,600 entries. An Awesome Gemma repository launched with the announcement, meant as an index of vetted projects, fine-tuned models, tutorials, and tools. The figure matters to someone building sites too, because a model you run on your own server stops being exotic, which makes text processing without sending data to a third party workable.
Googleverified