> 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/privacy-requests/privacy-request-widgets/archive-privacy-request-widget.md).
# Archive privacy request widget
{% hint style="success" %}
**Access Type:** Privacy request widgets - Editor
**Premium Feature**: DSAR
{% endhint %}
Archiving a privacy request widget will remove the widget from any websites where that widget was embedded. In this article, we will cover how to archive an existing privacy request widget.
{% hint style="warning" %}
**Note**: Once a privacy request widget is archived it can no longer be edited, re-published, or duplicated.
{% endhint %}
Click **Privacy Requests** on the left-hand panel and select the **Widgets** tab on the subsequent page.
Navigate to a privacy request widget with a publication status of **Published** on the list and click the **ellipsis** inline with the privacy request widget name.
Select **Archive** from the menu.
{% hint style="info" %}
Only privacy request widgets with a [publication status](/privacy-requests/privacy-request-widgets/privacy-request-widget-status-glossary.md) of **Published** or **Unpublished Changes** can be archived.
{% endhint %}
Confirm the decision to archive the widget in the subsequent modal and click **Got it, archive!**
The privacy request widget will be archived and the widget will no longer be available on websites where the widget was embedded.
{% hint style="info" %}
Viewing archived privacy requests widgets are not available in the Didomi console and only retrievable via API. [Click here ](https://developers.didomi.io/api-and-platform/widgets/privacy-widgets/retrieve-widgets)to learn more.
{% 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/privacy-requests/privacy-request-widgets/archive-privacy-request-widget.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.
