> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/center/security-and-privacy/document-data-processing-consent.md).
# Document Data Processing Consent
A growing number of digital privacy laws require businesses to ask for consent to data processing. Documenting this in Daylite and filtering out those who have and haven't given consent is an important part of this process.
{% hint style="info" %}
Note: This information is provided as general guidance on how Daylite can support your broader GDPR compliance strategy. It does not constitute legal advice. For tailored advice or to ensure full compliance with GDPR, we recommend consulting your legal counsel.
{% endhint %}
### Documenting Consent
You can use keywords in Daylite to track which contacts have provided consent.
1. Open Daylite and choose **Settings** > **Keywords**
2. Choose **People**
3. Click **+**
4. Name the Keyword `Consent Given`
Now you can add the `Consent Given` keyword to any record who has given you consent to process their data
**Showing Contacts That Have Not Given Consent**
To create a Smart List of contacts who have not given consent, set the filter conditions do not include the Keyword "Consent Given."
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.daylite.app/help/center/security-and-privacy/document-data-processing-consent.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 `build a script that syncs our docs to a CMS` 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.