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.


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:


πŸ”š 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.

Last updated