The short version. We run no analytics and no ads, and we set no cookies. Our server sees your wallet address, and your IP address for rate limits. Your orders are sealed in the enclave. Google and email sign-in is handled by Reown: we never receive your email address.
1. Who is responsible
Hiddenliquid ("we", "us") is responsible for the personal data described here, for the website hiddenliquid.com and the app at app.hiddenliquid.com. Write to us at hiddenliquid@gmail.com.
2. What we handle, why, and for how long
Your wallet address and your requests
Our relayer, the server that pays gas for you and passes your requests to the enclave, receives your wallet address with each deposit, test-token request and order request. Order requests are sealed to the enclave: the relayer passes them on and cannot read them. It keeps no record of your requests once it has passed them on. We need this to provide the service you ask for.
Your account inside the enclave
The enclave keeps your account: balances, open and filled orders, the session keys of your signed-in devices, the public part of your exit key, and references to recent requests. It stores them sealed, so we cannot read them while the enclave runs its approved code (section 6 of our terms describes the one trust point left on the test network). They are kept for as long as your account exists in that deployment of the vault.
Your IP address
- The relayer uses your IP address to count requests against our rate limits (how many requests, test tokens and paid transactions one network may have). It keeps these counts in memory only, for 24 hours at most, and forgets them when it restarts. It keeps no access log.
- Our web server keeps no access log either. When a request fails on the server, for example while the relayer restarts, the server's error log records that request: your IP address, your browser's name and version, and the address asked for. These logs stay on our server until the system log deletes its oldest entries to make room.
- We use these to keep Hiddenliquid running and to stop abuse.
Emails you send us
If you write to us, we keep your email to answer it. Our mailbox is at Gmail, run by Google.
What is public on the blockchain
Deposits and withdrawals with their wallet addresses, each batch swap with its total, the enclave's updates and the encrypted exit records are public on Base Sepolia, for anyone, for good. Nobody can change or delete them, including us.
3. What stays on your device
We set no cookies. The app keeps these in your browser's local storage:
- your session key, which lets this browser place and cancel orders for your account until you sign out;
- your demo account's key, if you use a demo account;
- how you last signed in, so a reload can sign you back in;
- references to your recent requests, so an order sent again runs only once;
- your chart settings and drawings, the tokens you added to the wallet view, and whether fill alerts are on.
The app also keeps a copy of its own files, so it opens on a poor connection. Prices, balances and orders are never stored that way. All of this is needed for the app to work. None of it tracks you, and it leaves your device only as part of a request you make. Signing out removes the session key; clearing the site's data in your browser removes everything. Reown keeps its own sign-in data in your browser too.
If you turn on fill alerts, your browser asks your permission to show notifications. They are made on your device, and nothing is sent to a notification service.
4. Other companies that see your data
Your browser connects directly to some of these, so they see your IP address and their own part of what you do:
- Reown (WalletConnect) runs sign-in and wallet connections. If you sign in with Google, Apple or email, Reown, together with Google or Apple, handles your login and email address, and creates and runs your wallet. We never receive your email address, and Reown's analytics are switched off in our app.
- Binance provides the chart's market data, through its public data service.
- RPC providers answer your browser's questions to the blockchain: Base (sepolia.base.org), PublicNode and dRPC. They see which addresses and contracts your browser asks about.
- Phala hosts the enclave's machine. It carries your sealed requests but cannot read them.
- Contabo hosts our server: these pages, the app's files and the relayer.
- Google runs our mailbox, and X our account there, if you contact us through them.
- The wallet app you connect, if you use one.
Their own privacy policies apply to what they do. Some of them handle data outside your country, including outside the EU. We do not sell your data, share it with advertisers, or use it to build a profile of you.
5. Our legal bases
- To provide the service you ask for: your wallet address, your requests, your account in the enclave, and what the app keeps on your device.
- Our legitimate interest in keeping Hiddenliquid running and safe from abuse: rate limits and error logs.
- Your consent: fill notifications, and the emails you choose to send us.
6. Your rights
You can ask us what we hold about you, ask us to correct or delete it, to limit how we use it, or to send you a copy, and you can object to how we use it. Write to hiddenliquid@gmail.com. Some limits come from how Hiddenliquid works:
- Nobody can change or delete what is on the blockchain.
- We cannot open or delete a single account inside the enclave. Withdrawing your funds and signing out everywhere leaves no balance, open orders or active sessions there.
- Rate-limit counts are gone within 24 hours. To have error-log entries deleted, tell us your IP address and roughly when you used Hiddenliquid.
You can also complain to a data protection authority, for example the one where you live.
7. Children
Hiddenliquid is not for anyone under 18.
8. Changes
If we change this policy, the date at the top changes too. If we ever add something that needs your consent, such as analytics, we will ask for it first.