> 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.