Who runs this, where it runs, and what happens to your request.
Most providers put this page behind a compliance link. It is a selling point here: we publish the operating entity, the published processing scope, who touches a request, and what survives it.
There is a company behind the endpoint.
A contract with an API is a contract with whoever operates it. This is that legal entity, its jurisdiction, and the address a subpoena or a data-subject request would go to.
You can see where your own request ran.
The fleet changes, so this page does not publish an inventory of it. It publishes the part that is about you: which regions a request passes through, who operates them, and where your specific call ran.
rendered from the same register the DPA is built from · one country today · the global edge is transit and hosting, not model execution
The request path includes a qualified edge hop.
Inferway self-hosted inference keeps prompt and completion content transient in memory. Cloudflare may process decrypted content at TLS termination, depending on the deployed zone and edge configuration.
TLS from your machine to the edge.
Cloudflare may process decrypted content at TLS termination, depending on the deployed zone and edge configuration.
Key checked, limits applied, metadata recorded.
Prompt and completion content is transient in memory during Inferway self-hosted inference.
Response returned; Inferway does not persist request content.
Two categories, two different promises.
aligned with the Privacy Policy and DPAFor Inferway self-hosted inference, prompt and completion content is transient in memory and is not persisted by Inferway.
Metadata examples include token counts, timestamp, latency, model, endpoint/status/channel, and billing or abuse identifiers. The policy ceiling is up to 90 days.
Everyone who touches a request, and what they touch.
The tag on each row is the thing worth knowing: whether that party can see request content, or only metadata about it.
Per-vendor locations, retention authority and the sub-processor terms are in the DPA. Adding a party to this list requires a DPA revision, and existing customers are notified before it takes effect.
What we can prove, and what we cannot yet.
Monitoring has not started yet, so two of these three are empty. They stay empty until there is something real to put in them.
Recording begins when the service goes live. Until then there is no history, and we do not paint a green one.
Status pageNo performance number is published before it is measured on the current model. When the runs are done, each figure will state the hardware class, concurrency, prompt and output shape, and timestamp.
ReportsRecording begins when the service goes live. Until then there is no history, and we do not paint a green one.
Status pageThis page is a plain-language summary. Every claim on it is meant to be a weaker or equal statement of what the legal documents say — if you find a place where this page promises more than they do, that is a defect and we want to hear about it.