Trust & transparency

Data retention

Different records serve different operational and accounting purposes.

Draft for legal and operational review. This document must be finalized for the operator and deployment jurisdiction before commercial launch.

Prompt and response content

Not stored by this application. Content is processed transiently for forwarding and streaming. Upstream inference and network providers apply their own policies.

Usage metadata

Content-free request metadata is subject to the configured activity retention schedule. The default scheduled cleanup removes usage metadata older than 30 days. Aggregate and financial records can have separate retention needs.

Sessions and security

Authentication sessions expire and can be revoked. Token hashes, verification records, and necessary security records are retained only for their active purpose and configured lifecycle.

Financial records

Immutable ledger entries, invoices, payment events, and administrative financial audit records are retained separately. The operator must set a legally reviewed financial retention period before launch; deleting an account does not erase records required for accounting or law.

Provider boundaries

Cloudflare, OxaPay, and the inference provider process data independently. This schedule describes the application, not an unverified zero-retention agreement with upstream services.

Draft updated October 25, 2026.