PRIVACY POLICY

version 0.1 draft · last updated [DATE TBD] · plain-English honest version

⚠ DRAFT. This document is a starting point. It has not been reviewed by counsel. Before public launch, get a real lawyer (especially for GDPR / CCPA / MiCA compliance in your target jurisdictions).

± Short version. Liqua collects very little. We don't use cookies. We don't run analytics scripts. We don't track you across the web. Your wallet address and the transactions you sign are public on the blockchain — that's not us, that's how blockchains work. Off-chain, we keep an in-memory list of recent orders and chat messages for the relayer to function.

1 · Scope

This policy describes how the off-chain components of Liqua (this website, the relayer at relayer/server.js) handle data. It does not apply to the blockchain itself, which is operated by independent nodes outside our control.

2 · What we collect (off-chain)

data	why	where it lives	retention
Wallet address	identify maker on an order · receiver on a chat message	in-memory + `shared/book.kernel.json` on the relayer host	until the order expires, the chat message ages out of the 200-message ring, or the host is restarted
Signed order data	serve the orderbook to other users	in-memory + kernel JSON	until expiry or fill
Signed chat messages	display in the chat panel	in-memory ring buffer (200 cap) + kernel JSON	last 200 messages
Request IP address	basic rate-limiting / abuse prevention	web server logs (rotated)	~7 days
Error reports (if Sentry is enabled)	debugging	Sentry servers	per Sentry retention (typically 30–90 days)

3 · What we don't collect

No cookies. We don't set tracking cookies. Your browser may store wallet state (e.g. MetaMask's permissions) but that's the wallet, not us.
No analytics scripts. No Google Analytics, no Mixpanel, no Segment, no Facebook pixel, no Hotjar.
No PII. We don't ask for name, email, phone, address, ID, or anything else identifying. We can't, because we don't have accounts.
No fingerprinting. No canvas fingerprinting, no font enumeration, no browser fingerprinting.
No cross-site tracking. We don't share data with ad networks.

4 · What's on-chain (and we have no control over)

Anything you do on the blockchain — placing orders, signing transactions, transferring tokens, voting on governance proposals — is permanently public. Anyone can see it on a block explorer. We did not put it there; the blockchain did. Once on-chain, it cannot be deleted.

If you require privacy for your trading activity, use a fresh wallet per session, or use a privacy-preserving mixer or zkRollup. Liqua does not offer this; it's a transparent-by-design DEX.

5 · Embedded third-party scripts

Some pages load resources from third parties to function:

ethers.js via cdnjs.com — Ethereum signing + RPC client
TradingView widget on the main trading page — real-time market chart (loads from s3.tradingview.com)
Binance public WebSocket feed (relayer-side, not your browser) — live ETH/USDT depth

These services have their own privacy policies and may log your IP address when their resources load. We do not control their data handling.

6 · Sharing

We do not sell, rent, trade, or otherwise distribute the data we hold. We may disclose data if required by lawful subpoena or court order in a jurisdiction where we operate.

7 · Your rights

Because we hold very little data, most data-access requests resolve quickly:

Access: we'll tell you what we have on you (typically: your wallet address showing up in the recent book / chat / trades).
Deletion: we'll remove your wallet address from off-chain stores on request. We cannot remove on-chain data.
Correction: rarely relevant — what we hold is signed by you, so the chain of evidence is what it is.

Send requests to [privacy@liqua.app · TBD]. We aim to respond within 30 days.

8 · Security

The off-chain relayer is a standard Node.js application running behind HTTPS (in production). Operational security depends on the deployment — whoever hosts is responsible for keeping the kernel file (shared/book.kernel.json) and any keys (MIRROR_KEY) safe.

We use commercially reasonable measures to protect the relayer's host environment. We cannot guarantee absolute security; no internet-connected system is fully immune to compromise.

9 · Children

Liqua is not directed at children under 13 (or the applicable minimum age in your jurisdiction). We do not knowingly collect data from minors.

10 · International users

Liqua's relayer may be hosted in the United States or other jurisdictions. By using the service from outside, you consent to data transfer to and processing in the host country.

11 · Changes to this policy

We may update this policy from time to time. The "last updated" date at the top reflects the most recent change. Substantial changes will be announced via the project's official channels.

12 · Contact

Privacy questions: [privacy@liqua.app · TBD]. Security disclosures: [security@liqua.app · TBD]. Abuse reports: [abuse@liqua.app · TBD].