> 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/user-autonomy-and-control.md).

# User Autonomy and Control

In our commitment to user privacy and autonomy, DEMOS offers a feature known as the "Permissionless Purge." This functionality empowers users with the ultimate control over their data, allowing them to delete their enrollment in OnlyMeID without needing permission from any external authority. Here's a closer look at how this process works and the safeguards we've implemented to prevent misuse while ensuring user autonomy.&#x20;

<mark style="color:yellow;">**Permissionless Purge**</mark>: Users can delete their enrollment after a minimum period (one week), ensuring the integrity of our Sybil resistance while respecting user autonomy.


---

# 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/user-autonomy-and-control.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.
