> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/data-pipeline/jobs-and-costs-management/data-retention-policy.md).

# Data Retention Policy

Results from DataPipeline projects are stored temporarily, allowing you time to access and download them from the dashboard or receive them via a webhook. This policy outlines how long the data is retained for and when it is removed.

### Retention Period

* Job results are stored for **up to 30 days** from the time they become available.
* During this period, results can be downloaded or accessed at any time.

### Automatic Deletion

* After **30 days**, results are automatically deleted from the system.
* Once deleted, results cannot be recovered.

### Best Practices

To avoid losing your data, we recommend:

* Downloading the results shortly after they become available.
* Using webhooks to automatically store results in your own system.


---

# 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.scraperapi.com/data-pipeline/jobs-and-costs-management/data-retention-policy.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.