> For the complete documentation index, see [llms.txt](https://hyperlynx.gitbook.io/hyperlynx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperlynx.gitbook.io/hyperlynx-docs/resources/privacy-policy.md). # Privacy Policy *Last updated: 2026-06-24* {% hint style="info" %} Hyperlynx is non-custodial and account-free. We do not collect your name, email, or government ID, we never hold your keys, and there is no KYC. The blockchain, however, is public and permanent — your wallet address and transactions are visible to everyone, forever. This policy explains what that means and what limited data the interface touches. {% endhint %} ## 1. The short version * **No accounts, no KYC, no passwords.** You connect a self-custodial wallet; we never see your keys or seed phrase. * **We don't collect personal identity data** (name, email, address, government ID). * **On-chain activity is public by design** — not collected *by us*, but visible to the whole network. * **We don't sell your data**, ever. ## 2. What is on-chain (public, not controlled by us) When you trade, provide liquidity, or otherwise transact, you broadcast to public decentralized networks. Your **wallet address, transaction history, balances, and liquidity positions are permanently public** and outside anyone's control, including ours. This is inherent to blockchains, not a choice Hyperlynx makes. Anyone can view this data using a block explorer. ## 3. What the interface processes To make the app work, the following limited data is handled: * **Wallet address** — your connected public address, used to display your balances, positions, and (if you participate) your standing in The Hunt. This is public information. * **Wallet signatures (SIWE)** — if you authenticate or join the points program, you may sign a "Sign-In With Ethereum" message. The resulting signature and your address may be stored to attribute points and prevent abuse. **Signing this message never moves funds.** * **The Hunt / referrals** — your address, your on-chain activity, and referral relationships are processed to compute points, rank, and leaderboards. All of it derives from public on-chain data. * **Local preferences** — settings like theme, Simple/Pro view, and "intro seen" are stored in your browser's local/session storage. They stay on your device and are not personal data. ## 4. Third parties that may see technical data The Platform relies on third-party infrastructure to function. When you use it, these providers may automatically receive technical data such as your **IP address, device/browser information, and the requests you make** (standard for any website or RPC call): * **Wallet providers** (e.g. Rabby, MetaMask, WalletConnect) * **RPC and subgraph providers** (network reads/writes, indexed data) * **Swap aggregators / routing** (e.g. KyberSwap, when enabled) and **transaction relayers** * **Price-data providers** (e.g. DefiLlama, on-chain oracles) * **Hosting / delivery** (the website host and CDN) Each third party operates under its own privacy policy. Hyperlynx does not control how they handle data. In particular, **your IP address may be exposed to RPC providers** as part of normal network operation. If this concerns you, use a VPN or a self-hosted RPC. ## 5. Analytics & cookies The Platform may use **privacy-respecting, aggregate analytics** (e.g. page views, performance) to improve the product. We do not use cross-site advertising trackers and we do not sell data. Cookies and local storage are limited to functional purposes (preferences, session state). You can clear them in your browser at any time. ## 6. What we never do * We never collect or store your private keys or seed phrase. * We never ask for your password, identity documents, or banking details. * We never sell, rent, or trade your data. * We never DM you first asking for funds or "verification." ## 7. Data retention & your control Because the core data is on-chain, it is **permanent and cannot be deleted by anyone**, including Hyperlynx. Off-chain data the interface holds (e.g. points attribution, SIWE signatures) is retained only as long as needed to run the program. You can disconnect your wallet and clear local storage at any time. Depending on your jurisdiction (e.g. the EU/UK), you may have rights to access or request information about off-chain data associated with your address — contact us via the official channels below. ## 8. Children The Platform is not intended for anyone under 18 (or the age of majority in your jurisdiction). Do not use it if you are underage. ## 9. Changes We may update this policy. The "Last updated" date reflects the latest revision; continued use after a change constitutes acceptance. ## 10. Contact Questions about privacy? Reach the community through the official channels — **Telegram: t.me/hyperlynxchat** · **X: @hyperlynxfi**. Hyperlynx is an anon-built protocol; we have no physical mailing address. --- # 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://hyperlynx.gitbook.io/hyperlynx-docs/resources/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.