> 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/lost-secret-key-then-what.md).

# Lost Secret Key, then what?

Secret Keys control the funds sent to individual Stacks addresses. Secret Keys are either a 24 word secret phrase that users were prompted to record in the process of setting up their Leather, *or* secret keys stored on a connected 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).

In the past, users were able to use either a Trezor or Ledger to set up a Leather address as an alternative to generating a new secret key for their STX holdings. As such, they may have 12, 18 or 24 word secret keys that are associated with their hardware wallets that might have been used to set up Leather originally (or a preceding wallet such as Hiro Wallet or Stacks wallet).

Users who think they may have lost their secret key are encouraged to first check any hardware devices for their holdings by connecting to the latest Wallet for desktop via [get wallet](https://leather.io/install-desktop) and trying the steps for Ledger [here](https://leather.gitbook.io/guides/securing-the-wallet/using-ledger-with-leather) or Trezor [here](https://leather.gitbook.io/guides/securing-the-wallet/using-trezor-with-leather).

Users are also encouraged to check any safes / password managers or paper files with important information to find their 24-word secret keys if they have never used a hardware wallet.


---

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