Why your address is used
The data comes from Sona's API, which gives every visitor a small request budget. To tell visitors apart, the website passes your IP address to the API with each data request, and the API counts your requests against it.
Without this, one busy visitor would use up the budget for everyone behind the website. The address is used for nothing else.
What the API keeps
The API keeps two short-lived counters per visitor in its state store.
- A rate limit counter, stored under your address. It exists only until your request budget refills, which is seconds.
- A daily credit counter, stored under your address and the UTC date. It is deleted at the next UTC midnight.
For IPv4 the counter uses the full address. For IPv6 it uses only the first 64 bits, the network part. A cruder in-memory check groups IPv4 addresses by their first three numbers, and it forgets an entry within seconds of its last request. If the state store is unavailable, the same counting runs in the API's memory and is lost on restart.
The API's application log records only errors and warnings, such as a crashed request or a failed refresh. The code that writes it does not include the visitor address. Responses are cached and shared between visitors, so they are not tied to you.
What the website keeps
The website server holds your address in memory only, to space out its calls to the API for you. It keeps at most 10,000 addresses at a time and drops each one after 10 minutes without a request. The website code does not write addresses to a log, a file or a database.
Addresses you look up
Addresses, transactions and blocks you search for are public chain data. Searches are sent to the API to get an answer. The code does not store them against your visitor address.