> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/versions-and-proofs/privacy-records-beta/privacy-record-deletion.md).
# Privacy record deletion
Privacy record requests are available in the Didomi portal for 30 days after their latest creation/update date at which point they will be automatically deleted. Use the **Record Deleted In** column on the privacy records page to view the remaining days on any privacy record request.
{% hint style="info" %}
Update the privacy record request to reset the remaining days until the privacy record is deleted from the Didomi portal. Click here for more information.
{% endhint %}
Once the 30 day limit on a privacy record has lapsed, the privacy record will no longer be available in the Didomi console.
{% hint style="warning" %}
**Note**: The end-user's privacy record will still be stored in the Didomi database and can be retrieved by generating a new request for the privacy record.
{% endhint %}
---
# 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.didomi.io/versions-and-proofs/privacy-records-beta/privacy-record-deletion.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.
