> For the complete documentation index, see [llms.txt](https://docs.replicacyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.replicacyber.com/admin-guide/4.4-admin-guide/data-management.md).

# Data Management

This page summarizes where data is stored and how key platform data is retained.

## Replica Environment

### Virtual Environment Storage

Each virtual environment includes a home directory that persists for the life of that environment.

Data stored outside the home directory may be removed when the environment is not running. When an environment is deleted, all data inside it is permanently removed.

## Replica Platform

Replica performs nightly backups of critical platform data to isolated external storage.

### Butler

See [Butler Admin Guide](/admin-guide/butler-admin-guide.md) for Butler storage, transfer, and audit details.

### Egress

See [Egress data policy](/admin-guide/egress.md#egress-data-policy).

### Logging

See [Logging data management](/admin-guide/logging.md#logging-data-management).

### Telephony

Telephony data for software-defined resources is retained for at least one year.


---

# 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://docs.replicacyber.com/admin-guide/4.4-admin-guide/data-management.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.