Privacy Policy

Public wallet and card data

We process public blockchain and marketplace records to show digital counts, holdings, recorded activity, collector profiles and listings. A wallet address entered in a lookup is sent to our server and, where needed, to the services that provide that information. We cache checked results to keep the tools responsive and reduce repeated requests.

Public profiles do not verify a person’s identity. A wallet may belong to more than one person, a program or a marketplace. Blockchain records can be public and permanent even when an app stops displaying them. We cannot erase records from a blockchain or another service.

Public stats request limits

The public stats endpoint uses a daily changing, keyed digest of a network address to enforce request limits. IPv6 limits group addresses by network prefix. Raw addresses are not stored in its quota records; expired records are removed on the next request. Hosting services may retain their own access logs.

Usage analytics and cookies

Google Analytics helps us understand which pages and tools people use, including searches, filters, binders, copying, downloads and sharing. Usage is measured automatically while you browse. It receives standard browser and device information and uses cookies to recognise visits. It receives your network address to process requests.

We exclude wallet addresses, wallet holdings, spending amounts, pack counts, search text, entered ownership quantities and clipboard contents from the usage events we send. Collector pages are grouped together, and query strings are removed from recorded page addresses. We do not set an account ID or use advertising features.

We also measure whether a search finds zero, one or multiple cards, how long a binder lookup takes, and page loading, responsiveness and layout stability. These measurements do not include search text or wallet addresses. Analytics is not anonymous simply because those fields are excluded.

Browser privacy tools can limit analytics. You can also control or remove cookies through your browser. Local testing and branch previews do not collect usage analytics. Analytics retention follows the configured analytics account settings; this page does not promise a fixed deletion period that has not been verified.

Information on your device and in requests

Saved marketplace targets and some interface preferences are stored in your browser. You can remove local data using your browser’s site settings. Copies and downloads use your device. Wallets or filters included in a page link may remain in browser history or become visible to someone you share the link with.

Hosting and security services process request information such as network addresses, requested paths, times and errors to deliver and protect the site. This operational processing is separate from the filtered usage events described above. Do not enter private keys, seed phrases or other secrets in the site or bots.

Community bots

When available, bots process commands you send and the chat identifiers needed to reply. We store keyed hashes of user, chat and delivery identifiers to enforce shared rate limits and avoid repeat replies. The application does not store command message history or usernames in these records. Keyed hashes still distinguish repeat activity and are not a promise of anonymity.

Delivery records expire after two days. Usage counters expire at the end of their minute or day. Expired rows are removed in bounded batches during later command processing, so physical deletion may happen later if the bot is quiet.

A public wallet entered in a command is used for that lookup and is not added to usage analytics. Checked wallet summaries come from public chain records. The messaging service can retain your command and the reply under its own policies. Other group members can see Telegram commands and replies. Discord command responses are designed to be private to the person who asked.

Optional support, when enabled

If you contribute to the project’s receiving wallet, transfers may be publicly visible on the network you choose. The daily support check reads configured wallet balances and price quotes; it does not collect a donor name or publish a donor leaderboard. It stores the latest checked balance for each configuration. Older configurations are eligible for cleanup after 30 days during successful updates.

The receiving address can change. Previously sent transfers and old messages can remain public. We do not request a private key or sign a transfer for you.

Who processes information

We use service providers for hosting, database storage, analytics, public chain and marketplace data, price data, and messaging. They may process requests or store information in countries other than yours under their own terms and safeguards. Only information needed for the relevant function should be sent to each service.

Opening a marketplace, source post, game or X sharing link takes you to another website with its own privacy practices. Opening the X composer is counted as opening it, never as proof that you posted. Messages you send directly to santi are also handled through X.

Your choices and requests

You can browse without submitting a wallet or using a bot. Those inputs are optional, but the corresponding lookup needs them. Use browser controls to limit analytics and clear saved site data. Avoid posting a wallet in a group if you do not want members to associate it with you.

Contact santi to ask about information we hold, request access or correction, raise a privacy concern, or request removal from a public profile display. We may need enough information to verify the request, but will not ask for a private key. A request cannot remove public blockchain records, another platform’s messages or data we cannot identify from the information provided.

DM @santi_ on X Please keep sensitive information out of a public post.

Policy updates

We will update the date on this page when the policy changes. See the Terms of Service for the rules and limits of using Mudwater Stats.