Data handling basics.

Information we collect

• Account details such as email, GitHub identity, organization membership, and authentication events.
• API metadata such as request time, model, token counts, costs, status, latency, and key prefix.
• Billing and credit records needed to manage balances, limits, invoices, and refunds.
• Public-site attribution such as UTM parameters, referrer, page path, and coarse browser metadata.
• Google Analytics data such as page interactions, approximate attribution, device/browser signals, and cookie or client identifiers when analytics is enabled.

Prompts, outputs, and request bodies

Hosted requests may pass through Terminaili infrastructure for routing, logging, retry, debugging, and billing. Avoid sending secrets, regulated data, or confidential data unless your use case has the right permission and agreement.

How we use data

• Operate the API, route requests, measure capacity, and diagnose failures.
• Calculate usage, costs, credits, limits, and account activity.
• Improve onboarding, documentation, conversion, and support workflows.
• Protect accounts and investigate abuse, fraud, or compromised keys.

Sharing

Model providers and infrastructure vendors may process request data as needed to deliver the service. We do not sell personal data. We may disclose limited data when required by law, to protect the service, or with your direction. Google may process site analytics data for measurement when Google Analytics is enabled.

Retention and deletion

Operational logs and analytics are kept as long as needed for reliability, accounting, security, and support. Contact support@terminaili.com to request account export or deletion, subject to security and financial record requirements.

Security

API keys are treated as secrets, and the public product avoids exposing raw keys after initial creation. Security reports can be sent to security@terminaili.com.