> For the complete documentation index, see [llms.txt](https://battle-blitz.gitbook.io/battle-blitz-wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://battle-blitz.gitbook.io/battle-blitz-wp/disclaimers.md). # Disclaimers #### PLEASE READ THIS DISCLAIMER CAREFULLY. Nothing in this document, whitepaper, website, or any other materials related to Battle Blitz constitutes legal, financial, business, or tax advice. You should consult with your own professional advisors before engaging in any activity related to Battle Blitz or any associated tokens, NFTs, or assets. #### No Liability Neither the creators of Battle Blitz ("the Team"), the company issuing any associated tokens or NFTs ("the Company"), any vendors, partners, nor any service providers involved shall be held liable for any direct, indirect, incidental, or consequential damages you may suffer from accessing Battle Blitz materials, participating in its ecosystem, or using its website or platform. #### Purpose and Nature By acquiring any Battle Blitz tokens or NFTs, you acknowledge that they are meant to be used within the Battle Blitz ecosystem for gameplay, interactions, or related services, **they are not investments**.\ The Company acts solely as a third-party provider and does not offer financial, investment, or fiduciary services. This document, whitepaper, and website are for **informational purposes only**. They are not investment offers, securities solicitations, or contracts. Information provided may change at any time without notice, and accuracy is not guaranteed. Any third-party information referenced has not been independently verified. #### No Guarantees Nothing in this document, the whitepaper, or the website constitutes any form of guarantee, promise, or representation regarding the future performance of Battle Blitz, its tokens, NFTs, or any related products. Any agreements regarding token or NFT distribution are governed by separate terms and conditions, which should be read alongside this disclaimer. #### No Contractual Obligation This disclaimer and all related materials are for community discussion only and do not form a legally binding contract. No token, NFT, or payment should be accepted based solely on these materials. Any official agreement will be outlined in separate Terms and Conditions, which will take precedence in case of inconsistencies. #### Your Responsibilities By accessing Battle Blitz materials, you confirm and warrant that: * You are not relying on this document, whitepaper, or website for any financial decision. * You will comply with all laws applicable to you. * You understand that tokens and NFTs may have no value and are not intended for speculative purposes. * The Company and its partners do not guarantee liquidity, resale value, or secondary market availability for any Battle Blitz tokens or NFTs. * You are not participating from any jurisdiction where such participation is restricted, including but not limited to the United States or China, and you agree to provide verification documents if requested. #### No Warranties Battle Blitz, the Team, and the Company provide all materials "as-is" without warranties of any kind. To the maximum extent permitted by law, the Team, the Company, and its service providers disclaim any liability for losses, including loss of revenue, data, or opportunities arising from these materials. #### Token Use Battle Blitz tokens are designed for **in-game utility,** not for speculation or investment. Tokens: * Have no physical form or intrinsic value. * Cannot be refunded or exchanged for cash. * Do not grant ownership, dividends, voting rights, or any claim on the Company or its assets. * Are not financial instruments, securities, or investment products. * Are not loans or debts owed by the Company or Team. * Confer no economic interest in the Company, Team, or their assets. Any future secondary markets for Battle Blitz tokens will operate independently of the Company and Team. #### Forward-Looking Statements Any forward-looking statements are speculative and subject to risks, changes, and uncertainties. No independent review has confirmed the accuracy of such statements, and they only apply as of their publication date. #### No Regulatory Approval No regulatory authority has reviewed or approved any Battle Blitz materials. Accessing these materials does not imply compliance with any laws or regulations in any jurisdiction. #### Final Notes This document, whitepaper, and website are **conceptual** and subject to ongoing development. No future features, releases, or timelines are guaranteed. Materials may be revised or replaced at any time without notice. #### Language and Distribution The English version of this disclaimer and related materials governs in the event of conflicts with translated versions. No part of these materials may be copied, shared, or distributed without prior written consent from the Company. By accessing any Battle Blitz materials, you agree to all terms in this disclaimer. --- # 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://battle-blitz.gitbook.io/battle-blitz-wp/disclaimers.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.