> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/identity-and-privacy-foundations/from-identity-theft-to-control-rethinking-personal-data-ownership/what-is-a-decentralized-identity.md).

# What is a Decentralized Identity?

A decentralized identity (DID) system gives individuals control over their identity data. It uses **cryptographic tools to store credentials securely on personal devices or decentralised storage systems**, rather than a central database. 

**Each person manages their own** digital wallet for credentials—such as a driver’s license, university degree, or medical record; which is referred to as 'Self Sovereign Identity'. These credentials are verifiable, selectively shareable, and revocable.  

Instead of proving your identity by handing over a copy of your ID, **you share only the data that is needed, called 'selective disclosure'**. For example, proving you are over 18 without revealing your birthdate. (You can learn more about BSV's underlying privacy mechanisms, like Zero-knowledge proofs in the Path, "BSV's privacy technologies explained".) 

These systems provide privacy, flexibility, and resilience. If a credential is revoked or lost, it can be reissued or replaced without risking the entire identity profile. 


---

# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/identity-and-privacy-foundations/from-identity-theft-to-control-rethinking-personal-data-ownership/what-is-a-decentralized-identity.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.