> For the complete documentation index, see [llms.txt](https://docs.leather.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leather.io/get-started/connect-apps.md).

# Connect to apps

What an app can see and do after you connect Leather to it, and what still needs your approval.

Connecting Leather to an app gives the app your public addresses. Everything else needs your approval in Leather, every time.

## What happens when you connect

When you click "Connect Wallet" in an app and select Leather, Leather opens a "Connect app" window. It shows the domain that asks, the account it will share and the permissions. Check the domain, then click "Confirm" or "Deny".

## What a connected app can see

* The Stacks address of the account you chose.
* Its Bitcoin addresses, Native SegWit and Taproot.
* Anything public about those addresses on the blockchain, such as balances.

Leather remembers which account you connected to each site and uses that account for the site's later requests.

## What still needs your approval

A connected app cannot reach your Secret Key or private keys. It cannot move assets on its own. Leather opens a window and waits for your approval when an app asks to:

* sign or send a transaction
* sign a message

Read what you are asked to sign before you approve it.

## Another wallet opens instead of Leather

Leather registers in the browser as "LeatherProvider", and also under the older shared names "StacksProvider" and "HiroWalletProvider". With more than one wallet extension installed, an app that uses a shared name reaches the wallet the browser loaded first. That wallet's window opens instead of Leather's. Use the app in a browser profile with only Leather installed, or ask the app developer to support Leather by name.

## Related

* [Connect to dApps](/get-started/connect-dapps.md)
* [Disconnect from apps](/get-started/disconnect-apps.md)