> 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/privacy/private-vs-public.md).

# What Is Private and Public

VOID improves privacy.

It does **not** make you invisible.

{% hint style="warning" %}
VOID should not be treated as a guarantee of anonymity.

Privacy depends on how you enter, use and exit the private system, as well as the size of the anonymity set.
{% endhint %}

### What VOID Hides

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Private Transfer Details</strong></td><td>Note secrets and transferred amounts are not published on-chain during Private Send.</td></tr><tr><td><strong>Sender → Recipient Link</strong></td><td>The direct sender-to-recipient relationship inside a Private Send is not published on-chain.</td></tr><tr><td><strong>Deposit → Later Spend Link</strong></td><td>A later private spend does not reveal which specific deposit commitment it originated from.</td></tr><tr><td><strong>Wallet on Relayed Actions</strong></td><td>Your wallet is not the on-chain sender for relayed actions: Private Buy / Sell from private balance, Private Send and Withdraw.</td></tr></tbody></table>

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

A Private Send keeps the amount, asset and recipient hidden. If the relayer is unavailable, the app says so and offers a clearly labelled option to submit from your own wallet instead, which pays the ETH gas and appears as the on-chain sender.
{% endhint %}

{% hint style="warning" %}
The ability to obscure links between activity is limited by the size of the anonymity set.

The testnet anonymity set is currently small.
{% endhint %}

### What Remains Public

The following information can still be visible on-chain:

#### Deposits

* wallet address
* token
* amount

#### Private Send

* that a private transfer happened (new commitments and nullifiers)
* the VOID relayer as the transaction sender, not your wallet
* your wallet as the sender only if you choose the fallback to submit from your own wallet

#### Withdrawals

* receiving address
* token
* amount
* the VOID relayer as the transaction sender, not your wallet
* your wallet as the sender only if you choose the fallback to submit from your own wallet

#### Private Buy / Sell

The underlying DEX execution remains public, including:

* market
* amounts
* transaction time

If **Private Buy** is paid from a public wallet, that wallet is visible as the transaction sender.

#### Protocol Activity

The chain can also see:

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

{% hint style="info" %}
VOID hides specific relationships and private-note data.

It does not hide the existence of protocol activity or the underlying public DEX execution.
{% endhint %}

### Who Else Can See Data

#### Hosted Proof Service

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

The service:

* does **not** control your spending key
* cannot authorize a spend by itself
* does receive the prover inputs for the proof request

{% hint style="warning" %}
The current hosted proving model requires trusting the proof service with the inputs used to generate each proof.

**Local browser proving is planned before mainnet.**
{% endhint %}

#### Indexer and RPC Infrastructure

Infrastructure used to access blockchain data may be able to see information such as:

* your IP address
* blockchain data requested by the application
* timing of requests

These services do not receive your wallet private key or seed phrase.

### Privacy Tips

{% hint style="warning" %}
The anonymity set is still small on testnet.

Do not rely on VOID testnet for strong anonymity.
{% endhint %}

#### Avoid Easy Correlation

Timing and amount patterns can make activity easier to correlate.

For example, a distinctive public deposit followed later by a similar-sized withdrawal may provide clues about the relationship between the two.

Delaying a transaction or changing the amount does **not** guarantee unlinkability.

#### Consider the Withdrawal Address

Withdrawing to a wallet already linked to your identity can associate the withdrawal with you.

Once funds leave VOID and return to a public wallet, normal public-chain visibility applies.

{% hint style="info" %}
VOID provides privacy inside the protocol.

Your broader privacy still depends on how you interact with public wallets, exchanges, applications and other identifiable addresses before and after using VOID.
{% 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/privacy/private-vs-public.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.