Your wallet.
Your data.
Your control.

This notice covers the Exoswap website and its trading, bridge, market research, public analytics and support interfaces available at exohood.app. It does not automatically cover unrelated Exohood products, independent wallet apps, blockchain networks, governance forums or websites reached through external links.

Exoswap is presented under the Exohood Labs Protocol brand. The legal entity responsible for personal-data processing, its jurisdictional contact information and any designated data protection officer should be confirmed in the applicable official legal disclosures. For current enquiries, use the Exoswap Help Center and select a privacy-related request.

Different features require different information. Connecting a wallet is not equivalent to creating a hosted exchange account, but some information can still qualify as personal data when associated with an identifiable person.

Do not send passwords, seed phrases, private keys, identity documents or unnecessary sensitive personal information in open support messages.

Exoswap interacts with compatible non-custodial wallets, including browser providers and WalletConnect-compatible sessions. The wallet signs requests under its own security model. Exoswap does not require or ask you to disclose private keys or recovery phrases.

When you connect, the interface or its service providers may access your public address, chain identifier and selected account information to show balances, request quotes or verify transactions. A wallet address is pseudonymous, not guaranteed anonymous, and may be linkable to public transactions or information held elsewhere.

You can disconnect from the interface, remove WalletConnect sessions in your wallet and clear relevant browser data. Disconnecting does not delete existing public blockchain transactions.

When you request a swap quotation, Exoswap or its backend may send chain, token, amount and routing parameters to an independent liquidity aggregator such as 0x and to blockchain data providers. Wallet addresses may be needed for executable transaction construction and verification.

To support transaction confirmation and recovery, backend records may include quote references, hashes, selected network, transaction outcomes and related technical information. On-chain trade records can also be visible to anyone using a public blockchain explorer.

Exoswap may display aggregated analytics about confirmed swaps. A displayed trade count does not imply custody of users' assets or private keys.

Cross-chain transfers may depend on external bridge providers, source and destination RPC endpoints and independent settlement mechanisms. Route queries can reveal token choices, amounts, wallet addresses and the networks involved to the providers necessary for execution.

Bridge status may be checked separately from swap analytics. Providers may maintain their own logs and policies, and some transfers may require independent recovery or support processes.

The token directory, liquidity views, top-100 markets and stocks/ETF watchlist can request market information or images from third-party services. Those services may receive technical connection information when their resources load.

The current stocks and ETFs interface is research-oriented, with illustrative prices rather than enabled security-token trading. Viewing a symbol, filtering a list or reading a market page does not itself mean Exoswap has executed a trade for you.

Token listing requests may be reviewed and retained for approval and security purposes when a submission service is used.

When you submit a support request through /help/, the PHP contact workflow collects the details you provide, checks form validity and forwards the support message through a Telegram Bot API to the configured support chat. This is not an encrypted communication directly between you and Exoswap.

Typical fields include your name, email, network, device/browser, subject and description; public wallet and transaction hash are optional. The support form uses a temporary PHP session for anti-forgery protection and basic anti-spam controls. Support representatives or operators with access to the destination chat can view the submitted information.

Telegram may process the forwarded information according to its own privacy policy. Only include information necessary to investigate your request. Support messages may be retained for resolution, audit and misuse prevention according to the operational retention rules described below.

Technical systems may process limited request, diagnostic, session, error and rate-limit information to protect infrastructure, identify automated misuse, maintain reliability and investigate service failures.

The original Exoswap technical notice described limited hashed-IP information for abuse rate limiting and stored quote references. Hashing or truncation can reduce exposure but does not necessarily make information anonymous. Hosting providers can independently maintain access and security logs.

We do not treat these technical records as permission to profile visitors for unrelated marketing.

Functional browser storage is used where needed to make the interface work. Examples include WalletConnect session persistence, transaction-recovery references or application preferences. The support page may set a short-lived, HTTP-only PHP session cookie for form security.

Third-party providers can apply their own storage rules. The current main Exoswap trading page was configured without optional Hotjar, Microsoft Clarity, HubSpot, Yandex Metrica or Google Analytics scripts, but that technical observation is not a guarantee about every future page or third-party destination.

Where non-essential tracking is introduced and law requires consent, it should be disclosed and controlled before activation. Browser settings may remove local storage, although doing so can disconnect sessions or clear recovery references.

Information is used to provide requested features, secure the service, verify transaction outcomes, respond to support tickets, investigate incidents and meet applicable legal obligations. Under privacy laws such as the GDPR, a valid legal basis must apply to each processing purpose.

The precise lawful basis must reflect the responsible entity's actual processing operations and the user's jurisdiction; this table is an explanation of categories rather than a claim that every basis applies in every case.

The interface may rely on independently operated services for wallet connectivity, RPC access, liquidity aggregation, cross-chain routing, market research, hosting, fonts, blockchain exploration and messaging. Examples of integrations documented in Exoswap releases include WalletConnect-compatible infrastructure, 0x, public RPC services, market data sources, Google Fonts and Telegram for support.

Such providers may receive IP addresses, request metadata, wallet addresses or transaction parameters necessary to fulfil their functions. Their own policies and contractual terms may apply. Following an external community or governance link also takes you outside the Exoswap privacy environment.

Exoswap does not automatically endorse or control an independent provider's data practices.

Blockchains and infrastructure providers can operate globally. Data submitted to Telegram, wallet services, market-data providers or host infrastructure may be processed outside your country, including outside the European Economic Area.

Where an applicable privacy law requires safeguards for international transfers, the responsible organisation must assess the recipient, destination, lawful transfer mechanism and any supplementary protections. Information can also be disclosed where required by valid legal process or to defend legitimate legal rights.

Different records require different retention decisions: security logs should be limited to what is necessary to investigate abuse, support cases to their resolution and any applicable legal retention periods, and quote/transaction references to confirmation, recovery and audit needs. Browser-side data may remain until a session ends, it expires or you clear it.

A public blockchain record normally persists independently of Exoswap and cannot be deleted by removing data from a website. Hosting providers and third-party service operators may apply separate backup or retention rules.

Specific maximum retention periods for support records, backend logs and backups should be published once verified against the production systems. In the meantime, submit a request through Help for information about a particular record.

The interface is designed around non-custodial approvals and transactions, but no website, network, API or smart contract is immune to failure, interception or misuse. Transport security, access controls and anti-abuse safeguards reduce risk; they cannot provide an absolute guarantee.

Review transaction permissions before signing, verify official domains and token contracts, protect device access, update wallet software and never share recovery phrases. A staff member should not need your secret recovery phrase to resolve a ticket.

Depending on where you live and which privacy law applies, you may have rights to know what information is held, access it, correct inaccurate details, request deletion or restriction, object to certain processing, obtain portable data where applicable and withdraw consent where it is the lawful basis.

You may also have the right to lodge a complaint with a competent data protection authority. Some rights are subject to exceptions, such as legal record-keeping obligations or the rights of others. The public, immutable nature of blockchain data can limit what a website operator can change or erase.

Use the Help Center to submit a privacy request. Describe the record or transaction reference without including your private key. We may need a proportionate verification step to prevent disclosure to the wrong person.

Blockchain explorers, nodes and other network participants can access transactions recorded on public ledgers. Wallet addresses, contract interactions, transfer amounts and timestamps may be public permanently and may be correlated with off-chain information.

Even if Exoswap removes a locally held transaction reference when legally and technically appropriate, it does not erase the underlying public network record. Network participants operate independently and may be subject to different privacy rules.

The trading interface is designed for adults with the legal capacity to use the service and is not directed at children. Available features may be limited by law, location or partner requirements. Do not use a VPN or technical workaround to evade legally required access restrictions.

References to specific markets, tokens or governance tools do not establish that a feature is lawful or available in every jurisdiction. Consult the Terms of Service and risk disclosures.

This privacy notice can be updated to reflect newly enabled features, third-party integrations, legal requirements or operational changes. The latest revision date appears at the top of this page. Material changes should be communicated using appropriate notices when required by law.

A notice about a future feature does not mean that it is currently enabled or that personal information is already being collected for it.

Use the Exoswap Help Center and select a privacy-related issue. Explain the type of request, the email address to contact and, if relevant, a public wallet address or transaction reference. Never disclose a seed phrase, secret key or password.

For independent legal information, see Terms of Service, Risk Disclosure and How it works.