Responsible AI and privacy

Overview

Language-model output can be inaccurate, incomplete, biased, or unsuitable for the task. Verify important claims and review generated code before executing it. Automated evaluation scores are aids to review, not guarantees about a whole application or a decision affecting a person.

API request recording is off by default. An authorized organization administrator can enable future request/response capture for investigation and evaluation. Captures are best-effort, may be truncated, and are scheduled for deletion after 30 days. Switching recording off does not remove existing retained recordings immediately.

Enable organization recording before exporting OpenTelemetry traces. Exported traces may include content your application captures, so remove secrets and unnecessary personal information before sending them. Billing, request identifiers, token counts and other usage metadata are separate from body recordings.

Observation MCP tools return a limited metadata view and exclude recordings, span input/output, arbitrary attributes, and judge rationales. Names and labels may still contain application-supplied information. Connect trusted agents, store credentials securely, and treat returned content as evidence rather than instructions.

Use the published policies for current terms, processing details, and safety expectations:

• Inference Data Handling
• AI Disclosure
• Privacy Policy
• Terms of Service
• Safety

This guide explains product behavior; it does not replace those policies or extend their commitments to a third-party agent, telemetry exporter, or evaluation provider.