Privacy notice

1. Static site

This static site does not use analytics, cookies, or tracking scripts. It has no forms, customer accounts, or public payment flow. Ordinary hosting and network infrastructure may process connection information needed to deliver and protect the site.

2. Account and payment information

Direct onboarding may provide Teralor Tech with a customer's name, organization, contact details, account identifier, approval record, and support communications. Stripe processes the hosted payment. Teralor Tech receives and keeps the payment and Checkout identifiers, payment status, amount, currency, approved offer identity, and related account information needed to verify credit and reconcile balances and disputes. Teralor Tech does not receive the full payment-card number through this service.

3. Prompts and model responses

The API necessarily processes prompts and model responses to complete a request. That content passes through the customer gateway and model-serving infrastructure and may be held transiently in process memory while the request is handled. The service does not intentionally persist prompt or response content in its application database, billing records, operator logs, or backups. Prompt and response content is not used to train models by Teralor Tech.

Customers should not submit secrets, regulated data, or highly sensitive personal information unless that use has been expressly reviewed and approved through the direct onboarding channel.

4. Operational metadata

Teralor Tech records non-content operational metadata needed to authenticate access, meter service, secure the system, provide balance statements, and perform billing and reconciliation. This may include safe account and key identifiers, request identifiers, timestamps, model name, status, token counts, cost, cumulative credit and spend, account state, webhook event identifiers, and operator action records. Authorization values and plaintext API keys are excluded from application logs and persistent records.

5. Retention and disclosure

Account, payment, credit, usage, security, and operator records are retained as needed to operate the alpha, reconcile balances, investigate incidents, maintain accounting records, handle disputes, and meet legal obligations. Retention depends on the type and purpose of the record. Payment processing uses Stripe; service data may also be handled by infrastructure providers only as needed to provide and protect the service or comply with law.

6. Security and choices

Teralor Tech uses access restrictions, encrypted public transport, secret separation, and content-excluding operational logs as security controls. No system is free of risk. Customers should protect their API key and report suspected exposure through the direct onboarding channel without sending the key itself.

Questions or requests about account information can be made through that same direct channel. Teralor Tech will assess requests under applicable law and may need to retain records required for security, accounting, disputes, or legal compliance.