OpenRouter and model providers
Battlecat uses OpenRouter as part of its report-generation system. Submitted material is sent to the report-generation provider so Battlecat can create the report.
Battlecat’s OpenRouter account is configured with Zero Data Retention routing enabled across the available model groups, including non-frontier, Anthropic, OpenAI and Google routes. Provider routes that do not meet the Zero Data Retention requirement are blocked by that setting.
Battlecat’s OpenRouter privacy settings also block paid and free endpoints that may train on request data, block free endpoints that may publish prompts, and do not allow the optional data-discount setting that permits input/output use for product improvement.
Prompt and completion logging is not intentionally enabled for ordinary Battlecat report generation.
OpenRouter and downstream model providers still process submitted material in order to generate the report. OpenRouter may retain request metadata such as token counts, latency, model/provider routing information and cost reporting, but this metadata does not include the content of prompts or responses according to OpenRouter’s documentation.
Battlecat also enforces provider privacy controls in the report-generation request where supported, including Zero Data Retention routing and denial of provider data collection.