> For the complete documentation index, see [llms.txt](https://modster-customs.gitbook.io/modster-customs-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://modster-customs.gitbook.io/modster-customs-docs/support/18-refunds-and-rules.md). # Refunds & Rules ## File redistribution Do not redistribute, resell, leak, or publicly upload Modster Customs files unless your license explicitly permits it. ## License keys and account access Keep your purchase account, license keys, and authentication information private. ## Support Support is intended to help with legitimate purchases and supported configurations. ## Refund policy > **ACTION REQUIRED BEFORE PUBLISHING:** Replace this placeholder with the exact Modster Customs refund policy and any Tebex-specific terms you want customers to see. ## Terms > **ACTION REQUIRED BEFORE PUBLISHING:** Add your official terms/license link here if you have one. --- # 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://modster-customs.gitbook.io/modster-customs-docs/support/18-refunds-and-rules.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.