PRIVACY FIRST, CHAIN BY CHAIN

tx.taxi is a multi-chain explorer. The data visible for each chain follows that chain's design and the active tx.taxi capability manifest. Transparent fields may be displayed when the chain makes them public. Privacy-preserving fields, such as Monero RingCT amounts and recipients, stay hidden unless a supported browser-only reveal flow can decode them locally.

PRIVATE KEYS NEVER LEAVE THE BROWSER

For Monero key reveal, private view keys are processed in the browser. tx.taxi must not send private view keys, spend keys, seed phrases, mnemonics, or equivalent secret material to the backend over HTTP, websocket, analytics, logs, or any other channel. The server may provide public chain data needed for local scanning, but the secret key material remains local to your browser.

USING THIS WEBSITE

When you load pages, use search, call APIs, or connect to the websocket relay, tx.taxi receives the requests needed to serve those features. Requests may include public identifiers you choose to look up, such as transaction ids, block hashes, addresses on chains that support public address lookup, route paths, selected chain/network context, browser metadata sent by your client, and IP address information visible to the server.

LOGGING AND OPERATIONS

tx.taxi may keep minimal server, API, websocket, error, and source-health logs needed to operate, debug, secure, and measure the service. These logs should not intentionally include private key material. Operational logs may include IP addresses, user-agent strings, requested URLs, response status codes, timing data, and upstream source errors.

LOCAL BROWSER STORAGE

The frontend may store local preferences such as language, theme, time display, units, and similar UI settings. Key reveal state is designed as browser-local UI state; do not paste secret material into tx.taxi unless you intend to run the local reveal flow in that browser session.

THIRD-PARTY AND HOSTED SOURCES

tx.taxi backends may query public or hosted chain nodes, p2pool observer data, and other configured data sources. Those sources are used by the server-side adapter layer to build chain-contract responses. Browser users should not need to send private keys to those sources through tx.taxi.

ACCOUNTS, PAYMENTS, AND ADVERTISING

Phase 1 tx.taxi explorer pages do not require user accounts for normal browsing. If tx.taxi later adds account, payment, sponsorship, acceleration, or paid API features, those features need explicit policy text before they are advertised as available.

SELF-HOSTING

For maximum control, use a self-hosted explorer connected to data sources you operate or trust. tx.taxi is built from upstream mempool.space under the AGPL and keeps configuration-driven data-source boundaries so operators can replace hosted development sources with production sources without changing privacy guarantees in the browser.

EOF