Nothing to collect.

Looking up an address. The server reads public blockchain data and, when a record names a GitHub repository, that repository's public tally.json. It keeps the answer in memory for 30 seconds so a busy badge does not repeat the work. The addresses involved are public and are not tied to you.

Registering a contract. Your wallet signs in your browser; Tally never receives a key. The page remembers, in your browser only, the network you chose and the contracts you registered from it. Clearing the site's data removes that.

Hosting. The studio runs on Vercel, which keeps standard request logs (IP address, browser and URL) to run and protect the service. The studio adds no cookies, trackers or analytics of its own.

What it reads. On the block explorer pages it supports, it reads the contract addresses in the page's address and links. For each one, its background worker asks the network's public RPC endpoint for the registry record, and asks raw.githubusercontent.com for the repository's tally.json. So the addresses on pages you view are sent to those servers, as with any web request. Nothing goes to Tally's own servers unless you click a badge, which opens that address in the studio.

What it keeps. One setting in its popup: the network you chose last. It collects no browsing history and no personal information, runs no analytics, sells or shares nothing, and loads no remote code.