> For the complete documentation index, see [llms.txt](https://hinkal-team.gitbook.io/hinkal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hinkal-team.gitbook.io/hinkal/security-and-compliance/compliance.md).

# Compliance

Hinkal is built to stay a viable option for regulated entities.

Compliance runs on both ends of a transaction: funds are screened on the way in, and activity can be disclosed on the way out.

#### **Screening at Entry**

Every deposit is screened against Chainalysis before it enters the private balance, and gets a unique depositId, permanently linked to the depositor's wallet address at the time of deposit.

To deposit, transfer privately, or withdraw, a user generates a zero-knowledge proof that their funds aren't associated with any depositId tied to a sanctioned or high-risk address. The proof is verified against the current Chainalysis state, never a snapshot from deposit time.

The contract verifies the funds without revealing identity, balances, or transaction history. For anyone not flagged, privacy stays fully intact.

Screening is of wallet addresses, not identity. **Hinkal performs no KYC and collects no personal information.**

***

#### **Continuous re-screening**

Hinkal integrates directly with Chainalysis for **real-time re-screening**:

* Depositor addresses are re-evaluated automatically as new intelligence, sanctions, or risk signals emerge
* No reliance on static point-in-time checks at deposit
* Compliance status of funds evolves in sync with global regulatory datasets

Proofs run against the live screening state, so **protection extends** to funds already deposited:

* If a depositor address is flagged after funds have entered Hinkal, those funds immediately lose eligibility for private transfers
* That depositor can only withdraw publicly, back to the original address tied to the depositId
* The resulting flow is fully traceable and auditable

Funds leaving Hinkal's private balance are pre-verified against the latest compliance data - something exchanges, DeFi protocols, and counterparties can rely on.

***

#### **Selective Disclosure**

**Users control who sees their activity.**

Two mechanisms cover audit, reporting, and regulatory requests:

* **Viewing keys** - share full transaction history, or a specific set of transactions or time range, with an auditor, regulator, or counterparty
* **Downloadable transaction history** - export a complete record of your own activity when required

***

#### **What Hinkal Is Not**

Hinkal is **not** a mixer. Funds are **never** pooled with other users', every deposit stays permanently linked to the address that made it, and the protocol enforces screening rather than bypassing it.