Privacy and accounting
VERSION 2026-09-10
No content archive
We do not store prompts, model responses or attachments in our application database, and do not maintain a permanent per-request AI history. Processing still occurs: the gateway receives content and sends it to the chosen provider. This is not end-to-end encryption directly to the model.
Account aggregates
We retain account or Telegram ID, locale, balance, access settings and keys. Cumulative account/key counters cover requests, successful responses, reported uncached input, output, cache read/write and charges. Missing usage is flagged, not guessed. Historical cache information may be unavailable.
Temporary accounting
A technical queue event contains identifiers, numeric usage, latency and cost, never prompt/response content. It is usually processed within seconds, later during failures. Aggregates are updated transactionally. An unlinked processing identifier prevents duplicate charges for up to 14 days with periodic cleanup; it has no user/model linkage. Infrastructure queues and backups have their own retention behavior.
Availability and finances
Per-model outcomes are aggregated into five-minute buckets without user or key identifiers. Regular probes provide sampled 24-hour availability; traffic is used before the first probe. This is not an SLA or continuous time measurement. Old buckets expire. Payments, refunds and adjustments are retained separately; AI charges are grouped by UTC day. Broadcast delivery states and limited administrative/payment security logs are also retained.
Keys and external processors
New keys are encrypted for owner-requested reveal and hashed for authentication. Older hash-only keys cannot be recovered. Telegram, Cloudflare, payment intermediaries and model providers process data under their own policies. Our no-content-archive commitment does not bind them. Avoid sensitive content unless you have assessed those policies. You can revoke keys, change locale and disable broadcasts in the bot. Operator contact and statutory financial-retention periods must be finalized before legal launch.
Operator details and support contact are being finalized. Legal preparation of the paid service is not complete.