> For the complete documentation index, see [llms.txt](https://docs.hyperlink.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperlink.xyz/legal/privacy-policy.md).

# Privacy Policy

**Effective Date:** May 26, 2026

This Privacy Policy explains how HyperLink handles information in connection with HyperLink interfaces, including the web application at app.hyperlink.xyz, the API at api.hyperlink.xyz, any agent, Telegram, developer, or other interface, our documentation, and related software or services that link to this Policy (collectively, the **"Interface"**).

For purposes of this Policy, **"HyperLink"**, **"we"**, **"us"**, and **"our"** mean HyperLink and the persons or entities that operate, host, develop, maintain, or make the Interface available.

By accessing or using the Interface, you acknowledge this Policy.

## 1. Information We Collect

We aim to collect only the information reasonably needed to operate, secure, maintain, and improve the Interface.

### Information you provide or authorize

We may collect:

* **Wallet information**, including public wallet addresses, signatures, authentication events, connected-wallet status, and related public blockchain information;
* **Credential and account metadata**, including agent credentials, API-key metadata, names or labels you assign, permissions, creation dates, and usage events;
* **Telegram-linking information**, if you use Telegram-linked features, including identifiers and authentication metadata needed to provide those features;
* **Communications**, including information you provide when you contact us; and
* **Compliance information**, if requested, including information used to assess eligibility, sanctions risk, fraud risk, misuse, or legal compliance.

### Information collected automatically

When you use the Interface, we and our service providers may collect:

* **Device and connection data**, including IP address, browser type, device type, operating system, referring URL, pages viewed, timestamps, approximate location inferred from IP address, and standard server-log information;
* **Usage and performance data**, including page views, API usage, latency, errors, referrers, session events, and feature usage;
* **Security and compliance data**, including risk signals, rate-limit data, abuse indicators, geofencing signals, sanctions-screening results, and allowlist or blocklist status; and
* **Cookies and similar technologies**, as described below.

### Public blockchain information

Public blockchains are transparent. Wallet addresses, deposits, withdrawals, transaction hashes, token transfers, contract interactions, timestamps, and other on-chain activity may be public, permanent, and outside our control.

### Information we do not intentionally collect

We do not intentionally collect government IDs, legal names, dates of birth, residential addresses, or similar KYC information unless we determine it is necessary for legal, compliance, security, or risk-management reasons.

We do not have access to your self-custodial wallet private keys or seed phrases.

Technical protections may apply to certain transactions or instructions. However, public blockchain data and metadata, including timing, routing, size, IP-derived information, wallet information, and request information, may still be processed by us or our service providers.

## 2. How We Use Information

We may use information to:

* provide, operate, maintain, secure, and improve the Interface;
* authenticate wallets, credentials, API keys, and supported integrations;
* route, process, and display user-authorized instructions and related status information;
* provide support and respond to communications;
* monitor performance, debug errors, and improve reliability;
* detect, prevent, investigate, and respond to fraud, abuse, security incidents, prohibited conduct, and unlawful activity;
* enforce our Terms of Use, including eligibility, geofencing, sanctions, allowlist, and blocklist controls;
* comply with legal obligations, lawful requests, sanctions requirements, anti-money-laundering obligations, and regulatory inquiries;
* protect the rights, property, safety, and security of HyperLink, users, service providers, and others; and
* conduct analytics and measurement.

We do not sell personal information. We do not use personal information for targeted advertising.

## 3. Legal Bases

Where a legal basis is required, we process information as necessary to provide the Interface, perform or enforce our Terms of Use, comply with legal obligations, protect legitimate interests in security and abuse prevention, and, where applicable, based on your consent.

## 4. How We Share Information

We may share information with:

* **service providers**, including hosting, infrastructure, analytics, authentication, key-management, security, compliance, and support providers;
* **affiliates, contributors, and professional advisers**, including lawyers, auditors, insurers, accountants, and consultants;
* **authorities or other parties when legally required**, including to comply with law, legal process, sanctions obligations, regulatory requests, or to protect rights, safety, and security;
* **transaction counterparties**, in connection with a merger, financing, reorganization, transfer, sale, or similar transaction involving all or part of HyperLink; and
* **public blockchains and third-party protocols**, when you submit transactions or otherwise interact with blockchain systems.

Service providers receive information only as reasonably needed to perform their functions and are subject to their own terms and privacy practices.

## 5. Cookies and Similar Technologies

The Interface may use cookies, local storage, and similar technologies to maintain sessions, remember preferences, authenticate wallet connections, secure the Interface, measure performance, and provide basic functionality.

We do not use advertising cookies or third-party tracking cookies for behavioral advertising.

You can adjust your browser settings to block or delete cookies, but some features may not work properly.

## 6. Data Retention

We retain information for as long as reasonably necessary or permitted to provide the Interface, comply with legal obligations, resolve disputes, enforce our Terms of Use, prevent fraud and abuse, maintain security, and support legitimate operational purposes.

Server logs and analytics records are generally retained for limited periods, subject to operational needs and provider practices.

Public blockchain data may be permanent and cannot be deleted, modified, or controlled by us.

## 7. Security

We use commercially reasonable technical and organizational measures designed to protect the information we process. These measures may include encryption, access controls, monitoring, rate limiting, credential-management controls, and other safeguards.

No system is perfectly secure. We cannot guarantee that information will be secure or free from unauthorized access, loss, misuse, or alteration.

## 8. International Transfers

We and our service providers may process information in jurisdictions other than where you are located. Those jurisdictions may have data-protection laws different from those in your jurisdiction. Where required, we use appropriate safeguards for international transfers.

## 9. Your Choices and Rights

You may stop using the Interface at any time. You may disconnect your wallet, delete local browser data, revoke permissions where supported, and stop using credentials or integrations.

Depending on your jurisdiction, you may have rights to request access, correction, deletion, portability, restriction, objection, or withdrawal of consent. These rights may be limited where information is pseudonymous, public on-chain, necessary for security or legal compliance, or not reasonably capable of being linked to you without additional information.

To protect users, we may require you to verify control of a wallet address, including by signing a message, before responding to a request about wallet-linked information.

You may also have the right to lodge a complaint with your local data-protection authority.

To make a privacy request, contact <privacy@hyperlink.xyz>.

## 10. Children

The Interface is not intended for anyone under 18. We do not knowingly collect personal information from children.

## 11. Third-Party Links and Services

The Interface may link to or depend on third-party websites, applications, wallets, protocols, APIs, blockchains, infrastructure providers, or other services. We are not responsible for the privacy practices of third parties. Review their policies before using them.

## 12. Changes to this Policy

We may update this Policy at any time. Updates are effective when posted with a new effective date, unless otherwise stated. Your continued use of the Interface after an update means you acknowledge the updated Policy.

## 13. Contact

For privacy questions or requests, contact <privacy@hyperlink.xyz>.


---

# 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.hyperlink.xyz/legal/privacy-policy.md?ask=<question>&goal=<endgoal>
```

`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.
