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

# Sign In & Wallets

PolyPoll paper mode uses Privy authentication.

## Do I need a wallet?

No. A wallet is optional in paper mode.

You can sign in with:

* email
* Google
* a wallet you already use

## Why would I still connect a wallet?

A wallet can still be useful for:

* keeping the same identity across sessions
* preparing for future wallet-aware features
* matching the account you use elsewhere in the app

## What matters in paper mode

Your paper bankroll, positions, and history live in the **paper backend**, not in an onchain wallet balance.

That means:

* no USDC approvals
* no gas requirement
* no bridge step

## Wallet mismatch protection

When the app does require an authenticated wallet action, the paper API checks that the signed-in Privy wallet matches the requested actor.


---

# 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://polypoll.gitbook.io/polypoll-docs/user-guide/connecting-your-wallet.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.