> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-agentix/learn-about-cortex-agentix/data-retention-policy.md).

# Data retention policy

Learn more about the default retention periods for all Cortex AgentiX licenses and the available retention add-ons.

All Cortex AgentiX licenses provide you with six months of default retention for cases and issues data, as well as agentic assistant chats and related artifacts.

Cases data is retained according to the **Last Updated** date. Issue data is retained according to the **Observation Time** date. Data collected within these dates is kept and displayed for six months. To ensure the accuracy of issues, Cortex AgentiX provides a grace period of up to 31 days for issues displayed in the Issues view, Issues table, and Cases view.

You can extend your license retention by purchasing a retention add-on. Each retention add-on provides an additional 31 days of case and issue retention and agentic assistant chats and related artifacts, in addition to the default six months.

For more information on your storage license details, see [Dataset Management](/cortex-agentix/configure-cortex-agentix/data-management/dataset-management.md).


---

# 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://cortex-docs.paloaltonetworks.com/cortex-agentix/learn-about-cortex-agentix/data-retention-policy.md?ask=<question>&goal=<user_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.