> For the complete documentation index, see [llms.txt](https://phemex.gitbook.io/phemex-web3-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://phemex.gitbook.io/phemex-web3-whitepaper/concepts/privacy.md).

# Privacy

As a soulbound token, the [Phemex Soul Pass](/phemex-web3-whitepaper/features/phemex-soul-pass.md) and its metadata are present and verifiable on-chain. Initially, this on-chain data will be fully public but we are keeping a close eye on the technological strides being made in the field of programmable privacy. In the future, if Phemex Soul Pass holders do not want their PSP information to be public, one option can be to store the data off-chain while leaving a hash of it on-chain. The PSP holder would then be able to reveal the contents of their Soul Pass only when they want to.&#x20;

Another method to enhance SBT privacy is through zero-knowledge proofs. Since ZKPs can be used to prove the veracity of an arbitrary statement without revealing anything more than the statement itself, they enable SBT holders to prove their legitimacy without having to expose their identity or SBT metadata. Designated-verifier proofs and verifiable delay functions are additional powerful mechanisms that build on top of ZKP as mentioned in [Weyl, Ohlhaver, and Buterin’s paper on Decentralized Society](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4105763). As cryptographic techniques continue to develop regarding privacy, Phemex will assess their viability and look to apply them to the Phemex Soul Pass.&#x20;


---

# 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://phemex.gitbook.io/phemex-web3-whitepaper/concepts/privacy.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.
