> 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/privacy-records-beta.md).

# Privacy records (Beta)

{% hint style="warning" %}
**Note**: Currently, privacy records do not support DSAR events and API events.
{% endhint %}

A privacy record tracks the evolution of an end-user's consent and preference selections, and data requests. These records are retrievable, accessible, and downloadable from the Didomi console by clicking **Versions & Proofs** on the left-hand panel and selecting the **Privacy Records** tab.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FcCbKArsY6uKzcMFsJSIB%2FScreenshot_2026-05-08_at_1_23_06%E2%80%AFPM.jpg?alt=media&amp;token=0fa4d9d9-40f5-4e38-8598-7a4f373db83c" alt="" width="563"><figcaption></figcaption></figure>

On the subsequent page, your organization can request a privacy record and manage any existing privacy record requests. For each request, your organization can find the following information:

<table><thead><tr><th width="187.33343505859375">Field</th><th>Description</th></tr></thead><tbody><tr><td>Status</td><td>Current status of the request. <a href="https://docs.didomi.io/versions-and-proofs/privacy-records-beta/privacy-record-status-glossary.md">Click here</a> for more information.</td></tr><tr><td>User ID</td><td>User ID used for the request. Will be empty if request was made with Organization User ID</td></tr><tr><td>Organization User ID</td><td>Organization User ID used for the request. Will be empty if request was made with User ID</td></tr><tr><td>Date of Request</td><td>Initial date of when the request was made</td></tr><tr><td>Last Update</td><td>Latest date of when the request was updated</td></tr><tr><td>Record Deleted in</td><td>30 day count down from the last update date at which time the record will be deleted. <a href="https://docs.didomi.io/versions-and-proofs/privacy-records-beta/privacy-record-deletion.md">Click here</a> for more information.</td></tr><tr><td>Choices Record</td><td>Number of events recorded for the User ID/Organization User ID</td></tr></tbody></table>

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2Fv6TH51AOK3TJ2ezLSWMj%2FScreenshot_2026-05-13_at_10_07_07%E2%80%AFAM.jpg?alt=media&amp;token=c26a4491-63e2-4190-956b-eb3e73bc79d6" alt="" width="563"><figcaption></figcaption></figure>

***

### Resources

See the following articles for more information on privacy records:

* [Generate privacy record](https://docs.didomi.io/versions-and-proofs/privacy-records-beta/generate-privacy-record.md)
* [Privacy record status glossary](https://docs.didomi.io/versions-and-proofs/privacy-records-beta/privacy-record-status-glossary.md)
* [Privacy record deletion](https://docs.didomi.io/versions-and-proofs/privacy-records-beta/privacy-record-deletion.md)
* [Update privacy record](https://docs.didomi.io/versions-and-proofs/privacy-records-beta/update-privacy-record.md)
* [Download privacy record](https://docs.didomi.io/versions-and-proofs/privacy-records-beta/download-privacy-record.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 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/privacy-records-beta.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.
