> 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/data-security-documentation/get-started-with-cortex-data-security/understand-cortex-data-security-licenses/license-expiration.md).

# License expiration

Cortex Data Security licenses are valid for the period associated with the license purchase.

* **Access grace period:** After the license expires, you retain console access for an additional 48 hours. After the 48-hour grace period, the interface is disabled until the license is renewed.
* **First 31 days after expiry:** Cortex Data Security continues to monitor your data sources and retains data in the Cortex Data Layer according to your retention settings (default 30 days for ingested data).
* **After 31 days:** The tenant is decommissioned. All data, configurations, and data security policies are deleted, and data collection ceases.

{% hint style="warning" %}
**Warning:** To avoid data loss, renew the license or extend retention before the 31-day decommissioning window ends. Purged data cannot be recovered.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/data-security-documentation/get-started-with-cortex-data-security/understand-cortex-data-security-licenses/license-expiration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.