> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/form-settings/privacy.md).

# Privacy

Handing privacy is an important part of the data collection process and ngSurvey offers several features to let you customize the way you set your policies and notify your respondents about it. Using the privacy tab you can setup following policies.

{% hint style="info" %}
Privacy options can also be set globally for all accounts and surveys from the [sytem settings](/installation-setup/system-settings.md) page.
{% endhint %}

## 🕶️ **GDPR** 

Enabling the GDPR will enable a link that will be displayed on each of your survey pages footer. This link will open a dialog that will show to the respondent your [GDRP](https://gdpr.eu/what-is-gdpr/) policy.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MO7zmgiPq_eTVH8qHwY%2F-MOAhdQavyt8zzrljMa_%2Fimage.png?alt=media\&token=eafebeff-8cb0-4605-ad39-462badca6d7f)

## 🔅 GDRP properties

* **`Popup link label`** label of the link that will be displayed on the survey footer.
* **`Popup title`** title displayed in the header of the policy dialog window.
* **`GDPR policy`** your company GDPR policy.

{% hint style="warning" %}
If you're collecting data from EU based respondents it is mandatory to comply with GDPR and setup a GDRP policy on your surveys that informs about the respondents rights and let them know a focal point where they can ask for access, deletion or modification of their personal collected data.
{% endhint %}

## 🍪 **Cookie consent**

Enabling cookie consent will display a banner on the bottom of the respondent's browser that will let him display your company cookies policy in a dialog window. You may check out the [privacy checklist](/form-management/form-designer/form-settings/privacy/privacy-checklist.md) to see the information ngSurvey sets on the respondent browser.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MOAj1-p6ylGRtfT5QH_%2F-MOAkOIebJmRr7wYCZa_%2Fimage.png?alt=media\&token=24c57f6c-f12d-43a2-ae24-36a19030c140)

## 🔅 Cookie consent properties

* **`Banner text`** text that will be displayed in the footer's banner.
* **`Popup title`** title displayed in the header of the cookie consent dialog window.
* **`Consent policy`** your company cookie consent policy.


---

# 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.ngsurvey.com/form-management/form-designer/form-settings/privacy.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.