Privacy

Effective 2026-08-02. Short version: we measure how dTAOscan is used so we can improve it. We set one first-party cookie, keep a short-lived usage log, and run Google Analytics if you accept it in the cookie banner. If you buy access, we record the payment. We do not sell your data, we do not share it with data brokers, and we do not run ads.

Why we collect any of this

One reason: to understand how the site is actually used so we can improve the experience and the product. Which pages people find, what they look for, what breaks, whether anyone is here at all. That is the entire purpose. It is not sold, it is not shared with data brokers, it is not used to target advertising, and it is not used to build a profile of you as a person.

What we process

We set a single first-party cookie, dt_uid, a random opaque id (not linked to your identity) used only to count anonymous usage. We keep a bounded usage log (request path, coarse region and datacenter from Cloudflare, user-agent, and that opaque id) pruned to a rolling 14-day window. Your IP address enforces API rate limits and appears in standard Cloudflare logs, retained briefly for operations and abuse prevention. If you pay via x402, we record the payment authorization (payer address, amount, resource) to deliver access and settle on-chain. API keys and Pro passes are associated only with the fact of their use. Beyond this, the only third-party analytics is the optional, consent-gated Google Analytics described below; no ad networks run on dTAOscan.

Analytics (optional, consent-gated)

We use Google Analytics 4, a web analytics service provided by Google LLC (and, for visitors in the EEA and the UK, Google Ireland Limited), to understand how visitors use dTAOscan. It runs only if you accept it in the cookie banner. If you decline, or ignore the banner, no analytics code loads and nothing is sent to Google.

If you accept, Google Analytics collects: the pages you view and how you arrived; approximate city-level location derived from your IP address (Google Analytics 4 does not log or store the IP itself); device information such as browser, operating system, screen size, and language; and a random identifier stored in first-party cookies (named _ga and _ga_ plus a container id) so repeat visits count as one visitor. We do not send Google any wallet address you look up, we do not use analytics data for advertising, and we do not sell it. Google processes this data on our behalf as a data processor under Google's data processing terms, which include the EU Standard Contractual Clauses where they apply; data may be processed in the United States, and Google LLC participates in the EU-U.S. Data Privacy Framework.

Retention: Google Analytics keeps this data for up to 14 months, then deletes it automatically; the _ga cookies expire after at most two years. Your consent choice stays in your browser until you change it: use the Cookie settings link in the footer at any time. Switching analytics off deletes the Google Analytics cookies for this site and stops any further collection.

Address lookups

When you look up a wallet, the address you enter is a public Bittensor coldkey and its positions are public on-chain data. We cache the computed result for a few minutes to avoid re-reading the chain, keyed by that public address, and we do not link it to you, your IP, or any identity. Looking up an address is not a claim that you own it.

What we do not do

We do not sell your personal data or share it with data brokers. We do not run advertising, we do not build advertising profiles, we do not fingerprint your device, and we do not send marketing email. Analytics cookies are set only if you accept them, and you can withdraw that at any time from Cookie settings in the footer.

Third parties

The site is served via Cloudflare. If you accept analytics, your browser talks to Google Analytics as described above. Subnet logos are loaded from URLs their owners published on-chain, so your browser requests those images from third-party hosts; if you object, block third-party images. Chain data comes from public Subtensor RPC endpoints; your requests never reach them.

Contact

Privacy questions: via DRM3 Labs (drm3.io).