> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/facilitation/facilitator-dashboard/data-retention-and-erasure.md).

# Data Retention and Erasure

There are several layers of data retention and they serve different purposes.

The controls are in the Facilitator Dashboard above the Master Events List(s) and explained here:

[Master Events List](/feature-documentation/designing-and-running/master-events-list.md) in Reset Option.

| Requirement                                              | How To                                                                                      | Comments                                                                                                                                                                                                                        |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Eradication of exercise, exercise data and players       | From the Editor, upload a new open or empty exercise with only the designer as Facilitator. | <p>This will remove all players, their data and replace the scenario. <br><br>System logs from the exercise will survive in Conducttr for security and auditing purposes for 90 days and will be then automatically deleted</p> |
| Erase audience records (i.e. email addresses of players) | From the Editor upload a new team with only the designer as Facilitator                     | <p>This will remove all players.<br><br>System logs from the exercise will survive in Conducttr for security and auditing purposes for 90 days and will be then automatically deleted</p>                                       |
| Erase exercise data                                      | From the Facilitator Dashboard click to Reset Messages and Reset Data                       | <p>Exercise data and messages from the last session will be deleted.<br>System logs from the exercise will survive in Conducttr for security and auditing purposes for 90 days and will be then automatically deleted</p>       |

**Question: What about the exercise After Action Report?**

Answer: The report is generated on-demand when the Facilitator asks for it to be downloaded. It does not exist independently of the exercise data and is deleted after download - hence is not retained. If the data is erased, requesting a report will produce an empty document.


---

# 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/facilitation/facilitator-dashboard/data-retention-and-erasure.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.
