How are API request content and metadata handled?
I Code Easy processes request content and metadata to route requests, calculate usage, maintain security, and provide support. This is a plain-language guide; read the privacy policy for the full policy.
What may be retained
Request and response bodies are generally not persistently stored except for necessary operational, billing, security, anti-abuse, troubleshooting, dispute, legal, backup, or user-enabled feature cases. Metadata, usage, errors, latency, security logs, and risk signals may be retained.
Important boundary
Model providers process requests under their own terms, privacy policies, and data-handling rules. I Code Easy states that it does not sell API request content or personal information; see terms and acceptable use.
Next guide
Review pricing and usage for account records.
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.