Thanks to visit codestin.com
Credit goes to docs.context.dev

Skip to main content
Zero data retention (ZDR) is an opt-in mode on selected Context.dev endpoints. When you set zdr=enabled on a request:
  • Shared caches are bypassed end-to-end for that request.
  • Usage logs record operational metadata only, with no request body, response body, query values, user-agent, or tags.
  • Uploaded bytes (parse) and captured screenshots are handled in memory and are never staged in shared object storage.
  • The response carries X-Context-ZDR: true so you can confirm ZDR was honored.
Use it when your workflow requires these retention controls, such as when processing customer-uploaded documents. Review the data processing terms for requirements beyond this per-request setting.
Zero data retention is a per-organization entitlement. Contact [email protected] to have it enabled on your account before sending ZDR requests.

Supported endpoints

ZDR is only accepted on the endpoints below. Every other endpoint rejects the parameter with ZDR_NOT_SUPPORTED. Sending zdr in the wrong location (for example, in the crawl query string or a scrape body) returns 400 INPUT_VALIDATION_ERROR.

Enable ZDR on a request

zdr accepts two values: enabled and disabled. Any other value returns 400 INPUT_VALIDATION_ERROR. Omitting the parameter is equivalent to disabled and behaves exactly like a normal request.

Query-parameter endpoints

The PHP Parse example uses the SDK’s low-level request to send raw file bytes. The Go example passes query options explicitly because SDK 2.14.0 does not forward Parse parameters.

Body-parameter endpoint (crawl)

Confirm ZDR was honored

Successful ZDR responses include the CORS-exposed response header:
If the header is missing, do not treat the response as confirmation of ZDR. Check the request parameter and status; the request may have used standard mode or failed before ZDR took effect.

Trade-offs

Because ZDR skips shared caches and richer processing paths, expect:
  • No shared cache reuse. Repeated ZDR requests cannot reuse a shared cached result, so they may take longer than standard requests.
  • No search-assisted sitemap discovery. GET /v1/web/scrape/sitemap under ZDR relies on direct crawling only.
  • No usage tags. Request tags are dropped from usage logs. Track ZDR usage in your own systems if you need per-workload attribution.
Pricing and rate limits are unchanged.

Errors

Request tags

Understand usage attribution and why tags are dropped under ZDR.

Rate limits

Pace ZDR requests within the standard rate limits.