Skip to main content
Inference.net is designed to support production workloads without treating captured request data casually.

Core principles

  • request data is not used for model training by default
  • secrets and similar sensitive values are stripped where possible
  • platform data is encrypted in transit and at rest
  • retention should match the operational need of the workflow

Direct API vs Observe

The direct API and Observe are different product paths, but the same general rule applies: only keep what is operationally useful, and use project-level controls and data curation intentionally. For the workflow-first entry point into Observe, start with /start-here/observe-quickstart.
  • use environments and task IDs to segment traffic
  • create long-lived datasets only for the examples you want to preserve
  • review retention expectations before broad production rollout

Need a specific retention policy?

If you need a specific policy, no-retention handling, or help mapping the platform into your internal compliance requirements, meet with our team.