> For the complete documentation index, see [llms.txt](https://docs.keyring.network/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keyring.network/docs/protocol-guide/data-flow/data-collected.md).

# Data Collected

## **User Compliance Data**

**Definition:** Datapoints collected from users as part of onboarding, including Personally identifiable information (PII).

**Use of data:** Used for the core purpose of our solution. Keyring does not share any PII or data outside of its core use case and never sells it. At a User’s request, Keyring may also use the contact information provided upon onboarding to keep them updated on their onboarding status.

## **Usage Analytics Data**

**Definition:** Data points collected from Users’ usage of Keyring, such as cookies or anonymised website usage data.

**Use of data:** Used in a range of ways to improve user experience on the Keyring’s interface, including keeping users signed in, and understanding how they use our app and website for internal analytics.

<details>

<summary>What types of cookies are used? </summary>

* Strictly necessary cookies. These are cookies that are required for the operation of our website. These essential cookies are always enabled because our website won’t work properly without them. They include, for example, cookies that enable you to log into secure areas of our website.
* Analytical or performance cookies. These allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it.
* Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region).

</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 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.keyring.network/docs/protocol-guide/data-flow/data-collected.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.