> For the complete documentation index, see [llms.txt](https://spozz-club.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spozz-club.gitbook.io/whitepaper/reference/disclaimer.md). # DISCLAIMER This whitepaper is meant to describe SPOZZ’s currently-anticipated plans for developing its business, NFTs, and SPOZZ tokens. Nothing in this document should be treated or read as a guarantee or promise of how SPOZZ’s business will develop or of the utility or value of these NFTs. This document outlines our current plans, which could change at our discretion. Further, the success of these plans will depend on many factors outside our control, including market-based factors and factors within the cryptocurrency industries, among others. Any statements about future events are based solely on our analysis of the issues described in this document, and our analysis may prove to be incorrect. Purchasing NFTs is subject to many potential risks, some of which are described in this paper, and some of which are provided in the FAQ on our website. These documents, along with additional information about our business and SPOZZ NFTs, will be available on SPOZZ.club, soon. As with most digital assets, purchasers of SPOZZ NFTs could potentially lose all or some of the value of the funds used to complete their purchase. --- # 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://spozz-club.gitbook.io/whitepaper/reference/disclaimer.md?ask=&goal= ``` `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.