Privacy Policy — Metropolis
Last updated: October 21, 2026
This Privacy Policy explains how Metropolis processes personal data in connection with the website available at metropolis.exchange and any related subdomains (the "Website") and the decentralized exchange, vault, staking, bridge and other functionality made available through it (the "Service").
Metropolis is operated by Blue DAO LLC, a limited liability company organized under the laws of the Republic of the Marshall Islands, which acts as the controller of the processing described in this Privacy Policy ("Metropolis", "we", "us").
Capitalized terms not defined here have the meaning given to them in the Metropolis Terms of Use.
1. Our approach: we hold almost nothing
Metropolis is a non-custodial interface. We do not create user accounts, we do not require your name or email, we do not process payments, and we do not keep a database of your wallet addresses, watchlist, positions, vault deposits or staking locks. Your watchlist and interface settings are kept locally in your browser. Almost everything the Service does happens either in your own browser, on the Sonic blockchain, or through the data services described below.
As a result, the personal data we process is limited to what is described below.
2. What we process
2.1 Delivery of the Website
When you access the Website, standard technical data is temporarily processed to deliver and secure it, in particular your IP address and browser metadata (such as date and time of access, requested page, browser type, operating system and referring page). Where this is stored in server or hosting log files, it is kept only as long as necessary for functionality and security, usually no longer than 14 days.
2.2 Wallet addresses you enter or connect
The Service lets you connect a wallet to transact, and lets you enter any public wallet address to view read-only information. We do not access, request or store any private key, seed phrase or other wallet-access credential.
To show positions, vault holdings, profit-and-loss estimates, wallet activity and swap quotes, the relevant wallet address is sent through our server to the data services listed in Section 6. We pass these requests through without storing the address in a database. Because the address can be part of the requested URL, it may appear in the short-lived technical logs described in Section 2.1.
2.3 On-chain activity
When you swap, provide liquidity, create a pool, deposit into or create a vault, stake METRO, claim rewards or bridge assets, you sign a transaction in your own wallet that is recorded on a public blockchain. This on-chain data — including your wallet address, transactions, liquidity positions, vault shares and staking locks — is created and stored on the public blockchain, not in a database controlled by us. See Section 4.
2.4 Wallet avatar
If a connected wallet holds a Metronix NFT, the Service loads that NFT's metadata and image from IPFS through a public gateway in order to show it as your wallet avatar. This request is made from your browser and discloses your IP address to the gateway operator.
2.5 No analytics
We do not use analytics, advertising or other tracking of your use of the Service.
3. Publicly displayed data
The Service displays wallets, positions and vault holdings derived from public blockchain data, including the open positions in each pool ranked by profit-and-loss, and the profit-and-loss of any wallet address entered into the Service. This information is not confidential and may relate to any wallet address, including addresses of people who have not themselves used the Service.
Because a wallet address can in some circumstances be linked to a person, such data may constitute personal data. Where we display it, we do so on the basis of our legitimate interest in providing a transparent analytics tool for liquidity providers, and on the basis that the underlying data is already public on-chain.
If you do not want a wallet address associated with you to appear in public rankings, you may request its exclusion through the channels in Section 7, and we will exclude it from those features. We cannot alter or remove the underlying data recorded on the public blockchain, which is outside our control.
4. Blockchain data is public and permanent
On-chain data, including wallet addresses, transactions, liquidity positions, vault shares and staking locks, is public, may be accessed and analyzed by anyone, and cannot be deleted, modified or restricted by Metropolis. Where processing of personal data occurs on a public blockchain, that processing is not carried out by us. Your wallet address and on-chain activity may be combined with other information by third parties, which may make it possible to draw conclusions about your identity.
5. Cookies and local storage
We only use cookies and similar technologies (such as local and session storage) that are technically necessary to provide the Website and the Service — for example to keep your wallet connection, your dashboard watchlist, saved liquidity shapes and interface preferences in your browser. We do not use analytics, advertising or other non-essential cookies, and therefore we do not ask for cookie consent. You can delete cookies and stored site data in your browser settings, though some functions may then no longer work.
6. Recipients of personal data
We do not sell personal data. Because we store almost nothing, the recipients of data are essentially the infrastructure required to run the Service:
- Hosting and infrastructure providers that serve the Website and may keep short-lived technical logs on our behalf.
- The Metropolis data APIs, which receive wallet addresses through our server in order to return pools, positions, vault holdings and profit-and-loss data.
- The Sonicscan block explorer API, which receives wallet addresses through our server in order to return wallet activity.
- The DE1 aggregator, which receives your wallet address and swap details through our server when you request an aggregator quote, and the OpenOcean contracts through which such swaps are executed.
- RPC and node providers (such as Sonic Labs, PublicNode and dRPC), which receive your IP address and the on-chain reads and transactions your browser sends to them.
- LI.FI, when you use the bridge, which receives your IP address, wallet address and bridge details directly from your browser.
- Your wallet provider, including WalletConnect or the MetaMask SDK where you use them to connect, and the public blockchains when you submit a transaction.
- Content hosts from which your browser loads token logos, curator logos and NFT images (such as GitHub, Trust Wallet assets, DefiLlama icons, image proxies and IPFS gateways), which receive your IP address.
These third parties act as independent controllers of their own processing, which we do not control; we recommend reviewing their privacy policies. We may also disclose data where required by law or to establish, exercise or defend legal claims. Recipients may be located in countries other than your country of residence, which may not provide the same level of data protection.
7. Contact and your rights
Subject to applicable data protection laws, you may have the right to request access to, correction, deletion or restriction of your personal data, to object to processing based on our legitimate interests, and to data portability. Because we do not operate accounts and do not keep a database of wallet addresses or other personal data, the data we hold about an individual user is very limited, which may affect how these rights apply in practice. Rights cannot be exercised with respect to data recorded on public blockchains, which is outside our control.
For any privacy question or request — including a request to exclude a wallet address from public rankings — please contact Metropolis through the official Metropolis communication channels linked on the Website, such as Discord and X.
8. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. The current version, including the date of the latest revision, will be made available through the Website.
END OF PRIVACY POLICY
