> For the complete documentation index, see [llms.txt](https://leather.gitbook.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leather.gitbook.io/guides/securing-the-wallet/secret-key-and-password.md).

# Secret Key and password

What is the difference between a Secret Key and a Password in Leather?

Secret Keys control the funds sent to individual Stacks or Bitcoin addresses. Secret Keys are either a 24 word secret phrase that users are prompted to record in the process of creating a wallet with Leather, *or* a Secret Key connected to a hardware wallet device. A full overview and background on Secret Keys is available [here](https://leather.gitbook.io/guides/securing-the-wallet/secret-key-basics). Without a Secret Key, users cannot access the wallet.

‍Leather is compatible with BIP39 Mnemonic Seed Phrases that have a length of 12, 15, 18, 21 or 24 words. Leather *will/has always* generated 24-word seed phrases. 

A Password within Leather simply acts as another layer of security that is device-specific. Passwords are created by users and they must meet certain security requirements. Passwords are useful if you use the same device and same browser every time you use your Leather, as it saves you from having to re-enter your Secret Key each time you login. Unlike Secret Keys, Passwords can be reset and recovered.

‍

To reset the password, simply log out of the Wallet. You can do this by navigating to upper right corner menu of the Wallet and selecting "sign out." When you log back in with your Secret Key, you will be automatically prompted to create a new password.


---

# 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://leather.gitbook.io/guides/securing-the-wallet/secret-key-and-password.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.