> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/backup-and-archive/search/purging-data-from-flosum-backup-and-archive.md).
# Purging Data from Flosum Backup & Archive
{% hint style="success" %}
#### Required User Credentials
\[**Flosum User**] - **Backup & Archive** license with **App Settings** permissions
{% endhint %}
## Overview
Purging data deletes selected records from all your Flosum backups and archives, helping you meet GDPR requirements. The process starts with searching for the data you want to remove. After confirming the search results, you can continue with the purge. This article shows how to purge data after a search is complete. To learn how to perform a search, see the following article.
* [Searching in Flosum Backup & Archive](/backup-and-archive/search/searching-in-flosum-backup-and-archive.md)
{% hint style="info" %}
To search for records, you must have **Backup & Archive** permissions. Therefore, to execute both a Search and a Purge, permissions for **Backup & Archive** and **App Settings** are required.
{% endhint %}
{% hint style="warning" %}
Purging Data will only delete records from the Flosum **Backup & Archive** app. No data will be deleted from **Salesforce**.
{% endhint %}
## Purge Data
{% stepper %}
{% step %}
### Select Search Request
1. Click **Search** from the sidebar menu.
2. Click the **Organization Switcher** from the breadcrumb path.
3. Select the organization you wish to use.
4. In the **History** table, click a **Search Request** job marked as **Ready for purge**.
{% hint style="info" %}
Only **Search Requests** that have one or more **Records** and haven’t been purged will be marked as **Ready for purge**.
{% endhint %}
{% endstep %}
{% step %}
### Review Data
It is essential to review the search results before purging the data. For instructions on reviewing search results, see the **Reviewing Search Results** section of the following article.
* [Searching in Flosum Backup & Archive](/backup-and-archive/search/searching-in-flosum-backup-and-archive.md#reviewing-search-results)
{% endstep %}
{% step %}
### Run Purge
{% hint style="warning" %}
Running a **Purge** will permanently remove the selected data from all backups and archives. Review the data to confirm that the correct data is being deleted, as this process cannot be reversed.
{% endhint %}
1. Click **Run purge**.
2. Click **Run purge** on the **Run purge** confirmation dialog box.
3. Scroll down to the **History** table to view the status of the Purge Job.
{% endstep %}
{% endstepper %}
---
# 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.flosum.com/backup-and-archive/search/purging-data-from-flosum-backup-and-archive.md?ask=&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.
