Security
Last reviewed August 25, 2026
Transport and access
Public EasyAI traffic is served over HTTPS. API requests require an API key, while console access uses the authentication and security controls configured in New API.
Protect your keys
Store API keys in server-side environment variables or a secret manager. Never commit keys to source control or embed them in browser, mobile, or desktop client code. Revoke and replace an exposed key immediately.
Data handling
EasyAI does not use user requests or responses to train models. Requests are forwarded to the selected upstream model provider, whose security and retention rules may also apply. Billing and technical metadata may be retained for operations, abuse prevention, and legal obligations.
Report a vulnerability
Email market@easyairoute.com with a clear description, affected URL, reproduction steps, and potential impact. Do not access other users' data, disrupt production, or publicly disclose an unresolved issue.
Current assurance level
No independent security audit or certification is claimed unless it is explicitly published here. Security controls and operational practices will be updated as the service matures.