> ## Documentation Index
> Fetch the complete documentation index at: https://docs.laozhang.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How LaoZhang API handles data and logs

> How LaoZhang API handles prompts, responses, request metadata, billing records, account data, and support materials under its Terms and Data Policy.

LaoZhang API does not store API prompts or responses by default. API content is transmitted only as necessary to process the request and return the result.

Based on the [Terms](https://www.laozhang.ai/terms) and [Data Policy](https://www.laozhang.ai/data-policy) (updated January 1, 2026), last verified **September 2, 2026**; the formal policies control if this page differs.

## API prompts and responses

| Item | LaoZhang API boundary |
| - | - |
| Stored by default | No |
| Default retention | Not applicable |
| Use | Transmitted only to process the request and return the result |
| Training or profiling | Not used by default for model training or user profiling |
| Third-party processing | Sent to the upstream model and infrastructure providers required to complete the request |

<Warning>
  Upstream providers may apply their own logging, retention, abuse monitoring, safety review, training, and opt-out terms. LaoZhang API cannot guarantee that every upstream provider uses the same data practices.
</Warning>

## Request metadata

LaoZhang API stores operational metadata such as:

* account or API key identifier;
* timestamp, model, endpoint, and route;
* token or usage amount and billing unit;
* request status, error category, and latency;
* routing reliability, security, and abuse-prevention information.

Troubleshooting logs are generally retained for **7 days**. Relevant data may be retained longer where reasonably necessary for security, abuse investigation, billing disputes, legal compliance, or service integrity.

## Other stored data

| Category | Examples | Retention boundary |
| - | - | - |
| Billing and transaction records | Credit purchases, balance changes, amounts, currency, invoices, refunds, and chargebacks | As required for accounting, tax, payment disputes, anti-fraud, and legal compliance |
| Account and security data | Email, account settings, API key identifiers, IP address, user agent, login and security events | While the account is active and for a reasonable period after closure |
| Support materials | Messages, screenshots, error reports, and diagnostic files that the user provides | For a reasonable period needed to resolve requests, maintain support history, and handle disputes |

<Tip>
  Do not send complete API keys, passwords, regulated data, or sensitive personal information in support messages, screenshots, or public chats. Provide only necessary, redacted information through a support-approved secure channel.
</Tip>

## Cross-border processing and user responsibility

API requests may be transmitted to upstream model, infrastructure, and service providers in the United States, Singapore, the European Union, or other regions. Users are responsible for confirming that they:

1. have the right to submit and transmit the data;
2. have obtained necessary notices, consents, contractual protections, and legal bases;
3. comply with applicable privacy, data protection, cybersecurity, export-control, and cross-border transfer requirements;
4. minimize, de-identify, or anonymize personal, confidential, or regulated data where appropriate.

## Pre-integration checklist

* Store API keys in a server-side secret manager or environment variable.
* Minimize personal and sensitive data in prompts.
* Complete internal security, legal, and upstream-policy reviews before production use.
* Use [call logs](/en/faq/call-logs) to review metadata and errors without copying complete request content into support messages.
* Revoke or rotate a potentially exposed key immediately and contact support.

## Related documentation

* [Content safety and compliance](/en/faq/content-safety)
* [Call logs](/en/faq/call-logs)
* [API key management](/en/faq/token-management)
* [LaoZhang API Terms](https://www.laozhang.ai/terms)
* [LaoZhang API Data Policy](https://www.laozhang.ai/data-policy)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.