zdr: "enabled".
Supported endpoints
Batches, Monitors, and feedback do not support this request mode. Unsupported routes reject it with
ZDR_NOT_SUPPORTED.
Enable a request
Send this body toPOST /web/scrape. See the Quickstart for authentication and SDK setup.
zdr=enabled. Omitted or disabled uses standard mode. Invalid values, both locations, or the wrong location return 400 INPUT_VALIDATION_ERROR.
Confirm ZDR was honored
Successful supported responses, including Scrape, includeX-Context-ZDR: true. Scrape also returns cache_metadata.status: "zdr" and age_ms: 0. Verify the confirmation before recording that the control was applied.
What changes
Brand retrieval and Styleguide
For Brand retrieval and Styleguide,zdr: "enabled" suppresses application logs, request-log entries, and exported traces. Brand records, shared caches, and hosted assets can still be read and saved. This mode does not make brand data ephemeral. Cloudflare platform invocation logging is unchanged.
Send this body to POST /brand/retrieve:
zdr=enabled to the query string. Both require the organization’s ZDR entitlement and confirm acceptance with X-Context-ZDR: true. Cache metadata can still report hit or miss. These requests do not appear in request-log history. Fresh maxSpeed Brand results skip background refresh and are not saved as shared brand records.
Other supported endpoints
Shared caches and asset uploads are skipped. Retained logs contain operational metadata without request/response bodies, query values, user agent, or tags. Uploaded bytes and screenshots are processed in memory. AI processing uses a dedicated zero-retention configuration.
These requests may take longer without shared cache reuse. Your application remains responsible for its own content storage and logs.
A
403 ZDR_NOT_ENABLED means the organization lacks the entitlement. See security and trust and the DPA for broader data-handling requirements.