Data retention
Inputs and outputs from Chat Completions and Decisions requests are deleted within 60 days of processing. Organizations on zero data retention store nothing.
Other data has no expiry:
- Conversation history. Saved Responses turns
stay stored. Each belongs to the conversation named in the response's
conversation.id; delete that conversation to remove it with every turn in it. - Inline PDFs. A PDF sent as
file_dataon Chat Completions is stored, and the API can't delete it. Withstore: false, SubQ deletes it once the request is processed. Or upload the file and delete it when you're done. - Uploaded files. Files sent to the Files API stay until you delete them.
To keep a turn or request out of storage, see Opting out per request.
Content flagged for a potential violation of the Terms or Usage Policy may be kept while SubQ investigates the violation. SubQ may also keep inputs and outputs longer when the law requires it.
SubQ always records model, token counts, timing, and your
metadata tags for billing and
support. That record never includes prompts or completions.
Zero data retention
Requests work as usual, but nothing is stored afterward. To enable it for your organization, submit a ZDR request.
| Endpoint | Behavior |
|---|---|
| Chat Completions | Works as usual. Nothing is stored. |
| Responses | Works, but turns aren't saved. Send the full context in input on every request instead of previous_response_id. |
| Conversations | Unavailable (403 zero_data_retention). |
| Decisions | Works as usual. Nothing is stored. |
Inline PDFs (file_data) | Rejected (400 document_source_unsupported). Upload the file and pass file_id. |
Opting out per request
To keep a single request out of storage, send store: false on
Chat Completions or
Responses.