Privacy Policy

Draft — no effective date

Placeholder — not in effect.This policy has not been written. The text below is structural filler to lay out the page, it has had no legal review, and it does not state the terms that apply to anyone. Do not rely on it, cite it, or treat acceptance of it as agreement to anything.

1. Who is responsible

This section will identify the data controller and how to reach them.

2. What is collected

The real policy needs to account for at least the following, all of which the service handles today:

Wallet addresses. Public on-chain identifiers, linked to trades, token launches, chat messages, and holdings.
Consent records. An address, a timestamp, the document version accepted, and the wallet signature proving it.
Content you submit. Token names, tickers, descriptions, images, social links, and chat messages.
Network metadata. IP addresses, used for rate limiting and abuse prevention.

3. What is public and permanent

This section needs to be unusually plain. Anything written to the blockchain — every trade, every launch, every transfer — is public, permanent, and outside the operator's control. It cannot be edited or deleted on request, by anyone. Token images and metadata pinned to IPFS are similarly public and may persist on nodes the operator does not run.

4. Third parties

This section will list the processors and infrastructure providers involved — the hosting provider, the RPC provider used to read and broadcast chain data, and the IPFS pinning service used for token images — and what each one receives.

5. Cookies and local storage

This section will describe what is stored in the browser. Today that includes a theme preference and wallet connection state.

6. How long data is kept

This section will set retention periods for the off-chain data — consent records, chat, indexed trade history — and acknowledge that on-chain data has no retention period because it cannot be deleted.

7. Your rights

This section will describe access, correction, deletion, and objection rights under the applicable regime, and will have to be explicit about which of them cannot be honoured for on-chain data and why.

8. Security

This section will describe the measures protecting off-chain data, and state clearly that the operator never has access to user private keys or funds.

9. Changes to this policy

This section will describe how changes are published and re-accepted. The consent record stores a document version for this purpose.

10. Contact

This section will give a contact address for privacy requests.