Concepts

Data handling

What Seldon stores, what it never does with your data, and the request controls that limit storage and routing.

This summary also appears at the top of the Quickstart. The AI data handling page and the privacy policy are authoritative.

Routing and retention

Seldon routes requests to configured model providers. Seldon retains audit, usage and trace data for billing, audit, reliability, debugging, security and product operation.

No resale or model training

Seldon does not resell prompts, outputs, traces, cached responses or API traffic, and does not use them to train generalized AI models.

Stored payloads and cache

Current behavior may store redacted request and response trace payloads and exact response-cache entries. Functions store their drafts, evaluation examples and execution records as private workspace content. Stored BYOK connections keep encrypted credentials in a dedicated vault. Transient BYOK headers are used for the request and are not stored.

Policy-aware routing

Privacy-forward controls such as provider.zdr, provider.data_collection = "deny" and cache.no_store can be used, but can fail with no_policy_compliant_provider when provider policy metadata is unknown.

AI data handling Security posture Privacy policy Subprocessors

Controls you can set per request

Control	Effect
`provider.zdr: true`	Only zero-data-retention providers may serve the request.
`provider.data_collection: "deny"`	Excludes providers that may use data for training.
`provider.data_residency`	Keeps providers whose regions overlap the listed values.
`cache.no_store: true`	The response is neither read from nor written to the response cache.
No `cache` object	Response caching stays off for the request.

Providers whose policy metadata is unknown are treated as non-compliant, so strict controls can return 422 no_policy_compliant_provider. A workspace may enforce stricter defaults that requests cannot loosen. See Models and routing.

Functions content

Function drafts, evaluation examples, evidence and execution records are private workspace content.

Trace files uploaded for import expire after 24 hours; drafts copied from them remain.
Imported example corrections are kept out of synthetic-data prompts and held-out sets.
Deleting a function stops its aliases immediately and purges its private content within 24 hours. Backups expire separately.

Credentials

API keys are shown once. Seldon stores only what it needs to verify them.
Stored BYOK credentials are encrypted in a dedicated vault. Transient x-byok-key headers are used for the request and not stored.
Keep credentials out of function drafts and imported requests.