> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/truvera-workspace/team-management/data-retention-policies.md).
# Data retention policies
Every team can customize their data retention policies based on specific requirements. Truvera promotes user privacy and data management best practices by minimizing stored data and empowering customers with flexible retention controls. You can now configure:
* **Verification Data Retention Policy**: Credential presentation data from completed verification requests will be automatically deleted after the selected time. Default is 72 hours, with a 1 hour minimum retention time.
* **Verification Requests Retention Policy**: Verification request data (except for verification ID) will be automatically deleted after the selected time. Default is 72 hours, with a 1 hour minimum retention time.
* **Credential Offers Retention Policy**: Unclaimed credential offers will be automatically deleted after the selected time. Default is 72 hours, with a 1 hour minimum retention time.
{% hint style="warning" %}
This setting does not apply to credential offers generated via the OID4VC Issuer API with `singleUse` set to `false`. These offers persist until manually deleted.
{% endhint %}
* **Credentials Retention Policy**: All except persisted credentials will be automatically deleted after the selected time. Default is infinite, with a 1 hour minimum retention time.
These granular settings give you complete control over your data lifecycle while maintaining compliance with privacy regulations.
There is an option to store subject reference ID, that shows up on the credential view table and can be useful for filtering the credentials. The storing of it is optional as it may contain PII and is not suitable for all use cases.
---
# 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.truvera.io/truvera-workspace/team-management/data-retention-policies.md?ask=&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.
