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

# Legal and risks

> How MixFun handles risk, custody, and user responsibility.

{% hint style="danger" %}
**Irreversibility.** All deposits, withdrawals, and transfers on Solana are final. MixFun cannot reverse, refund, or recover a transaction. Keep your note safe. Double-check recipient addresses before signing.
{% endhint %}

## Non-Custody

MixFun is a non-custodial protocol running on Solana. MixFun does not hold user funds, maintain balances, or act as a counterparty. Every deposit, withdrawal, and transfer settles on Solana under the control of the signer (you, a note holder, or an optional relayer acting on a proof you generated).

Pools are on-chain program accounts. The program enforces deposit, withdrawal, and fee logic. No operator can freeze a pool, seize a deposit, or redirect a withdrawal.

## User Responsibility

MixFun is a protocol, not a service. Users are responsible for:

* **Note custody.** Lost notes equal lost funds. MixFun cannot recover them.
* **Jurisdictional compliance.** Privacy protocols have different legal status in different places. Users are responsible for understanding the rules that apply in their jurisdiction.
* **Verifying transactions.** Always verify amounts, recipients, and token mints before signing.
* **Wallet security.** MixFun never asks for your seed phrase or private key. If any page or service prompts you for either, close it and verify the URL.

## Privacy Characteristics

MixFun hides the link between a deposit and a withdrawal. It does not hide:

* **That you interacted with MixFun.** Deposit and withdrawal transactions are on-chain and publicly visible.
* **The deposit amount.** Pool denominations are public. Private Swap commits the exact amount into the deposit record. Stealth Transfers leak the amount because the payment is a direct on-chain transfer.
* **The pool you used.** Pool addresses are public. Using an unusual denomination narrows the anonymity set.
* **Correlation signals.** Time-correlation, wallet reuse, and identifying metadata can defeat anonymity-set protection. See [Anonymity sets](/mixfun/concepts/anonymity-sets.md).

## Data Practices

MixFun stores:

* **Encrypted notes** if you sign in. Encryption happens on your device. MixFun stores only the ciphertext.
* **Per-user transaction history** if you sign in. Derived from on-chain transactions your wallet signed.
* **Server logs** for requests made while you use MixFun, as is standard for any web service.

MixFun does not sell, share, or build profiles from user data.

## Intended Use

MixFun is built for legitimate privacy needs: paying contributors discreetly, receiving into unlinked wallets, protecting treasury movements from public analysis. It is not built to evade sanctions, platform restrictions, or law enforcement authority, and MixFun does not support such use.

## This page is not legal advice

This document describes how the protocol works and what user responsibilities are. It is not legal advice and does not cover every jurisdiction. Consult local counsel for specific regulatory questions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://mixfun.gitbook.io/mixfun/support/legal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.