> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/get-started/general/consent-storage.md).

# Consent storage

End-user consent is stored on the client-side and server-side. However, Didomi does not send HTTP requests to determine the end-user's consent status since we keep a local cache of this data in a cookie (`didomi_token` or `didomi_dcs`).

{% hint style="info" %}
[Click here](/get-started/general/didomi-consent-string-dcs-and-signature.md) to learn more about the cookie stored client-side (`didomi_dcs`)
{% endhint %}

Didomi will perform the following:

1. Check the client-side cookie for consent information.
2. If the information is missing, Didomi will show your organization's consent notice configured for the website.
3. Collected end-user consent will be stored in a client-side cookie and also sent to Didomi servers for long-term storage.


---

# 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.didomi.io/get-started/general/consent-storage.md?ask=<question>&goal=<endgoal>
```

`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.