> 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/the-tech/design-principles/non-custodial.md). # Non-custodial Non-custodial - a fancy way to say 'what's yours is yours'. Gridlock operates on a non-custodial basis, ensuring that we have no claim to your assets. Our role is to offer secure storage and oversee networks for smooth operation. While your wallet may rely on others to safeguard your crypto, control always resides with you. You remain the undisputed owner of your crypto, not us, not your guardians. Gridlock is a system guided by you, supervised by us, and safeguarded by friends. To better understand the role that your guardians take in protecting you, see [All About Guardians](/guardians/all-about-guardians.md) --- # 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/the-tech/design-principles/non-custodial.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.