What Deepslate stores
By default, Deepslate stores call data so you can review and analyze your calls in the Deepslate platform, for example to check transcripts, debug a conversation, or improve your system prompt. The table lists every data category, whether it is stored by default, whether you can turn storage off, and whether it is stored with Zero Data Retention.
Deepslate needs the data that is also stored with ZDR to bill you, monitor performance, and prevent abuse. It stores all other data so you can review your calls in the platform.
Abuse screening
Deepslate automatically screens your system prompts for violations of our usage policies. A flagged prompt is kept until it has been reviewed. If the flag turns out to be wrong, the prompt is deleted. If a violation is confirmed, the prompt is retained. Abuse screening also applies to sessions with ZDR.Model training
Your data is not used for model training without your consent. Deepslate does not train its models on your call data unless you have explicitly agreed to it.Deletion
To have stored call data deleted, contact us at support@deepslate.eu. When your contract ends, your data is deleted in accordance with your Data Processing Agreement (DPA).Zero Data Retention
Zero Data Retention is designed for workloads with especially sensitive data, for example in insurance, banking, or healthcare. With ZDR enabled, audio, transcripts, chat history, system prompts, and tool call content are processed exclusively in volatile memory, only for as long as needed to run the session in real time, and are never persisted by Deepslate. The one exception is a system prompt that is flagged by abuse screening: it is kept until it has been reviewed, and retained if a violation is confirmed.Availability
Zero Data Retention is an Enterprise feature and applies to the Realtime API only.Data stored with ZDR
To operate and bill the service, Deepslate keeps only the data marked Yes in the Stored with ZDR column of the table above. This data contains no audio, transcripts, or chat history. It is limited to technical values such as timestamps, durations (including audio duration), generation times, and IDs, plus system prompts flagged by abuse screening.Limitations
- Limited support and debugging. Because Deepslate does not have the conversation content of ZDR sessions, we cannot inspect them when you report an issue. Troubleshooting is limited to the technical telemetry that is stored with ZDR. To help us debug, include the session ID and a description of what happened.
- No call review in the platform. ZDR sessions do not show transcripts, chat history, or recordings in the Deepslate platform. Tool calls appear with a generic label instead of the tool name.
Keeping your own records
If you need a record of the conversation, store it on your side. Your client can request the full conversation at any time during the session withExportChatHistoryRequest. The SDKs and plugins expose the same capability as chat history export.