> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/privacy-hubs/configuration/data-subject-requests.md).

# Data subject requests

Learn how to configure a Data subject requests collection form in your Privacy hub

#### Activating the 'Data subject requests' feature in Your Trust center

To activate the ' Data subject requests' feature in your Trust center, refer to the general configuration section where you can enable or disable this option. Once enabled, a new public page titled 'Data subject requests' will be added to your Trust center.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2FoXjz7lyLsPJYGYFUoKwD%2FCapture%20d'%C3%A9cran%202024-11-18%20233858.png?alt=media&amp;token=1f8ad3fa-2a9a-491e-a6df-647ad8341374" alt=""><figcaption><p>The Data subject requests configuration accordion</p></figcaption></figure>

#### Prerequisites

To display a Data subject requests collection form in your Trust center, you must have the **'Data subject requests'** module included in your subscription and have previously configured and published a collection form.

#### Data subject requests collection form

This field allows you to select the Data subject requests collection form to display in your Trust center. Note that only one collection form can be displayed per Trust center.


---

# 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://doc.dastra.eu/en/features/privacy-hubs/configuration/data-subject-requests.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.