How are API request content and metadata handled?
This page states the everyday boundary. For a dispute, compliance question, or security incident, the privacy policy controls.
Bodies and metadata
Request and response bodies are used for that request's routing, billing, and failure handling. Bodies are not kept long term except for the operational, billing, security, anti-abuse, troubleshooting, dispute, legal, and backup cases listed in the privacy policy, and for features you turn on yourself.
These records are kept: model name, token usage, charge, status code, latency, error summary, security logs, and risk signals. They show up in request logs and usage details.
Who else sees a request
Model providers process requests under their own terms, privacy policies, and data-handling rules. I Code Easy does not sell API request content or personal information. Use of the service is covered by the terms and acceptable use.
Where to read prices, balance, and bills is in pricing, balance, and usage.
Related guides
Where can I check RMB prices, balance, and usage details?
Check live RMB prices, account balance, request logs, token usage, billing details, and payment availability through the public and dashboard surfaces.
FAQ
Troubleshoot API keys, 401 and 429 responses, Windows environment variables, client connectivity, quotas, and support reporting.