> For the complete documentation index, see [llms.txt](https://docs.quantpad.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quantpad.company/reference/terms-of-use.md). # Terms of use Plain-language terms for using Quant Pad. Read them before launching or trading. Plain-language terms for using Quant Pad. Read them before launching or trading. ## What Quant Pad is Quant Pad is software that builds Solana transactions for Meteora and for the Quantum Hooks program. You sign every transaction in your own wallet. Quant Pad does not custody funds, does not hold private keys and cannot reverse transactions. ## Your responsibility * You are responsible for what you launch, including names, images and links, and for complying with the laws that apply to you. * Do not launch coins that impersonate people, brands or projects, or that infringe anyone's rights. * Tokens launched here have no intrinsic value and no promise of returns. You can lose everything you spend. ## Third parties Coins are created and traded through Meteora's Dynamic Bonding Curve and DAMM v2, which are operated by third parties with their own fees, rules and admin powers. Their changes can affect coins launched here, including stopping Quantum Hooks. ## No warranty The software is provided as is, without warranties of any kind. Smart contracts can contain bugs. Quant Pad is not liable for losses arising from its use, to the extent the law allows. ## Content Quant Pad may hide coins from its own pages for any reason. Hidden coins remain on-chain and on Meteora. --- # 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.quantpad.company/reference/terms-of-use.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.