> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/api-and-platform/widgets/privacy-widgets.md).

# Privacy widgets

A Privacy widget is an end-user-facing form used to either collect preferences from your end-users or allow them to submit privacy requests.

**Didomi provides three types of widgets to collect preferences.**

* Single purpose widget: A contextual question embedded on your website.
* Multi purpose widget: Several or all questions in one place, accessible directly on your website.
* Preference Center: All preferences in one place, accessible through a dedicated URL.

**Didomi provides one widget to allow your end-user to submit privacy requests.**

* Privacy Request widget: All user's rights supported by Didomi in a unique form, accessible directly on your website.

For each widget, we provide different options in terms of configuration and implementation.

<table><thead><tr><th width="158">Widget</th><th width="158">Product</th><th width="178">Implementation</th><th width="158">Purposes and preferences from your Configuration Tree</th><th>Collect preferences</th><th>User Rights</th></tr></thead><tbody><tr><td>Single purpose widget</td><td><a href="/api-and-platform/widgets/privacy-widgets/create-a-widget.md#create-a-single-purpose-widget">Preferences</a></td><td>Embedded</td><td>1</td><td>On click</td><td>N/A</td></tr><tr><td>Multi purpose widget</td><td><a href="/api-and-platform/widgets/privacy-widgets/create-a-widget.md#create-a-multi-purpose-widget">Preferences</a></td><td>Embedded</td><td>All</td><td>Save button</td><td>N/A</td></tr><tr><td>Preference Center</td><td><a href="/api-and-platform/widgets/privacy-widgets/create-a-widget.md#create-a-preference-center">Preferences</a></td><td>Hosted</td><td>All</td><td>Save button</td><td>N/A</td></tr><tr><td>Privacy Request widget</td><td><a href="/api-and-platform/widgets/privacy-widgets/create-a-widget.md#create-a-privacy-request-widget">Privacy Requests</a></td><td>Embedded</td><td>N/A</td><td>N/A</td><td>All</td></tr></tbody></table>

You can customize each widget's appearance and content to fit your brand, adjust the authentication process, and either embed it in your website or host it on a separate webpage.

* [Create a widget](/api-and-platform/widgets/privacy-widgets/create-a-widget.md)
* [Retrieve widgets](/api-and-platform/widgets/privacy-widgets/retrieve-widgets.md)
* [Edit a widget](/api-and-platform/widgets/privacy-widgets/edit-a-widget.md)
* [Deploy a widget](/api-and-platform/widgets/privacy-widgets/deploy-a-widget.md)
* [Authentication](/api-and-platform/widgets/privacy-widgets/authentication.md)
* [Archive a widget](/api-and-platform/widgets/privacy-widgets/archive-a-widget.md)
* [Headless widgets](/api-and-platform/widgets/privacy-widgets/headless-widgets.md)
* [Tutorial](/api-and-platform/widgets/privacy-widgets/tutorial.md)


---

# 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://developers.didomi.io/api-and-platform/widgets/privacy-widgets.md?ask=<question>&goal=<user_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.