Privacy & security
Provider data policies
What each provider endpoint declares about data collection, retention and location, where to read it, and how to route only to endpoints that meet your requirements.
Every provider endpoint declares how it handles the requests it serves: whether it collects data, how long it retains it, and where it processes requests. You can read these declarations before you send traffic and filter on them per request, so a request that must not be retained never reaches an endpoint that says it keeps data.
What an endpoint declares
| Declaration | Values | Meaning |
|---|---|---|
| Data collection | Collects data, no data collection, or undeclared | Whether the provider collects request data, for example for training |
| Retention | none, limited, indefinite, unknown | How long the provider keeps request data |
| Maximum retention | A number of days | The upper bound for limited retention |
| Countries | ISO country codes, such as DE | Where the endpoint processes requests |
| Regions | Region identifiers chosen by the provider | Finer-grained or multi-country locations |
An endpoint with retention none is a zero-data-retention (ZDR) endpoint.
Where to read the declarations
Open Compare providers in the dashboard and select a provider. Its Endpoints and data terms section lists each endpoint with its state, how many models it serves and its data terms:
| Badge | Meaning |
|---|---|
| Collects data, No data collection or Collection undeclared | The collection declaration |
| Retention: none, limited, indefinite or unknown | The declared retention, followed by · Nd max when a maximum is declared |
| Country and region badges | The declared locations |
GET /models/{author}/{slug}/endpoints returns each endpoint's tag for provider.only and provider.order, but not its data terms. Use the dashboard to read them, or filter with the preferences below and let routing enforce them.
Filter endpoints per request
Three provider preferences restrict routing by declaration. Each is a hard filter: an endpoint that doesn't satisfy it is never tried, including during fallback.
provider
data_collectionstringDefaultallowdenyexcludes every endpoint that declares it collects data, and every endpoint without a declaration.zdrbooleanDefaultfalsetrueallows only endpoints that declare retentionnone.regionsstring[]Allow only endpoints whose declared countries or regions include at least one of these values. Up to 64 unique values, matched case-insensitively. Each value starts with a letter or digit and may contain letters, digits,
.,_,:and-, up to 64 characters.
curl -X POST "https://api.numes.ai/api/v1/chat/completions" \ -H "Authorization: Bearer $NUMES_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "openai/gpt-6-luna", "messages": [ { "role": "user", "content": "Classify this support ticket." } ], "provider": { "data_collection": "deny", "zdr": true, "regions": [ "DE", "AT", "CH" ] } }'The filters combine with each other and with the rest of the provider object, such as sort, order, only and max_price. regions is an extension to the OpenRouter API, which uses a separate base URL for regional routing. See Provider routing.
When no endpoint qualifies
If no endpoint of the model satisfies every filter, the request fails before any provider is contacted, and nothing is charged:
{ "error": { "code": 503, "message": "no provider is available", "metadata": { "error_type": "provider_unavailable" } }}A request is never relaxed to a less private endpoint. Choose a model with a qualifying endpoint, or loosen a requirement you can live without. Strict filters can also leave fewer and more expensive endpoints, and fewer fallbacks when one is busy.
Review and records
Review. Declarations are reviewed when an endpoint is approved. When a provider changes a serving endpoint's declarations, the change is reviewed while the previously approved terms keep serving.
Routing. Filters remove endpoints first. Default routing,
sort,orderand fallback then use only what remains.Recorded location. For each request, the platform records the regions you asked for and, when known, where the request was served. Both appear as dimensions in Activity.
Misrepresenting a model, its capabilities, its usage or its data handling leads to suspension and to withholding or reversal of earnings.
Endpoint declarations cover what the provider does. For what Numes itself records, see Data retention and logging.