> 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/versions-and-proofs/consent-proofs-reports.md).

# Consent proofs reports

When an end-user provides consent for your organization's website/application, Didomi stores proof of the consent in our databases. This consent proof is retrievable by your organization if you ever have to produce documentation regarding an end-user's consent as a response to an individual request or supervisory audit.

{% hint style="warning" %}
**Note**: Consent proof reports only retrieve end-user consent proofs that were generated via the SDK and not proofs created directly via the Didomi API.

Didomi stores end-user consent proofs for a period of 5 years and is retrievable 24-hours after the end-user has provided their consent selections.&#x20;
{% endhint %}

<details>

<summary>Respond to supervisory authority</summary>

If your organization is responding to a request from a supervisory authority, Didomi can provide individual proofs of consent for all of your organization's end-users as well as notice configurations for the domain under review. The process Didomi will follow is below:

1. Didomi will do a complete export of your organization's end-user consent base via API&#x20;
2. Notice versions can be retrieved by your organization via API (if you used the Didomi console to manage consent notices)

</details>


---

# 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.didomi.io/versions-and-proofs/consent-proofs-reports.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.
