> 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/generate-privacy-record.md).
# Generate privacy record
A privacy record tracks the evolution of an end-user's consent and preference selections, and data requests. In this article, we will cover how to generate an end-user's privacy record using that user's user ID or organization user ID.
Click **Versions & Proofs** on the left-hand panel and select the **Privacy Records** tab on the subsequent page.
Use the provided field to select whether the end-user for whom you are generating a privacy record report be identified by a **User ID** or an **Organization User ID** (configured by your organization when implementing the SDK).
Input the value for the ID in the provided field and click **Generate Record** when finished.
Once the request is finished processing, an email will be generated to the email address associated with your Didomi account and the results posted to the privacy records page.
---
# 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/generate-privacy-record.md?ask=&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.
