# Ask for less.

Source: https://docs.privatar.app/permissions

Permissions describe what a site may request. The wallet user chooses whether to grant them.

## Available permissions

| Permission | Allows | Does not allow |
| `addresses` | Read public addresses for the approved account and network. | Reading the recovery phrase or private keys. |
| `balances` | Request actual wallet balance data. | Spending or approving a transaction. |
| `signData` | Request a supported sign-in challenge signature. | Silent signing, arbitrary transaction approval, or unrestricted spending. |
| `transactions` | Request separately reviewed intents, contract balancing, signing and submission on Preview. | Silent execution, Mainnet approval, or unrestricted spending. |
| `proving` | Request supported pool and campaign circuit proofs with pinned public material. | Transferring funds, approving a transaction, or arbitrary circuits. |
| `fundingReceipts` | Encrypt and recover supported campaign receipts locally; prepare eligible claims inside Privatar. | Reading recovery words, spending keys or withdrawal authorizers; bypassing transaction review. |

## Make consent legible

Show why your site needs each permission. Display the full browser origin and the SDK-provided comparison code while pairing. Ask the user to compare the code in both places.

An application name is supplied by the site. It is not a verified identity. A matching comparison code binds the pairing exchange; users should still check the origin.

## Revocation and disconnect

The wallet Connections view shows approved sites and their scopes. Revoking a connection stops further wallet requests. The SDK disconnect callback is the point to clear your local wallet state.

Revocation does not erase data already disclosed to a site or automatically terminate that site’s own authentication cookies.

## Current boundaries

Supported Preview transaction requests require separate wallet review; a connection does not grant silent signing or unrestricted spending. Selective-disclosure credentials and identity attestations are not implemented. Do not represent an authentication signature as proof of a real-world identity.
