Lu xew
OpenAI introduced Private Intelligence, an umbrella that expands its (ZDR) program with Private Safety Processing (PSP) now available and a preview of Private slated for later this year.
At OpenAI’s DevDay 2026, the company announced a two‑part initiative called Private Intelligence. The first part, with Private Safety Processing (ZDR + PSP), builds on OpenAI’s existing ZDR policy that excludes customer prompts and responses from abuse‑monitoring logs. PSP adds an encrypted storage layer where selected content is kept in a customer‑controlled bucket (AWS S3, Azure Blob, or Google Cloud Storage) for up to 30 days, allowing an automated, hardware‑attested safety runtime to review the data without human inspection.
OpenAI says the safety runtime can only emit predefined safety signals and encrypted results, preventing its personnel from seeing raw customer content. The encrypted records are not used for model training or shared with other OpenAI groups, and the company retains only metadata indexes.
The second component, Private , was presented as a preview. OpenAI described it as a confidential‑computing solution that will provide verifiable controls during inference, but detailed technical specifications, supported models, and pricing were not disclosed. The rollout is planned for the fall of 2026.
Ay leeral ci cosaan: venturebeat.com ↗
Lu tax mu am solo
The rollout gives enterprise customers a technical guarantee that sensitive prompts and model outputs are not visible to OpenAI staff and are not used for training, addressing growing concerns over data leakage and intellectual‑property exposure as AI models become more capable.
Enterprise AI adopters have increasingly demanded stronger guarantees that proprietary code, research data, or confidential documents cannot be accessed by AI providers or inadvertently incorporated into future models. Private Safety Processing translates OpenAI’s policy promises into a concrete architecture, reducing reliance on contractual language alone.
The feature addresses recent reports that companies such as Palantir, Nvidia, and Booz Allen Hamilton are restricting model use over data‑privacy concerns, and it counters the “snoop‑and‑scoop” worries highlighted by the Navier‑Stokes controversy. By keeping encrypted data in customer‑controlled storage and limiting human access, OpenAI aims to differentiate its enterprise offering from competitors that rely on less transparent data‑handling practices.
If widely adopted, Private Intelligence could set a new baseline for privacy‑by‑design in AI services, influencing industry standards and potentially prompting regulators to expect similar technical safeguards from other AI providers.
Mekanism buy weccoo xalaat: naka lay doxee
Saytu xarala yu bees yi ci ginaaw yokkute bii ci anam wu weccoo xalaat.
Why can ethical evaluation not be reduced to one model score?
Li nga wara seetaan ci topp
How OpenAI will implement Private , which models it will support, pricing, and whether customers can independently verify the confidential‑computing environment.
The specific hardware trusted‑execution environment OpenAI will use for Private and whether it will be compatible with existing ChatGPT Enterprise or API workloads.
Which model families (e.g., GPT‑4, GPT‑4‑Turbo) will support the Private service and whether the feature will be optional or mandatory for certain enterprise contracts.
Pricing and billing structures for the encrypted storage and safety‑runtime components, which OpenAI has not disclosed.
Independent verification mechanisms that customers can employ to attest that OpenAI’s runtime does not expose their data, and any third‑party audits that may be conducted.