> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/security/deletion-policies.md).

# Data retention

Delete recordings automatically once they reach an age you choose.

Delete recordings automatically once they reach an age you choose. Available on Pro and Enterprise.

{% embed url="<https://app.screendesk.io/recordings/bca7ca1d-5584-478f-8dd4-63f52039b3d8>" %}

{% hint style="danger" %}
Deleted recordings can't be recovered.
{% endhint %}

In **Settings → Data retention**, click **New policy** and complete the sentence:

> Delete \[Customers / Team / Video calls] after \[30] days \[in any folder / in a folder / with a label]

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2F9sPG4TTLXj43BE5iVXmK%2Fdocs-panel-retention.png?alt=media" alt="Settings, Data retention with two policies"><figcaption></figcaption></figure>

A new policy starts off. Click the eye icon to see what it will delete, then turn it on. Policies run every day at midnight UTC.

* Team includes bug reports.
* Reusable videos are never deleted.
* On a plan without Data retention, policies turn off but stay saved.


---

# 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.screendesk.io/security/deletion-policies.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.
