> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/security/data-residency-and-compliance/data-retention-periods.md).

# Data Retention Periods

Data retention is limited to the period necessary to fulfill the purposes for which it was collected and processed. Once the defined retention period expires, the data is systematically purged or anonymized according to our data lifecycle management policies.

Refer to the following table for the standard data retention periods associated with key entities within our systems:

| Entity                 | State     | Retention Period                    |
| ---------------------- | --------- | ----------------------------------- |
| Client                 | Active    | Indefinitely                        |
| Client                 | Inactive  | Following termination of contract   |
| Consent                | Created   | 30 days                             |
| Consent                | Accepted  | Until revoked                       |
| Consent                | Revoked   | 180 days                            |
| Connection Credentials | Active    | Until associated consent is revoked |
| Connection Credentials | Inactive  | Removed immediately                 |
| File.1 File            | Draft     | 30 days after last modified date    |
| File.1 File            | Submitted | 30 days after submission            |


---

# 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.zwapgrid.com/security/data-residency-and-compliance/data-retention-periods.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.