Privacy

This site has no accounts, no login, no advertising and no third-party analytics. It sets no tracking cookies and embeds no social widgets that would set them on our behalf.

Pages are prerendered as static files. A request reaches the hosting provider, which necessarily processes your IP address and user agent in order to serve a response and to keep operational logs. That processing is the hosting provider's, and it is the minimum required for a web server to function.

The language preference is expressed in the URL — `/en/…` or `/ru/…` — rather than stored in a cookie, so switching language leaves nothing behind on your device.

If you contact the project through a public channel such as the repository issue tracker or a group chat, that platform's own privacy policy applies to the message and to your account there.

There is no contact form on this site and no endpoint that accepts personal data.

This is the part that a conventional privacy policy would omit. A public ledger is designed to be permanent and universally readable. Addresses, balances, transaction amounts and timing are visible to anyone, forever, and cannot be deleted, corrected or withdrawn by us or by anyone else.

Addresses are pseudonymous, not anonymous. Analysis of transaction patterns, timing and amounts can link addresses to each other and, in combination with information from outside the chain, to a person.

Because on-chain records cannot be altered, rights that assume a controller can erase or rectify data — such as those under the GDPR — cannot be exercised against the ledger itself. Consider this before putting anything on any chain.

Running a node means participating in a peer-to-peer network. Peers observe your IP address, and the consensus model additionally observes the autonomous system a node announces from, because network diversity is one input to node weight.

Operators who want to reduce that exposure should treat it as an infrastructure decision, made before joining rather than after.

This document changes when the deployment changes. The date above is the date of the last revision.