> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/privacy-documentation/frequently-asked-questions/is-consent-required-for-the-setting-of-the-jentis-cookies.md).

# Is consent required for the setting of the JENTIS cookies?

As a general rule. under EU ePrivacy Directive, user consent is required for any access to or storage of information on a user's device, such as setting a cookie. In exceptional cases, the consent is not required for “technical storage or access” or for access to the user device that is “strictly necessary”.

With JENTIS Customers have the technical capacity to granularly configure data capture in both scenarios: when a user gives explicit consent and when a user does not give consent. This is possible with [**JENTIS Essential Mode**](/privacy-documentation/jentis-and-privacy-use-cases/essential-mode.md)**.** This ensures that the application of consent rule for data processing, as well as consent exceptions is implemented in a compliant and effective manner.


---

# 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.jentis.com/privacy-documentation/frequently-asked-questions/is-consent-required-for-the-setting-of-the-jentis-cookies.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.