> For the complete documentation index, see [llms.txt](https://docs.demos.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.demos.global/onlymeid/user-privacy-and-safety.md).

# User Privacy & Safety

At DEMOS, we prioritize a no-KYC approach to Proof of Personhood, ensuring that users' privacy, security, and autonomy remain central to our operations. OnlyMeID embodies this ethos by implementing internal procedures and practices designed to maximize user privacy and minimize potential security risks.

It's crucial for OnlyMeID users to comprehend the scope and purpose of the data they provide. This transparency fosters informed decision-making and reinforces trust in our system.

#### <mark style="color:yellow;">User Information Stored:</mark>

* User Selfie: For enrollment, a snapshot from the live session is stored to enable AI-driven uniqueness checks. This ensures each user is distinct, supporting our system's scale and accuracy.
* Blockchain Address: The connected wallet address is stored to facilitate Proof of Liveness features, linking digital identity with blockchain activities.

<br>


---

# 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.demos.global/onlymeid/user-privacy-and-safety.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.
