Skip to content

Data retention

Understand how Engy handles request content, and require zero data retention for a request, an API key, or an account.

This page explains how Engy handles request content and how you require zero data retention. It is intended for developers and account owners who handle sensitive data.

Default behavior

Zero data retention is the default for every account. Engy does not store your prompts or the model outputs.

Requests are served by GPU workers. Some workers are operated by independent providers on the Engy network. To make sure that no worker can retain request content, require zero data retention end to end.

Require zero data retention

Set provider.zdr to true to restrict a request to ZDR-certified workers. ZDR-certified workers either use confidential computing, which keeps request content sealed from the operator, or are operated by Engy without request logging.

curl https://api.engy.ai/v1/chat/completions \
  -H "Authorization: Bearer $ENGY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "kimi-k3",
    "provider": {"zdr": true},
    "messages": [{"role": "user", "content": "Hello"}]
  }'

If no ZDR-certified worker is available for the model, the request fails with HTTP status 503. Engy does not send the request to any other worker. Models that support zero data retention are marked in Models and pricing.

Require zero data retention for a key or an account

If your client cannot add fields to each request, Engy can require zero data retention for an API key or for your whole account. To request this, email [email protected] from the address on your account. Every request from that key or account is then handled as if it set provider.zdr to true.

Supported endpoints

The provider object works on /v1/chat/completions, /v1/completions, /v1/messages, and /v1/responses. Engy removes it before the request reaches the model.