# Disclaimer The **PokeDAO NFT** Project was conceptualized and developed as a tribute to and celebration of the immense passion and love that countless fans harbor for the world of Pokemon. Our primary intention is to offer a space for these enthusiasts to unite, connect, and share their unique experiences and stories under a collective banner. It is essential for all participants and observers to understand that the PokeDAO NFT Project operates entirely independently. We have no official ties, associations, or affiliations with Nintendo, the Pokemon Company, or any related entities or franchises. Our project is not endorsed by, directly affiliated with, maintained, authorised, or sponsored by any of these official bodies. All product and company names, including but not limited to "**Nintendo**" and "**Pokemon**", are the registered trademarks of their original owners. The use of any trade name or trademark is for identification and reference purposes only and does not imply any association with the trademark holder or their brand. We fervently respect the intellectual property rights of all parties and strive to operate within the boundaries of fair use and fan appreciation. Any participant or user of the PokeDAO NFT Project should proceed with the understanding that we are a community-driven initiative, focused solely on celebrating our shared love for the Pokemon universe, and not an official representation or extension of Nintendo or the Pokemon franchise. --- # Agent Instructions: 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: ``` GET https://pokedaos-organization.gitbook.io/pokedao-calling-all-pokemon-trainers/disclaimer.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.