Privacy

Pools Markets applies data minimization across account, extension and discovery systems. The legal privacy notice at pools.markets/privacy  governs the product; this page explains the technical principles.

Account data

An email can be used to create or restore a Pools Markets account. Account infrastructure may store the identifiers required to authenticate the user and operate secure signing. Raw private keys are not needed by the application for routine transactions.

Onchain activity

Blockchain addresses, positions, transfers, settlements and payouts are public on their respective networks. Pools Markets cannot make public chain activity private or erase it from the chain.

Extension data

The extension can store preferences, account state and short-lived Explore listings locally. Local cache is used to avoid persisting every browsed launchpad asset in the backend. Clearing extension storage can remove non-durable local data.

Discovery and telemetry

Operational metrics should focus on system health, such as mount recovery, panel latency, API failures and stream reconnects. Pools Markets should not collect unrelated browsing history merely because the extension runs on a supported host.

Intelligence sources

When public sources are processed for market intelligence, the system should retain the minimum structured evidence, citations and hashes needed for audit. Source collection remains subject to provider terms and applicable law.