# Content Policy ⚠️ IMPORTANT: The AquaBank ecosystem strictly adheres to the following content guidelines to provide participants with reliable on-chain data and a transparent, non-custodial Web3 interface. *** ### 1. Provision of Transparent and Verified On-Chain Information All information provided through the interface is based on transparent on-chain data and verified smart contract source code. Key data, including estimated protocol reward rates, smart contract risk factors, and liquidity provision conditions, are explained in intuitive and objective language to ensure clear user comprehension. *** ### 2. Strict Prohibition of Misleading Financial Claims and Exaggerated Advertising Any expressions that could mislead users into confusing the interface with traditional financial products or custodial services, such as guarantees of principal, promises of fixed returns, or inflated reward simulations, are strictly prohibited. Marketing content is governed by the principle of providing neutral information based solely on on-chain facts and statistical data. *** ### 3. Intuitive Design Centered on Web3 Beginners To ensure that the interface remains intuitively accessible even to users without prior knowledge of the DeFi ecosystem, complex technical jargon is simplified and visually driven guides are provided. Up-to-date, step-by-step guides are maintained for smart contract interactions, including “Connecting a Personal Wallet,” “Supplying and Withdrawing Liquidity,” and “Claiming Protocol Rewards.” *** ### 4. Continuous Improvement Based on Participant Feedback The AquaBank ecosystem continuously evolves by actively incorporating feedback and improvement requests from ecosystem participants. Frequently Asked Questions (FAQs) and community insights serve as core indicators for continuously refining the interface’s user experience (UX) and content structure in a more user-friendly manner. *** ### 5. Compliance with Regulatory Guidelines and Maintenance of Technical Rigor All content is prepared in consideration of global Web3 regulatory developments and relevant guidelines. The AquaBank ecosystem clearly states that it is a “software interface” that does not directly manage users’ assets, and transparently discloses the technical limitations and applicable disclaimers of any integrated third-party protocols. --- # 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://aquabank.gitbook.io/aquabank/en/important-notices/content-policy.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.