Data processing under ZDR
- Prompts: Used only for the current inference request and deleted after the response is returned.
- Model responses: Deleted after they are returned and not retained.
- Model training: Enterprise customer data is not used to train models.
By default, the Kimi Open Platform does not use enterprise customer data to train models. ZDR further extends this protection by eliminating content retention.
Security
ZDR changes only how content is retained; it does not change the platform’s usage policies. Automated safeguards, including content safety reviews, continue to apply to all traffic. If we identify abusive behavior, we may take action under our usage policies, including terminating ZDR service.Who can enable ZDR?
ZDR is available on request to enterprise customers. If your business handles sensitive data or operates in an industry with data-retention requirements, contact our sales team to request an evaluation.Frequently asked questions
Does ZDR change how I use the API?
No. ZDR is a server-side data-processing policy. The API, parameters, and billing remain unchanged.Can I still troubleshoot issues with ZDR enabled?
The platform does not retain request content, so we cannot trace the content of an individual request after the fact. Retain request logs in your own systems for troubleshooting.Does ZDR apply to all data types?
No. Please note the following exceptions:- Batch Job service: The Batch API does not support ZDR for batch jobs.
- Directly uploaded images and videos: ZDR cannot be guaranteed for images or videos submitted directly through the File Upload API.
- Operational data: Operational data, such as security logs and billing records, is outside the scope of zero data retention.
- Third-party services: Data processed by third-party models, connectors, or plugins is not covered by this ZDR policy.