> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/panel-management/panelist-consent-and-opt-in.md).

# Panelist consent and opt-in

As part of GDPR compliance, your panelists have full control of their data. They have the option to opt-in or -out of all communications, such as email and SMS, from your company. Your panelists also have the option to delete all of their data.

## Opt-out of communications

The **Unsubscribe** hyperlink at the bottom of any email sent to the panelists via Private Panels links to the **Opt In** panel property on their profile. They can change this panel property to **Opt out** by clicking the **Unsubscribe** hyperlink.

<img src="https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/uUJ1xaIt2lzyrn3jZrK1/38060661394836" alt="" width="563">

The hyperlink will open the **Consent Management** web page where the panelist can see and verify their account details. They can turn off the toggle bar beside **Opted in** to opt out after verifying their details.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/XUZvl3MuBHKrZGe7Rst7/37034481355540)

The text beside the toggle bar will then change to **Opted out.**

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/JW2SJffxXo1wTXERAVqi/37034481358484)

If a panelist has chosen to opt out of communications, Private Panels will block all outgoing emails to this individual. Then, you can only get in touch with the panelist from your company email.

## Delete panelist data

The option to delete a panelist’s data can also be found at the bottom of any email sent to them via Private Panels. This is the **manage your data** hyperlink.

<img src="https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/OFCTgO03uBV3WTvhwfZt/38060661395860" alt="" width="563">

The **manage your data** hyperlink will open the **Consent Management** webpage, which contains their account details and two options, in a new tab. The user's data can be deleted by clicking the **Manage deletion of my profile and data** hyperlink

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/dFGvHblA83GNGkXEWVnc/37034481361044)

The user can either confirm or cancel the deletion of their data on the next page. They can proceed with the deletion by clicking the **Delete my data** button

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/fJ0JOhPvWuwDBeGH7MNh/37034460780692)

After confirming, the deletion will take effect immediately.

{% hint style="info" %}
**Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact <support@dscout.com>.
{% 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://help.dscout.com/private-panels/panel-management/panelist-consent-and-opt-in.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.
