> For the complete documentation index, see [llms.txt](https://docs.zenlytic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenlytic.com/legal-and-support/legal/llm-data-use-and-retention.md). # LLM Data Use and Retention Policy How customer data sent to Zenlytic's third-party LLM providers is used and how long it is kept. Last updated: October 2026 Zenlytic is a product of Chord Commerce, Inc. In this policy, "Zenlytic," "we" and "us" refer to Chord Commerce, Inc. as the provider of the Zenlytic service. Zenlytic uses third-party large language model (LLM) providers to power Zoë and other AI features. This policy explains how customer data sent to those providers is used and how long it is kept. ## No training on customer data Zenlytic does not use Customer Content to train AI models. Under the commercial terms that govern our use of each provider's API, providers do not use customer prompts or outputs to train their models. ## Provider retention * OpenAI: prompts and outputs may be retained in OpenAI's abuse monitoring logs for up to 30 days * Anthropic (Claude), via Google Cloud Vertex AI: prompts and outputs may be retained for up to 30 days * Google (Gemini), via Google Cloud Vertex AI: prompts and outputs may be retained for up to 30 days Retained data is used only to detect misuse and is not used to train models. ## Customer-controlled routing Customers can route LLM traffic to their own LLM instance. In that case, the customer's own agreement with that provider governs retention and use. ## Changes We will notify customers of changes to LLM providers or retention periods as set out in the Data Processing Addendum and AI Addendum. ## Contact --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zenlytic.com/legal-and-support/legal/llm-data-use-and-retention.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.