> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/data-retention.md).

# Data Retention

### Introduction

This tab allows the removal of events and other data related to cardholders from Command Centre.

**Note:** This tab will only display if your license file contains either `PIIRedaction=1` or `DataRetention=1`.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Data Retention** tab.

   The sub-tabs that display depend on what your site is licensed for, (i.e. for the **Redaction** sub-tab to display your license file must contain `PIIRedaction=1`, and for the **Retention** sub-tab to display your license file must contain `DataRetention=1`).

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cb7a62efe9ed1ba501057be865d79885da04ee1a%2Fdataretentiontab.png?alt=media)
3. The Redaction functionality enables the removal of cardholder personal identifiable information (PII) from Command Centre system to protect client data in European countries and the UK. This feature is provided to users as a set of REST API calls in Command Centre.

   If your site intends using this functionality, refer to [Redaction Configuration in Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction/redaction-configuration-in-command-centre.md) for the procedure.
4. Click the **Retention** sub-tab if displayed.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-05be1d638fcfaaa1f93a733e238b2c6a9df0306a%2Fdataretentiontab_retention.png?alt=media)
5. Configure the fields as required:

   **Note:** Operators require the "Manage Data Retention Settings" privilege to be able to edit fields on this sub-tab.

   <table><thead><tr><th width="274">Field</th><th>Description</th></tr></thead><tbody><tr><td>Limit Data Retention</td><td>When ticked, this enables the system to purge events as defined in the Schedule.<br>If the server is offline, events are purged once the server comes back online.<br>(Default = unticked)</td></tr><tr><td>Purge all Cardholder activity older than</td><td>When ticked, the system will remove all Cardholder activity for the period indicated.</td></tr><tr><td>Purge all events older than</td><td>This is the age of the events that will be removed from the system.<br>(Default = 7 years. Range = 1 to 99 years)</td></tr><tr><td>Remove cards (*) that are unused for more than</td><td>When ticked (default), this is the age of the unused cards that are removed from the system.<br>(Default = 7 years. Range = 1 to 99 years)</td></tr></tbody></table>
6. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/data-retention.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.
