How Tinplate handles requests, telemetry, and edge caching.
Tinplate APIs process request payloads strictly in volatile memory on Cloudflare Workers. We never log, store, inspect, sell, or retain your request bodies, response bodies, signing secrets, PII, HTML, emails, or tokens.
To monitor uptime, latency, and quota abuse, the gateway records only non-content operational metrics:
10_JSON_HEAL) and HTTP method.rapid, zyla) and subscription tier name.le_4kb), HTTP status code, and server processing time (ms).No IP addresses, headers, API keys, or payload fragments are written to telemetry or logs.
/v1/eu-vat-iban/vat) and public HTML-to-Markdown conversions by URL hash (/v1/html-to-markdown) may be cached briefly in Cloudflare KV to reduce upstream latency. Raw HTML inputs and private secrets are never cached."use_ai_judge": true on /v1/prompt-guard or /v1/hallucination-diff, the text excerpt is evaluated statelessly via Cloudflare Workers AI with no training retention.