# Compliance Integrations

**Enterprise grade privacy without built in surveillance.**

While Veilon is built with privacy as the default, it also understands the real world needs of businesses, institutions, and regulated entities. That’s why it offers optional, modular compliance tools designed to be integrated only when needed.

> *Compliance is a feature not a requirement.*

***

### <mark style="color:yellow;">Who It’s For</mark>

* Regulated financial institutions
* Enterprise dApps
* Crypto payroll and treasury platforms
* OTC desks and liquidity providers
* DAOs with KYC/AML requirements

***

### <mark style="color:yellow;">What Veilon Offers</mark>

Veilon’s compliance toolkit is modular, non-invasive, and developer-friendly. Here’s what’s available:

**API Integrations with Leading Compliance Providers**

* Native support for tools like Chainalysis, TRM Labs, and others
* Easy integration via pay-per-use APIs
* Enables origin tracking, blacklist checks, or PoI verification when needed

**View Key Frameworks**

* Users can grant read only access to specific transaction sets
* Enables source of funds validation without revealing full history

**Proof of Innocence (PoI) Integration**

* Automatically verify that funds are **not linked** to blacklisted sources
* 100% zero-knowledge nothing about the user is revealed

***

### <mark style="color:yellow;">Fair Usage Design</mark>

Veilon's compliance features are built to serve those who actually need them and not to burden regular users.

* **Opt in only** — everyday users are never forced into surveillance
* No extra fees unless activated
* **Enterprises pay per request** — usage is not subsidized by the community
* **Transparent design** — no hidden monitoring or default data extraction

> *Privacy remains the default. Compliance is opt-in, modular, and intentional.*

***

### <mark style="color:yellow;">Why It Matters</mark>

In many privacy protocols, enterprise adoption is blocked by a lack of tooling for legal or regulatory frameworks.

Veilon bridges that gap providing the transparency institutions need, without sacrificing user sovereignty or protocol neutrality.

* Maintain privacy where it matters
* Enable traceability only when required
* Keep user control at the center

> *Veilon’s compliance design proves you can be compliant without being surveilled.*


---

# 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.veilon.io/features/compliance-integrations.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.