Zero data retention

Zero data retention means covered prompts, completions, traces, files, eval examples, labels, and comparable customer payloads are processed only for the request or workflow you authorize, and are not retained by Understudy after that processing is complete.

ZDR also means we do not use covered customer payloads to train, fine-tune, evaluate, or improve models for another customer.

For hosted gateway requests, covered payloads are request and response content sent through Understudy-managed infrastructure. We may retain operational metadata such as account, key, provider, model, timing, status, token counts, routing decisions, and error metadata where needed to operate, secure, debug, bill, and improve the service.

For local tools and workbench workflows, customer traces and artifacts remain under customer control unless the customer explicitly uploads, shares, or authorizes processing by Understudy.

When a customer enables a ZDR workflow, Understudy routes covered requests only to providers, accounts, or customer-supplied keys that the customer has approved for that workflow.

If a customer uses its own provider account or key, the provider's retention and training commitments are governed by the customer's agreement with that provider.

Some Understudy projects involve an agreed training, fine-tuning, evaluation, labeling, or model-improvement window. During that window, Understudy may process and retain the covered training materials only for the customer-authorized project.

After the agreed training window closes, ZDR applies to the covered materials and related runtime requests unless the customer and Understudy agree otherwise in writing.

Models, prompts, evaluators, routing rules, or other artifacts produced for a customer remain governed by the applicable order form, statement of work, or written agreement.

Understudy may use aggregated or de-identified operational signals across customers to improve reliability, safety, routing quality, latency, cost controls, and product workflows.

Those aggregate improvements do not allow Understudy to use one customer's confidential payloads to create or tune models for another customer.

We may retain limited records where required for security, abuse prevention, billing, audit, legal compliance, or to enforce our terms, but those records should not include covered prompt, completion, trace, dataset, or label payloads unless required by law or explicitly authorized by the customer.

Customer-specific written agreements, order forms, data protection addenda, or security addenda control where they conflict with this page.

Questions about ZDR, provider routing, or customer-specific security terms should be sent to support@understudylabs.com.