> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loisforword.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI provider data retention

> How retention controls apply when LOIS for Word sends customer content to AI providers, and how provider processing differs from content stored in the product.

LOIS for Word uses contractual and technical data-retention controls when sending customer content to AI providers. Zero Data Retention (ZDR) applies to eligible provider processing; it does not mean that content intentionally saved in LOIS for Word is immediately deleted.

## What ZDR means

For an eligible request covered by ZDR, a model provider processes the request without retaining its content in provider logs for model training or later reuse. The exact controls depend on the provider, service configuration, and feature being used.

<Note icon="shield-lock">
  Provider-level ZDR is separate from LOIS for Word storage. Chats, playbooks, saved prompts, and precedent may remain available in the product according to organization settings and user actions.
</Note>

Provider data controls may include:

* Contractual restrictions on model training
* Reduced or disabled provider logging for eligible requests
* Technical configuration that prevents application-state storage where supported
* Data-processing terms governing permitted use

Some provider features or endpoints may have different retention requirements. LOIS for Word evaluates provider controls in the context of the features it uses.

## What ZDR does not cover

Provider-level ZDR does not automatically delete content stored in LOIS for Word, including:

* Chat history retained under your organization’s policy
* Playbooks, checks, profiles, and saved prompts
* Precedent and other knowledge-base content
* Account, organization, and product configuration data

See [Data protection](/docs/security/data-protection) for product storage and [Organization settings](/reference/organizations/organization-settings) for chat retention controls.

## Why it matters

<CardGroup>
  <Card title="Stronger Security" icon="lock">
    No persistent storage means dramatically reduced risk of data leakage, even in the event of provider compromise.
  </Card>

  <Card title="Data minimization" icon="scale-balanced">
    Limiting provider retention supports data-minimization and purpose-limitation practices.
  </Card>

  <Card title="Transparent Governance" icon="eye">
    Documented provider controls help organizations evaluate how requests are processed and retained.
  </Card>
</CardGroup>

We’re committed to privacy-first AI and continue to partner with providers to push the boundaries of secure, compliant, and responsible LLM usage.