> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/resources/data-privacy/data-retention.md).

# Data Retention

Retention periods for different types of data collected by Currents

{% hint style="info" %}
Retention plans can be customized per customer upon request.

This customization can affect the standard pricing published on our website. The actual deletion / rotation of the data can happen after the deadline.
{% endhint %}

### Retained Data

In addition to the data stored permanently in our database, as outlined in the [Access to Customer Data](/resources/data-privacy/access-to-customer-data.md) page, we also have a description of certain data types subject to time retention limits.

| Data type                                                                                                                                                                                | Retention time                                                                                                        |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| <p><mark style="color:orange;">Artifacts</mark></p><ul><li>screenshots</li><li>videos</li><li>terminal output</li><li>traces</li></ul>                                                   | <p>21 days for <a data-footnote-ref href="#user-content-fn-1">high impact tests</a></p><p>7 days for passed tests</p> |
| <p><mark style="color:purple;">Test results</mark></p><ul><li>error details</li><li>test results</li></ul>                                                                               | <p>3 months in hot storage<br>9 months in cold (archive) storage</p>                                                  |
| <p><br><mark style="color:green;">Tests details</mark></p><ul><li>execution steps</li><li>test records</li><li>live preview</li></ul>                                                    | <p>30 days in hot storage<br>60 days in cold (archive) storage</p>                                                    |
| <p><mark style="color:blue;">Reports / Analytics / Aggregated Results</mark></p><ul><li>Aggregated test metrics</li><li>Aggregated run metrics</li><li>Aggregated step metrics</li></ul> | 12 months                                                                                                             |

If you have any questions or concerns, please feel free to reach out to us through our support channels: **<support@currents.dev>** or via the in-app chat.

[^1]: (failed, flaky, quarantined, etc)


---

# 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.currents.dev/resources/data-privacy/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.