Privacy

Privacy

How tx.taxi handles lookups, logs, and redirects. No user accounts, no tracking pixels, no personally identifiable information collected by design.

The short version

tx.taxi is a lookup router. You paste a value, the service classifies it, and you get redirected to a third-party block explorer. We do not run user accounts. We do not collect personally identifiable information. We do not sell data. The longer version below explains what does and does not happen on the server side.

What tx.taxi sees

When you visit tx.taxi/{value}, the value in the URL is processed server-side so the resolver can classify it and pick a destination explorer. The value itself is, by design, public information - a blockchain address, transaction hash, block hash, or block number is not secret. Pasting one at a public router does not reveal anything you would not also reveal by pasting it into the destination explorer directly.

Standard HTTP request metadata - source IP, user agent, referer, timestamp - may be present in operational logs the same way it would be on any web service. tx.taxi keeps logs minimal and operational: enough to debug failures, measure load, and detect abuse, not enough to build a profile of a specific person.

What tx.taxi does not do

  • No user accounts. There is nothing to sign up for and nothing to sign in to.
  • No tracking pixels or third-party advertising trackers embedded in the page.
  • No selling of lookup history, IP addresses, or any other request data to third parties.
  • No deliberate collection of personally identifiable information. The product does not ask for your name, email, wallet, or any other personal field.

Server-side processing

Lookups are processed server-side because the resolver needs to run regex classification and, for ambiguous inputs, bounded probing against public RPC or API endpoints. That work happens inside the tx.taxi service and is not visible to the destination explorer until the redirect lands.

The chain registry, RPC endpoints, and explorer list are static configuration. The resolver decision is made from your input plus that configuration. There is no machine-learning model, no user-history-based ranking, and no behavioral targeting.

Redirects to third-party explorers

When the resolver picks a destination, tx.taxi issues a 302 redirect to a third-party block explorer - for example Etherscan, Solscan, BscScan, mempool.space, Tronscan, Tonviewer, SuiVision, and others depending on the detected chain. Once your browser follows the redirect, the destination explorer sees your request directly. Each of those services has its own privacy policy, logging behavior, and analytics setup. tx.taxi has no control over what they collect, and we cannot make promises about third-party services.

If you have a privacy concern about a specific destination explorer, read that explorer's privacy policy directly. The tx.taxi side of the interaction ends at the redirect.

API usage

The public REST API at /api/v1/resolve returns the same routing decision as the browser redirect, in JSON, for integrations like wallets, bots, and dashboards. The same posture applies: no accounts, no PII collection, minimal operational logs, and your input value is treated as public information.

Changes

This policy can be updated as the service evolves. Material changes to logging, data handling, or third-party integrations will be reflected here. See /contact if you spot a claim on this page that does not match the behavior you observe.