> For the complete documentation index, see [llms.txt](https://docs.gridlock.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridlock.network/guardians/all-about-guardians/why-not-use-a-seed-phrase-for-recovery.md). # Why not use a seed phrase for recovery? Using a seed phrase for recovery can have its drawbacks due to human error. We understand the importance of minimizing any potential vulnerabilities in security, not just in terms of hackers exploiting them. Typically, a seed phrase is advised to be written down on paper and stored in a safe place. However, think about the possibilities if that piece of paper gets lost. What if there's a fire, a burglary, or your partner accidentally throws it away while cleaning? In such cases, your recovery option would be gone! Human error has proven to be one of the most significant security flaws throughout history, and we believe you shouldn't have to deal with the stress and uncertainties it brings when managing your crypto --- # 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://docs.gridlock.network/guardians/all-about-guardians/why-not-use-a-seed-phrase-for-recovery.md?ask=&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.