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

# User guide

The Privacy Portal is COTI V2's user-facing `dApp` for interacting with tokens on COTI, letting you bridge between Public tokens and [PrivateERC20](/coti-documentation/coti-privacy-portal/developer-guide/privateerc20.sol.md) tokens.

It allows you to work with two types of tokens:

## Public Tokens

Public Tokens behave like standard blockchain tokens:

* balances are visible on-chain
* transactions are transparent

## Private Tokens

Private Tokens add an extra layer of privacy:

* balances are stored encrypted on-chain
* you decrypt and view them locally using your wallet and the COTI MetaMask Snap

This helps keep your financial data confidential.

## What you’ll learn

This guide will walk you through how to:

* connect your wallet to the Privacy Portal
* [onboard](/coti-documentation/build-on-coti/core-concepts/what-is-onboarding.md) so private features can unlock
* bridge public tokens into private tokens
* send and receive private transactions
* view your balances securely

## Why use the Privacy Portal?

The Privacy Portal lets you move your tokens into a private state, giving you more control over what information is visible on-chain while keeping sensitive data confidential.


---

# 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://docs.coti.io/coti-documentation/coti-privacy-portal/user-guide.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.