Zero prompt retention by Lithune: prompt and completion content is processed in memory, is not written to Lithune's persistent storage and is never used for training.
Prefix caching remains enabled. Derived KV-cache blocks may stay in volatile memory until eviction or service restart; this cache is not prompt or completion content stored in a persistent database or file.
Inference flow
Requests may reach Lithune through OpenRouter and Cloudflare. Once received by Lithune, the request is sent only to the model running on Lithune-owned hardware in Türkiye. Lithune does not forward prompt content to an external model API, cloud GPU or model-training provider.
Training policy
- Prompts and completions are not used to train, fine-tune, evaluate or adapt a model.
- Inference content is not intentionally written to a file, database or other persistent store.
- Model weights are not updated using user requests.
- Only limited operational metadata is retained as described below.
Retention schedule
For public traffic routed by OpenRouter, Lithune records successful inference usage metadata against the shared provider credential presented by OpenRouter. Lithune does not receive the end user's OpenRouter API key, account identity or billing details, so these records do not identify an individual OpenRouter user to Lithune.
| Data | Stored by Lithune? | Retention | Purpose |
|---|---|---|---|
| Prompt content and attachments | No persistent storage | In-memory processing only | Generate the requested response |
| Completion content | No persistent storage | In-memory processing only | Deliver the response |
| Token counts and timestamps for successful inference requests | Yes; no prompt or completion content | Latest 5,000 records and no more than 90 days, whichever comes first | Usage verification, support, troubleshooting and abuse/security investigation |
| Key-linked daily/rolling request and token totals and exact last-use time | Yes | No more than 90 days | Usage accounting and capacity planning |
| Privacy-minimized failure events and fixed-cause aggregates | Yes; no prompts, completions, raw keys, IP addresses or media URLs | Latest 5,000 event rows and no more than 90 days; aggregates no more than 90 days | Reliability, capacity, support and security |
| General public website and API access logs | No | Disabled | — |
| Operational and error logs | Only operational messages and errors; normal request access logging is disabled | Service journals: separate rolling journal per operational service, each limited to 14 days and 500 MB. Technical server error log: only the web server process errors, without any request data; kept 14 days, longer only if the server was off or maintenance blocked the deletion when it was due. | Reliability, failure diagnosis and security |
| Support e-mails sent to Lithune | Yes, in Lithune's e-mail provider | Until the request and any related follow-up are handled | Answer support, privacy, legal and security requests |
The 90-day period is Lithune's purpose-based maximum rather than a statutory allowance. The limits are enforced during writes and by a persistent daily cleanup. Backups and exports containing either metadata store remain subject to the same deletion or restriction request.
Infrastructure and other providers
- Inference: performed on privately owned Lithune hardware located in Türkiye.
- OpenRouter: may handle platform access, routing, account data and billing under its own policies.
- Cloudflare: may handle network delivery and security data under its own policies.
- External model providers: none are used after a request reaches Lithune's inference pipeline.
Security controls
- TLS protects traffic in transit between public routing services and Lithune.
- API requests require a valid provider credential, and concurrency and capacity controls reject excess requests before they reach the model.
- General public website and API access logging is disabled. API failures emit only timestamp, final status, producing layer, coarsened route and method, fixed cause and duration; no key, address, request ID, content, media URL, query or user-agent is included.
- Infrastructure and retained metadata are restricted to authorised operational access, and these controls are reviewed as the service changes.
More information
This technical policy supplements the Privacy Notice. Product support, privacy, legal and security requests may be sent to [email protected].