> For the complete documentation index, see [llms.txt](https://docs.hann.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hann.finance/legal/privacy-policy.md). # Privacy Policy Last Updated: November 1, 2025 ## Operator and scope Protocol contributors (“we,” “us,” or “our”) operate the Hann Finance documentation sites and testnet interfaces. This Privacy Policy (the “Policy”) applies to information processed when you use , , and related public resources (the “Website”). We are the data controller for the information described in this Policy. The Website currently provides information and testnet access only. We have no plans to collect personal data beyond the scope stated in this Policy. ## Information we currently process As of the revision date, we collect only the following minimal information: * **Service metadata:** IP address, user agent, requested URL, and timestamp recorded in standard web server logs to secure the Website and troubleshoot problems. * **Aggregate performance metrics:** anonymous, cookieless measurements from Vercel Web Analytics and Vercel Speed Insights, including page path, referrer, country code derived from IP address, browser, operating system, device type, Web Vitals, and aggregate counts. These tools frequently rotate identifiers and do not permit tracking across sites or across days. * **Messages you send us:** the email address and content of messages sent to . We process them only to respond to your inquiry. We do not currently operate contact forms, user accounts, newsletters, tracking pixels, KYC/AML onboarding, or advertising on the Website. ## How we collect information * **Direct submissions:** emails you voluntarily send us. * **Automatic records:** minimal server logs, essential local storage, and cookieless Vercel telemetry needed to operate the Website. * **Public sources:** blockchain data anyone can view, including wallet addresses recorded on-chain. * **Service providers:** automated error and performance reports generated by infrastructure providers hosting the Website, currently Vercel. We do not operate sign-up flows, marketing forms, KYC procedures, or other channels that expand collection. Testnet activity may be recorded in aggregate to maintain reliability, and those records may be deleted at any time. We have no plans to expand collection beyond the scope stated in this Policy. ## How we use information We use the information collected to: 1. Operate, secure, and troubleshoot the Website. 2. Measure aggregate performance and improve the documentation experience. 3. Respond to support requests you send us. 4. Meet legal obligations and respond to requests from competent authorities. We do not sell personal data or run targeted advertising. ## Cookies and similar technologies * We do not use non-essential cookies. Essential local storage may remember settings such as theme selection. * Vercel Web Analytics and Speed Insights count visits using rotating hashes and do not track you across sites or over time. * We receive “Do Not Track” signals but take no additional action because we do not engage in behavioral advertising. * You can block cookies or local storage in your browser. Some convenience features may be limited. * We do not use Google Analytics, Meta Pixel, Hotjar, session replay scripts, or comparable high-fidelity tracking tools. ## Public blockchain data Wallet interactions with public smart contracts remain permanently visible on-chain. We may review public ledger data to monitor protocol health, but we do not use it to build user profiles. ## Third-party wallets Connecting a non-custodial wallet, such as Kaia Wallet or MetaMask, means using software maintained by that wallet provider. Its privacy policy governs personal data processed by the wallet extension. We cannot access or recover your private keys or seed phrase. ## Third-party sites and communities Documentation and community pages may link to GitBook, X (Twitter), Discord, Telegram, Medium, or external DeFi protocols. These services operate independently and apply their own privacy policies. [GitBook's Cookie Policy](https://policies.gitbook.com/privacy/cookies) applies to documentation sites provided by GitBook. Information shared in public channels may be visible to other users. ## Information sharing We share information only when needed for the purposes above: * **Infrastructure providers:** hosting, CDN, and analytics providers, currently Vercel, process logs and performance data under contractual safeguards. * **Professional advisors:** we may share limited information needed for legal, regulatory, or tax advice. * **Regulators and authorities:** we may disclose information to comply with lawful requests or protect rights and safety. * **Business successors:** after a merger, acquisition, or reorganization, successors must follow this Policy or provide an updated policy. * **Third parties you choose:** information may flow to third parties when you explicitly connect a wallet or integrate with an external app. ## International transfers Infrastructure may operate outside your country of residence. Where the law requires it, we apply safeguards such as Standard Contractual Clauses and add technical protections for international transfers. ## GDPR legal bases For visitors in the European Economic Area, United Kingdom, or Switzerland, where applicable, we process information on the following bases: * **Legitimate interests — GDPR Article 6(1)(f):** operating, securing, and improving the Website without profiling users. * **Legal obligation — GDPR Article 6(1)(c):** responding to lawful requests or retaining logs required by law. * **Consent — GDPR Article 6(1)(a):** obtaining consent before collecting optional KYC documents, newsletter subscription information, or other elective information. * **Contract — GDPR Article 6(1)(b):** processing data needed to deliver requested functionality in future regulated services. ## Retention and deletion * We retain server metadata only for the period needed to deliver and secure the Website, then delete it. * We store aggregate analytics as anonymous statistics and regularly overwrite them during ongoing reporting. * We delete messages you send us when the inquiry is resolved. If the law requires a longer retention period, we follow that period. * If compliance archives are introduced, we will disclose statutory retention obligations before collection. We delete information that is no longer needed or irreversibly anonymize it. ## Security We apply reasonable technical and organizational safeguards, including TLS encryption in transit, access logging, least-privilege controls, and dependency reviews. No online service can guarantee complete security. You must protect your devices and wallets and must not share private keys. If we become aware of a data incident, we will investigate and notify affected parties and authorities where required by law. ## Your rights You may exercise rights recognized by the law in your jurisdiction, including access, correction, deletion, restriction, objection, and portability of your personal data. You may withdraw consent for processing based on consent. Withdrawal does not affect lawful processing carried out before withdrawal. To exercise your rights, email . We may request limited identity verification details before processing your request. You also have the right to complain to your local data protection authority. ## Changes to this Policy We may update this Policy for new features, regulatory requirements, or operational changes. The Last Updated date identifies the latest revision. We will announce material changes on the Website or through another appropriate channel before they take effect. Before collecting additional information, we disclose the types of information and the purposes of processing, and obtain consent required by law. ## Contact Send questions about this Policy to . --- # 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://docs.hann.finance/legal/privacy-policy.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.