> 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/embed-privacy-request-widget.md).
# Embed privacy request widget
{% hint style="success" %}
**Access Type:** Privacy request widgets - Editor
**Premium Feature**: DSAR
{% endhint %}
Once a privacy request widget is published, it can be successfully embedded onto your organization's website(s). In this article, we provide an overview of the process involved with embedding these privacy request widgets.
{% hint style="warning" %}
**Note**: The directions in this article and section assume your organization is creating and configuring your privacy request widget within the Didomi console which limits the deployment options. [Click here](/privacy-requests/privacy-request-widgets.md#didomi-console-vs-didomi-api) to learn more about the differences between utilizing the Didomi console vs the Didomi API and its impact on deployment.
{% endhint %}
The configuration for your published privacy request widget is stored in an Amazon S3 bucket and can be accessed by loading the Didomi SDK and adding the relevant Didomi container on your website.
To find the necessary code snippets that need to be added to your organization's website(s), 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](/privacy-requests/privacy-request-widgets/privacy-request-widget-status-glossary.md) of **Published** on the list and click the **Edit** icon inline with the privacy request widget name.
Select the **Embedding** tab in the privacy request widget configuration flow and navigate to the right-hand panel.
Use the provided fields to copy and paste the SDK script and Didomi container code snippet onto your website(s). The necessary values will already be inserted into the copied code.
---
# 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/embed-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.
