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

# Privacy Model

ZOKA's privacy model separates public verification from private wallet state.

The public chain provides enough data for consensus, mining, and auditability. The wallet keeps the user-specific view: balance, history, spend authority, and recovery material.

This means the chain can remain publicly verifiable without becoming a public account ledger for every user. Nodes can reject invalid blocks and double spends, while wallets decide which encrypted outputs belong to the local user.

## Summary

| Hidden from public explorer          | Public for consensus                    |
| ------------------------------------ | --------------------------------------- |
| Sender                               | Block height                            |
| Receiver                             | Block hash                              |
| Amount                               | Timestamp                               |
| Wallet balance                       | Proof-of-work metadata                  |
| Address history                      | Commitments and nullifiers              |
| Recovery phrase, scan key, spend key | Public transaction or private tx hashes |

## Design Goal

The goal is not to hide the existence of the blockchain. Blocks, mining, supply, and network health are public. The privacy model focuses on preventing public infrastructure from turning private payments into searchable sender, receiver, amount, and balance records.


---

# 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:

```
GET https://zokanetwork.gitbook.io/zokanetwork/privacy.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.