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

# Compliance

## Privacy, Compliance & Acceptable Use

VOID is a **non-custodial privacy layer on Robinhood Chain**.

It is designed to reduce public exposure of financial activity between deposit and withdrawal where the protocol allows, while deposits and withdrawals remain public blockchain transactions.

This page explains:

* what is visible on-chain
* what VOID infrastructure can see
* current privacy limitations
* protocol safeguards
* acceptable use
* the powers and limits of the VOID team

{% hint style="warning" %}
VOID is currently **unaudited testnet software** running on Robinhood Chain Testnet, **Chain ID 46630**.

Mainnet is planned but has no confirmed launch date.

All testnet tokens have **no monetary value**.
{% endhint %}

### Who Can See What

| Activity               | Public Blockchain                                           | VOID Services                                    | User                         |
| ---------------------- | ----------------------------------------------------------- | ------------------------------------------------ | ---------------------------- |
| **Deposit**            | Wallet, token, amount and timing                            | Public transaction data                          | Full details                 |
| **Private Send**       | Commitments, nullifiers and VOID relayer as sender          | Hosted prover receives proof inputs              | Full details                 |
| **Private Buy / Sell** | Underlying DEX market, amounts, time and relayer            | Hosted prover and relayer process required data  | Full details                 |
| **Withdrawal**         | Receiving address, token, amount and VOID relayer as sender | Public transaction data                          | Full details                 |
| **Private Balance**    | Not published as a readable balance                         | Encrypted-note infrastructure supports discovery | User can decrypt owned notes |

Also visible on-chain:

* commitments
* nullifiers
* Merkle roots
* contract calls
* the VOID relayer address

{% hint style="info" %}
For relayed actions such as **Private Buy / Sell from private balance**, **Private Send** and **Withdraw**, the VOID relayer appears as the on-chain sender instead of the user's wallet.

A Private Send does not reveal the amount, asset or recipient. If the relayer is unavailable, the user can choose to submit from their own wallet instead, which then appears as the on-chain sender.
{% endhint %}

#### Testnet Anonymity Set

The anonymity set on testnet is still small.

Timing and amount patterns may make it possible to correlate a public deposit with later activity or a withdrawal.

{% hint style="warning" %}
Do not rely on the current testnet for strong anonymity.
{% endhint %}

## Privacy Limitations

VOID reduces public exposure, but it does **not** make every part of a transaction invisible.

### Deposits & Withdrawals

Deposits and withdrawals remain public blockchain transactions.

Information that may be visible includes:

* wallet or receiving address
* token
* amount
* transaction timing

Withdrawals are submitted by the VOID relayer on testnet, so the relayer, not your wallet, is the transaction sender. If you choose to submit from your own wallet, your wallet is visible as the sender.

### Private Buy / Sell

When a trade is executed from private balance through the VOID relayer, the user's wallet is not the direct on-chain sender.

However, the underlying Uniswap trade remains public.

This means the following may still be visible:

* market
* amounts
* execution time
* liquidity pools used
* VOID relayer as transaction sender

{% hint style="info" %}
Private trading protects the direct link between your wallet and private balance.

It does **not hide the underlying DEX execution**.
{% endhint %}

### Timing & Amount Correlation

Timing and amount patterns may sometimes be used to infer relationships between:

* public deposits
* private activity
* later withdrawals

Privacy generally improves as the shielded pool and anonymity set grow.

Delays or amount changes do **not** guarantee unlinkability.

## Proving Your History

Every VOID address has a **viewing key**.

Private notes are encrypted to that key, and the VOID app uses it inside your browser to discover and read notes belonging to you.

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Viewing Key</strong></td><td>Can read private notes belonging to the user.</td></tr><tr><td><strong>Spending Key</strong></td><td>Required to authorize spending of private notes.</td></tr></tbody></table>

{% hint style="info" %}
A viewing key can read notes.

It cannot spend them.
{% endhint %}

### Selective Disclosure

Sharing or exporting viewing information for selective disclosure is planned but is **not currently live**.

The app does not currently:

* display your viewing key
* export your viewing key
* allow you to share your viewing key

Association sets are also not currently enforced.

The testnet registry uses a **placeholder association root**.

Until selective disclosure is available, parts of a user's transaction history can still be demonstrated through public blockchain activity:

* deposits are visible on the Robinhood Chain explorer
* withdrawals are visible on the Robinhood Chain explorer
* Private Buy / Sell executes through public DEX liquidity

{% hint style="info" %}
Moving proving into the browser will prevent the hosted prover from receiving private proof inputs.

It will **not change what is publicly visible on-chain**.
{% endhint %}

## What VOID Services Keep

### Encrypted Notes

The app downloads encrypted notes through the indexer and attempts to decrypt them locally inside the user's browser.

The indexer therefore does not inherently know which encrypted notes belong to a specific user.

### Proof Service

The hosted proof service receives the proof inputs required to generate a zero-knowledge proof.

Operational logs may include:

* job status
* timing information

The service is not intended to log private proof inputs themselves.

{% hint style="warning" %}
The hosted proof service still receives prover inputs while generating the proof.

Local browser proving is planned to remove this privacy dependency.
{% endhint %}

### Relayer

The relayer keeps limited job information so that it can track and retry dropped transactions.

This may include:

* hash of transaction data
* job status
* transaction hash

### Web Infrastructure

VOID web infrastructure may retain standard access logs.

These may include information such as:

* IP address
* request timing
* requested resources

### Faucet

On testnet, the faucet records wallet and network claim activity required to enforce daily limits.

## Protocol Safeguards

VOID includes protocol-level protections intended to reduce the ability of any single service or administrator to control user funds.

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Zero-Knowledge Proofs</strong></td><td>Private spends require a valid proof verified on-chain.</td></tr><tr><td><strong>Nullifiers</strong></td><td>Prevent the same note from being spent twice.</td></tr><tr><td><strong>Asset Registry</strong></td><td>Restricts the protocol to supported assets.</td></tr><tr><td><strong>Non-Upgradeable Pool</strong></td><td>The main pool contracts are not upgradeable through a proxy.</td></tr><tr><td><strong>Emergency Pause</strong></td><td>Can stop new private activity without blocking withdrawals.</td></tr></tbody></table>

{% hint style="success" %}
A protocol pause is designed to stop new private activity **without trapping users inside the pool**.

Withdrawals remain available.
{% endhint %}

### Safe-Controlled Settings

A multisig Safe controls certain protocol settings on testnet, including:

* supported assets
* supported trading pairs
* fees
* minimum trade sizes
* association-set roots
* protocol pause

These powers do **not** allow the Safe to spend or take ownership of user private notes.

## Acceptable Use

Financial privacy is a legitimate and normal expectation.

VOID is designed to help users reduce unnecessary public exposure of their financial activity.

It must not be used to facilitate unlawful activity.

### VOID Is Built For

* keeping balances, salary and savings out of unnecessary public view
* paying people without exposing an entire wallet history
* trading without directly broadcasting wallet positions
* reducing unnecessary financial tracking
* protecting users from profiling based on public wallet activity

### VOID Must Not Be Used For

* moving proceeds of crime or concealing their origin
* evading sanctions
* use by or for sanctioned persons or entities
* financing terrorism
* fraud
* scams
* theft
* activity prohibited by applicable law

By using VOID, you confirm that:

* you are not a sanctioned person
* you are not acting on behalf of a sanctioned person or entity
* you will comply with the laws that apply to you
* you remain responsible for your own tax and reporting obligations

{% hint style="warning" %}
Privacy does not remove legal responsibility.

Users remain responsible for complying with the laws, sanctions requirements, tax obligations and reporting requirements that apply to them.
{% endhint %}

## What the VOID Team Can and Cannot Do

### The VOID Team Can

* explain how the protocol works
* explain what information is public on-chain
* pause deposits, Private Sends and private trades through the testnet Safe while an issue is investigated
* manage supported assets, trading pairs and certain protocol settings through the Safe
* publish and revoke association-set roots
* point users to public deposit, withdrawal and trading transactions

### The VOID Team Cannot

* spend a user's private notes
* move a user's private balance
* seize a user's private notes through an admin function
* read a user's private balance from public blockchain data
* upgrade the existing pool contracts in place through a proxy

## Frequently Asked Questions

### Is VOID a mixer?

No.

VOID provides a **private balance** that users can deposit into and use for supported private actions such as:

* Private Send
* Private Buy
* Private Sell

Deposits and withdrawals remain public, and private spends are validated on-chain using zero-knowledge proofs.

### Can VOID freeze or seize my funds?

The VOID protocol does not contain a function that allows the team to spend or move a user's private notes.

There is also no per-user freeze function in the VOID private pool.

The protocol pause can stop:

* deposits
* Private Sends
* private trades

It does **not stop withdrawals**.

However, there are important external and protocol-level considerations.

#### Association Sets

The Safe controls the association-set registry used by the protocol.

Association-set enforcement is not currently live on testnet.

#### Underlying Assets

Supported assets may retain their own issuer-level controls.

For example, **USDG may be frozen by its issuer**, including USDG held inside the VOID contract.

{% hint style="warning" %}
VOID cannot override controls built into an underlying token by its issuer.
{% endhint %}

### Is it legal to use VOID where I live?

Rules governing privacy technology differ between jurisdictions and may change over time.

You are responsible for complying with the laws that apply to you, including:

* sanctions requirements
* tax obligations
* financial reporting requirements
* any restrictions applicable in your jurisdiction

If you are uncertain about your obligations, seek advice from a qualified professional.

## Contact

For compliance and law-enforcement enquiries:

**<contact@void-protocol.com>**

***

**Last reviewed:** 19 October 2026

{% hint style="info" %}
This page explains how VOID works and the rules for using it.

It is **not legal advice**.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://void-protocol-2.gitbook.io/void-protocol-docs/security/compliance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.