# Privacy Policy

At **Decontext**, your privacy is not just respected — it’s fundamentally architected into the system. As a decentralized protocol, **Decontext does not collect, store, or process any personal data** unless explicitly provided through user interaction with integrated applications.

***

### 1. 🔄 Data Collection

**Decontext does not collect:**

* Personal identifiers (name, email, IP address)
* Device or location data
* Off-chain usage logs

All interactions occur on-chain or via user-controlled interfaces such as wallets or agents.

However, third-party dApps or agents using Decontext may:

* Store user-inputted metadata (e.g., context values)
* Request permissions to access wallet or context modules

> These third-party applications are responsible for their own data practices.

***

### 2. 🧠 Context Data

Context entries (e.g., `user.reputation`, `dao.activity`) are:

* **Publicly verifiable** when published to chain
* **Fully owned by the user**
* **Permissioned** via the DMCP protocol (only authorized parties can update)

No personal identifiers are ever required to interact with context modules.

***

### 3. 🔐 Zero-Custody Guarantee

Decontext:

* Does **not hold** any user private keys
* Does **not track** or profile users
* Ensures full **data sovereignty** via cryptographic signatures

***

### 4. 🛡️ ZK Context (Future Upgrade)

For sensitive use cases, Decontext will support **Zero-Knowledge Proofs (ZKPs)**, enabling users to prove facts about their context (e.g., score thresholds, activity patterns) without revealing the underlying data.

This ensures privacy **without compromising verifiability**.

***

### 5. 🔗 Third-Party Links

This documentation and ecosystem may reference third-party tools, SDKs, and applications. Please review their privacy policies individually, as Decontext does not control their behavior.

***

### 6. 📞 Contact

For governance-related privacy concerns or protocol-related questions, reach out via the Decontext DAO or through official communication channels:

* GitHub: [github.com/decontextai](https://github.com/decontextai)
* Twitter: [https://x.com/DecontextAI](https://x.com/DecontexAI)
* Telegram: <https://t.me/decontext>

***

### 🔚 Summary

Decontext is built to respect **user sovereignty, transparency, and trustlessness**. Privacy is not added as an afterthought — it's embedded into the protocol design.

> You own your data. We simply make it composable.


---

# 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.dctx.ai/other/privacy-policy.md?ask=<question>
```

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.