> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/cookies.md).

# Manage cookies consent

Learn how to set up a good management of consent to cookies.

## What are cookies?

[Cookies](https://en.wikipedia.org/wiki/HTTP_cookie) are small files that store information about a user visiting a website, for example their browsing history, site settings, etc.

The French data protection authority (CNIL) defines a cookie as follows:

> A cookie is a series of information, usually small and identified by name, which can be transmitted to your browser by a website on which you connect. Your web browser will keep it for a certain period of time, and send it back to the web server each time you reconnect to it.

The General Data Protection Regulation (GDPR), which applied from May 25, 2018, reinforced the requirements for valid consent set out in [article 82 of the French "Informatique et Libertés" law](https://www.cnil.fr/fr/la-loi-informatique-et-libertes#article82) (in French), which transposes Directive 2002/58/EC on privacy and electronic communications ("ePrivacy"). It requires, except in specific cases, that you collect the consent of users before any operation of writing or reading cookies and other trackers.

In early 2020, the CNIL published [recommendations on cookies and other trackers](https://www.dastra.eu/fr/article/recommendations-CNIL-cookies-expliquees-a-votre-boss/104) (article in French).

Compliance with cookie consent can be ensured by a cookie consent banner.

{% content-ref url="/pages/-M378oB2HodWBFfDdJsg" %}
[Set up the cookie consent banner](/en/features/cookies/banner/configure.md)
{% endcontent-ref %}


---

# 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://doc.dastra.eu/en/features/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.