# Introduction zCloak is a web3 privacy identity company focused on exploring and building the RWI (Real-World Identity) infrastructure in the Web3 world. We aim to transfer user data sovereignty from centralized data centers to the users themselves at the storage and computation level. Our team consists of professional cryptographers and developers with a strong pioneering spirit, continuously exploring the field of privacy identity with a focus on BUIDL. Our motivation stems from the realization of self-sovereign digital identities in Web3. In the system we build, we enable the creation, use, and management of an entity's identity, independent and unconstrained by centralized organizations or states. Motivated by this, and in line with W3C standards, we have proposed solutions involving DID (Decentralized Identity Document), VC (Verifiable Credentials), and ZKP (Zero-Knowledge Proof). Users need not worry about personal data leaks; all private data remains in their control. When personal data is required, users can demonstrate their compliance with requirements using local zero-knowledge proof technology or VP (Verifiable Presentation), ensuring that no one, except the user, knows their data. This document introduces our main infrastructure protocols and the related API usage. Through this document, you will understand our underlying protocols and how to use our accompanying SDK. In the SDK usage section, we provide various application scenarios to help you quickly get started and gain flexible mastery. Welcome to join our journey, let's together create a realm of privacy in the Web3 world. --- # Agent Instructions: 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: ``` GET https://docs.zcloak.network/about-zcloak/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.