Skip to main content

​
Overview

DeerAPI is designed to route API requests while limiting the data that is stored for routine service operation.

​
Request content

DeerAPI does not use customer prompt or completion content to train models. Operational logs may include metadata such as request time, request ID, endpoint, model ID, status code, token usage, IP address, and account usage.

​
Account information

DeerAPI may collect account details that you provide, such as email address, login provider identifiers, billing records, and support messages. This information is used to operate the service, prevent abuse, and respond to support requests.

​
Security

Keep API Keys private. Store keys in server-side environment variables or a secrets manager, and rotate keys after exposure. No internet service can guarantee absolute security, but DeerAPI applies access controls and operational safeguards to protect service data.

​
Third-party providers

Requests may be processed by model providers that power the selected model. Review the provider terms that apply to the models that you use.