OpenAI previews a way to catch AI misuse without giving up on zero data retention

Started by BlueFalcon, Aug 21, 2026, 11:21 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Topic: OpenAI previews a way to catch AI misuse without giving up on zero data retention   Views(Read 61 times)

BlueFalcon

OpenAI announced this week that it is testing a new system called Private Safety Processing with a small set of early customers including Microsoft and Databricks, aimed at closing a gap in its existing zero data retention protections. Under standard zero data retention, or ZDR, OpenAI does not keep customer prompts or model responses after a request finishes processing, and its own staff cannot pull that content up for review even if they wanted to, which is a meaningful privacy commitment for enterprise customers handling sensitive material.

The problem OpenAI is trying to solve is that existing ZDR compatible safety systems evaluate each interaction individually, in isolation from everything else that customer has done. As models take on longer, more autonomous, multi step tasks, some of the more serious risk signals only become visible when you look across a whole sequence of related interactions rather than any single one of them in isolation. A bad actor trying to piece together, say, working malware code could deliberately spread that work across several separate sessions specifically to dodge single interaction detection systems, and Private Safety Processing is meant to catch exactly that kind of pattern without OpenAI staff ever seeing the underlying prompts or responses directly.

The mechanics work through what OpenAI describes as narrowly defined signals. When the automated system flags something suspicious, OpenAI receives only a limited signal describing the general type of activity involved rather than the actual conversation content itself, and the company then decides based on that signal alone whether some kind of enforcement action is warranted. If it decides action is needed, OpenAI can request additional context from the customer directly, and the customer retains full discretion over whether to share that context or not, at least according to how the company has described the process publicly so far.

The timing here is not remotely a coincidence, since Anthropic recently instituted a mandatory 30 day data retention policy specifically for its most capable models, arguing that retention is genuinely essential for catching sophisticated attacks that unfold gradually across multiple separate requests rather than any single one. Anthropic has been notably candid that this stricter policy will be unpopular with customers who have grown accustomed to expecting zero retention as the default, and that it expects real business risk from the move, particularly if competitors do not follow suit with something similar of their own.

OpenAI is essentially betting the opposite way, that automated cross session pattern detection can deliver equivalent safety guarantees without ever requiring the retention tradeoff at all. Whether that technical bet actually pans out in practice, especially against genuinely sophisticated and determined bad actors specifically trying to game a system they know is watching for patterns rather than content, is not something anyone outside these two companies can properly evaluate yet, since OpenAI has not published the technical whitepaper it says is coming sometime in September.


Carol84

Anthropic going one direction and OpenAI going the opposite direction on the exact same underlying problem is a fascinating natural experiment for the industry to be running right now. In a year or two we will actually have real evidence about which approach caught more real attacks and which one enterprise customers ultimately preferred in practice.

NightHarbour30

The malware example they used is doing a lot of work in this announcement and for good reason honestly, since it is concrete and legible in a way abstract talk about risk patterns never quite manages to be. Spreading harmful requests across sessions specifically to dodge single interaction detection is a real and well documented adversarial pattern, not some hypothetical dreamed up for a press release.

James90

Competing on trust architecture instead of raw model capability feels like a new and honestly overdue phase for this industry to be entering. For a long while every single announcement out of every lab was purely about benchmark scores, and now we are finally starting to see real competition over how these systems actually get operated responsibly in production.

Whether that shift in competitive framing sticks around once the next big capability jump lands and dominates headlines again remains to be seen though.

Scholes

Zero retention plus pattern detection without content access sounds almost too good to be true on paper, and until the technical whitepaper actually drops in September I am reserving real judgment either way. There has to be some meaningful tradeoff hiding somewhere in how this system actually works, these things rarely come completely free.
Some call it obsession, I call it fine tuning

Postie

Enterprise customers are absolutely going to be the ones who decide who wins this particular fight, not individual developers or hobbyists tinkering on personal projects. Whichever approach ends up satisfying corporate security and legal teams while still catching genuine bad actors reliably is going to shape which lab ends up with the bigger enterprise contracts over the next couple of years.
Entangled with my ex, deployment & my sanity

Hidden Sookie

As someone who runs API integrations for a living, I genuinely like that customers keep full discretion over whether to share additional context after being flagged rather than OpenAI being able to just seize it unilaterally. That is a meaningfully different power balance from what a lot of platforms default to, and it is worth acknowledging even while staying skeptical about the rest.

Nadir Wolfhound

Narrowly defined signal is doing enormous, load bearing work in that description and it deserves more scrutiny than it is getting right now. What exactly counts as narrow here in practice, and who decides where that line actually sits when a borderline case comes up in the real world rather than a tidy example.

Related Topics (5)

Browser ID: smf (possibly_robot, is_webkit)
Templates: 6: index (default), RelatedTopics (default), Block (default), Optimus (default), Display (default), GenericControls (default).
Sub templates: 14: init, html_above, Blockheaders_above, body_above, Blockindex_above, footer_counters_above, related_topics_bot_above, main, related_topics_bot_below, footer_counters_below, Blockindex_below, body_below, Blockheaders_below, html_below.
Language files: 11: index+Modifications.english (default), Turnstile.english (default), RelatedTopics.english (default), Block.english (default), Optimus/Optimus.english (default), Post.english (default), Editor.english (default), Drafts.english (default), giphy.english (default), QRCode.english (default), klipy.english (default).
Style sheets: 7: index.css, attachments.css, turnstile.css, ajaxsearchlite.css, jquery.sceditor.css, show_password.css, responsive.css.
Hooks called: 294 (show)
Instances created: 14 (show)
Files included: 138 - 1846KB. (show)
Memory used: 11078KB.
Tokens: post-login.
Cache hits: 25: 0.00380s for 50,919 bytes (show)
Cache misses: 5: (show)
Queries used: 26.

[Show Queries]