> 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/introduction/privacy-request-implementation-overview.md).
# Privacy request implementation overview
Didomi offers the Privacy request feature to enable your organization to collect and manage end-users' Data Subject Access Request (DSAR). In this article, we will provide a general implementation path to create, configure, and launch the Didomi privacy request solution on a website.
* [Overview](#overview)
* [Console configuration](#console-configuration)
* [Embed privacy request widget](#embed-privacy-request-widget)
***
### Overview
### Console configuration
Use the table below to track the necessary configurations that need to be performed within the Didomi console before adding the required code onto your website.
### Embed privacy request widget
Once your privacy request widgets are configured and published, your organization can embed the required Didomi code onto your page.
{% hint style="warning" %}
**Note**: The resource below assumes 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 %}
---
# 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/introduction/privacy-request-implementation-overview.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.
