Privacy & data

When you look up a wallet

The tracker sends the public addresses you enter to our server to read balances and stake from Bittensor through a chain node. Server lookup jobs store those addresses, progress and results so the check can finish and resume. A job identifier retrieves the results; avoid sharing it if you do not want others to see the lookup.

Opening recent activity sends that wallet address through our server to TaoStats for indexed signed transactions and incoming/outgoing TAO transfers. Responses are cached for reuse. Public-chain balances and transactions can reveal financial activity even without a name attached.

Wallet links can include an address in the URL. Anyone you share that link with can see it. Requests and URLs may also be visible to hosting, network and data providers. Hiding amounts changes the display; it does not remove the underlying data or hide it from those providers.

What stays in your browser

The site uses local storage for last-checked wallets and holdings, a resumable job identifier, market/price caches, chart drawings, indicator colors and drawing-tool preferences. Some notices use session storage to remember dismissal for the current browser session. These copies are specific to this browser and profile; people using the same profile may see them.

Saved wallet results do not have an automatic browser expiry. They may remain until you remove them, clear site data or the browser removes them. A saved snapshot is not a fresh lookup.

Server storage & deletion

Our wallet worker’s configured default makes completed and failed lookup jobs eligible for deletion after 24 hours without an update. Cleanup checks run about hourly while the worker is operating. This is not a promise of deletion exactly 24 hours after you submit a lookup; queued or processing jobs are not covered by that cleanup rule.

Recent-activity responses normally use a five-minute cache, with stale responses sometimes served during refresh. A cache’s refresh interval is not a guarantee that every stored copy has been erased.

Application jobs, hosting/security logs, backups and provider caches are different records. We have not established one verified deletion period covering all of them. Older wallet snapshot records, where present, are not covered by the job cleanup rule. Browser clear/remove controls do not issue a server-side deletion request.

For help with server-held lookup data, email a privacy request. We can review what we control; we cannot erase Bittensor’s public history or promise deletion of records independently held by other services.

Other services you may interact with

• Hosting and chain data: Vercel serves the website, and the backend is hosted on Render. Requests can include IP address, browser information, URL and diagnostic information. Chain/RPC providers and TaoStats receive the public data queries needed for their features.
• Videos: embedded players use YouTube’s privacy-enhanced youtube-nocookie.com domain. Loading or playing a video contacts Google/YouTube; privacy-enhanced mode does not mean no data is transferred. Membership access is handled by YouTube.
• Bookings, purchases and community: Calendly, Stripe, the merchandise store, Telegram, X, partners and other linked sites handle their own interactions. Affiliate/referral links may identify Shizzy as the referrer. Their policies apply after you follow those links; we do not receive your payment-card details through the site’s checkout links.
• Contact: if you email or message us, the service you choose processes that communication. We use what you provide to respond and handle the request. No fixed deletion period for correspondence has been established.

Provider information: Vercel privacy notice · Render privacy policy · Google privacy policy.

Traffic & performance measurements

The site includes Vercel Web Analytics and Speed Insights to understand visits and real loading performance. Measurements can include page/route, referrer, browser/device information, approximate location and performance timings. Hosting and security logging are separate from analytics.

Vercel describes Web Analytics as cookie-free and uses an anonymous visitor identifier rather than a persistent tracking cookie. That does not make every service on this site cookie-free, or mean your IP address never reaches a server. Embedded media and linked services have their own storage and data practices.

We measure clicks to a fixed list of site sections and partner services. These events identify the destination category only, not a purchase or completed booking. They do not include wallet lists, balances or raw search text. Analytics URLs have query strings, fragments and recognized wallet addresses removed. The local subnet watchlist stores subnet numbers on your device; Clear watchlist removes that list. URLs themselves can carry information, so do not place secrets in links or inputs. Your browser’s privacy controls and content-blocking tools may limit third-party measurement; clearing local site data alone does not disable future analytics.

How Vercel Web Analytics handles data · About Speed Insights

Questions, corrections or privacy requests

Contact Shizzy Unchained at shizzyunchained@gmail.com. Tell us the feature and approximate date involved, and what you want us to review. Include a public address or job identifier only if needed—never a seed phrase, private key or password.

This notice describes the current site. We will update its date when these practices change.