Measure delivery without building identity profiles.

Search queries

Discovery search and explore accept bounded JSON POST bodies. Query text is processed in memory and is not persisted, logged, hashed, copied into response errors, or written to custom telemetry. Only a fixed operation and result-count bucket may be measured.

Custom catalog telemetry

At most one compact event may be written for an in-scope request. It contains a UTC hour bucket, event kind, normalized route, method, status class, content type, release ID, artifact kind, validated record ID, controlled requester class, and operator only when classified from an approved platform signal.

What custom telemetry excludes

IntentRoute does not place IP addresses, cookies, fingerprints, authorization headers, prompts, free text, arbitrary query values, query hashes, referrers, full user agents, provider credentials, or personal identifiers in the custom catalog dataset. It does not read an IP address to construct a custom rate-limit key.

Retention and interpretation

Custom aggregate events and accepted receipt categories are retained for up to three months. Missing credentials, an unavailable binding, expired retention, or a query failure means unknown data—not zero traffic. A request proves delivery only; it does not prove that an AI read or benefited from the record.

Outcome and correction receipts

Optional endpoints accept enumerated values only, without authentication or individual reply. They may be biased or abusive and never change a record automatically. Accepted syntax is retained as aggregate telemetry for up to three months.

Cloudflare platform processing

Cloudflare processes ordinary network and request metadata to host, protect, rate-limit, and observe the Worker under the applicable account plan. Existing Workers observability is separate from the privacy-minimized custom catalog dataset.