YOUR PRIVACY

draft 0.1 · plain language · last edit date filled in before mainnet

⚠ NO LAWYER HAS READ THIS. This page needs a qualified review before anything goes public. GDPR, CCPA and MiCA all apply, depending on where the users turn out to be.

± LIQUA keeps very little about you. No cookies. No analytics scripts. Nothing that follows you around the web. Your wallet address and whatever you sign on-chain are public to everyone, which is how blockchains work. Off-chain, the relayer holds a short list of recent orders and lobby lines so the book can do its job.

1 · What this page covers

How the off-chain parts of LIQUA handle data. That means this website and the relayer at relayer/server.js. It does not cover the blockchain itself, which independent nodes run and nobody on the project controls.

2 · What gets kept off-chain

what	for what	stored where	kept how long
Your wallet address	naming who made an order and who wrote a lobby line	in memory, plus `shared/book.kernel.json` on the relayer machine	until the order expires, the line falls out of the 200-line ring, or the machine restarts
Orders you sign	so other people can see them and take them	in memory, plus the kernel file	until the order expires or gets matched
Lobby lines you sign	showing them in the lobby chat	in memory, in a 200-line ring, plus the kernel file	the newest 200 lines
The IP address a request comes from	rate limits and blocking abuse	web server logs that rotate	about 7 days
Crash reports, only when Sentry is switched on	tracking down bugs	Sentry's servers	whatever Sentry keeps them for, usually 30–90 days

3 · What never gets kept

No cookies. Nothing here sets a tracking cookie. Your wallet remembers its own permissions, and the desk saves your watch list and practice-mode balances in your browser's own storage. None of that leaves your machine.
No analytics trackers. Zero Google Analytics, Mixpanel, Segment, Facebook pixel or Hotjar.
No personal details. Nobody asks for your name, email, phone, home address or ID. There are no accounts to pin them to.
No fingerprinting. No canvas tricks, no font lists.
No tracking across sites. Nothing goes to ad networks.

4 · What lands on-chain and stays

Whatever you do on a blockchain is public for good. That covers orders that settle, transactions you sign, tokens you move and votes you cast. Anyone can look it up in a block scanner. The chain wrote it, not this site, and it cannot be erased.

To keep your trading quiet, use a fresh wallet each session, or a network built for privacy. LIQUA does not offer that. Its exchange is see-through on purpose.

5 · Outside scripts some pages load

A few pages pull files from other services to work.

ethers.js from cdnjs.com, which signs messages and talks to the chain.
TradingView chart widget on the desk page, served from s3.tradingview.com.
A Binance public WebSocket feed for outside ETH/USDT depth. The relayer pulls it, never your browser.

Those services follow their own privacy rules and may log your IP when their files load. LIQUA has no say over what they do with it.

6 · Who else sees it

Nothing held here is sold, rented, traded or handed out. The one exception is a valid court order or lawful subpoena in a place where the project operates.

7 · What you can ask for

So little is stored that most requests are quick.

See it. You get shown what is held about you, usually just your address in the recent book, lobby or tape.
Delete it. Your address gets wiped from off-chain storage on request. On-chain records cannot be touched by anyone.
Fix it. Rarely needed, because everything held was signed by you.

A privacy contact is announced before mainnet. The aim is to answer within 30 days.

8 · Keeping it safe

The relayer is an ordinary Node.js app, and it sits behind HTTPS once deployed for real. How safe it is depends on who hosts it. The host has to protect the kernel file at shared/book.kernel.json and any keys such as MIRROR_KEY.

Sensible protections run on the host machine. Nothing connected to the internet is breach-proof, and nobody can promise otherwise.

9 · Kids

LIQUA is not meant for anyone under 13, or under the minimum age where you live. Data from minors is never knowingly kept.

10 · Crossing borders

The relayer might run in the United States or somewhere else. Using it from another country means your data may be handled wherever the host sits.

11 · This page can change

This page may get updated. The date line at the top shows the latest edit, and big changes get announced on the project's official channels.

12 · Reaching the project

Privacy, security and abuse contacts are all announced before mainnet.