# Compliant Privacy

Compliant privacy is a concept that aims to strike a balance between the need for privacy in digital transactions and the requirement to adhere to regulatory standards. In the context of blockchain technology and dApps, compliant privacy refers to the ability to maintain user privacy while ensuring that transactions and interactions within the network meet the necessary regulatory requirements. This balance is crucial for fostering innovation, trust, and security in the blockchain ecosystem.

The cryptography of zero knowledge proofs (ZKPs), and the tech stack that evolved around it, provide the base from which both privacy and compliance may be achieved; with the ideal situation being one in which a user would be able to prove with full mathematical certainly aspects of their identity, transactional history, reputation and financial good standing to other on-chain entities, regulated or otherwise, without disclosing any private information.&#x20;

On the other hand, with the use of zk stack, the said on-chain entities would be able to pre-set programmable rules of interactions (such as only KYC’ed accounts can interact) creating sorts of dynamic whitelists (who can and cannot interact) and conditions of this interaction (different terms depending on one’s web3 footprint).

Galactica Network bridges the void between Web3's founding principles and the need for regulation by enabling compliance and privacy to coexist on-chain. In doing so, the protocol succeeds in solving fundamental issues related to privacy, sovereignty, and safety across the realms of both decentralized and traditional finance. Distributed ledgers are superior to traditional finance tech stacks, enabling more effective self-regulation, composability, and financial sovereignty. You can find more information about the concept of Compliant Privacy in one of our articles [here](https://galactica.com/news/at-the-intersection-of-privacy-and-compliance).


---

# 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.galactica.com/galactica-network-faq/2.-galactica-networks-core-pillars/compliant-privacy.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.
