> 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/how-are-the-jentis-cookies-used-and-how-long-are-they-stored.md). # How are the JENTIS Cookies used and how long are they stored? With JENTIS, the Customer can collect its users’ data as first-party data via the JENTIS JavaScript, which sets the JENTIS first-party cookies. In line with its role as a data processor under GDPR, JENTIS provides full control to the Customer over the software configuration. Therefore, the purpose and use of JENTIS first-party cookies, as well as their storage duration, remain at the discretion of the Customer. JENTIS cookies can be configured as session cookies or as persistent cookies, with a maximum storage duration of up to 24 months. Detailed information on what cookies are set and their functionality can be found in our [**JENTIS Developer Documentation**](/core-concepts/jentis-cookies.md)**.** --- # 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.jentis.com/privacy-documentation/frequently-asked-questions/how-are-the-jentis-cookies-used-and-how-long-are-they-stored.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.