What StatsBin processes when you use the website.
StatsBin is the website operator and data controller for information processed by this service. Privacy, data-rights, and security requests can be sent to contact@statsbin.com.
Do not send seed phrases, private keys, passwords, identity documents, or payment credentials by email.
StatsBin does not place its own analytics identifier in your browser and does not ask for your name or email address to use the public dashboard. Burn Ads publishers provide a contact email for site verification and operational notices. Affiliate applicants provide an email address, display name, referral code and any optional website or LUNC payout address needed to operate their account.
Standard server and security logs may contain an IP address, user agent, requested path, response status, request identifier, and time. Affiliate authentication records store separate keyed, non-reversible hashes of limited network and user-agent data. These records are processed for legitimate interests in availability, abuse prevention, incident investigation, and service improvement; access is restricted and records are rotated.
Wallet addresses and Terra Classic transactions are public blockchain data. StatsBin is non-custodial: connection and signing happen through the Keplr third-party wallet. StatsBin never receives, stores, or recovers a seed phrase or private key.
Burn Ads records advertiser and publisher payout addresses, publisher contact emails, campaign payment transactions, burn outputs, and publisher payout transactions. Public proof pages may display those public-chain facts, domain names, campaign delivery totals, and aggregate publisher earnings. Advertiser management secrets and publisher session tokens are stored only as one-way keyed hashes on the server.
Publisher login records the payout address, login and logout times, session expiry, and keyed non-reversible hashes of limited request metadata for abuse prevention and incident investigation. The wallet signature is verified during login and is not retained as an account credential.
The embeddable LUNC Burn Ads script does not set a cookie or permanent cross-site browser identifier. For billing integrity, the server converts limited request metadata such as IP address and user agent into overlapping, rotating, keyed non-reversible viewer hashes. The raw values are not written to the ad ledger, and the hashes suppress repeat billing for the same campaign during the six-hour window.
A visit to the StatsBin publisher page through a valid affiliate link uses a signed first-party referral cookie containing the referral code, landing path, first-touch time and expiry. It is used only to attribute a newly registered publisher during the configured referral period and does not track browsing across other websites. Necessary affiliate account cookies authenticate login sessions; StatsBin stores salted password hashes and one-way reset/session token hashes, never raw passwords or tokens.
When no eligible LUNC Burn Ad is available, supported mobile pages may fall back to a third-party advertising provider and consent tools, which can use browser storage according to choices presented in your region. Infrastructure, anti-abuse, blockchain, price-data, email, and advertising processing may involve specialist providers. StatsBin does not sell personal information.
You can clear site data, block optional storage, or change consent choices in your browser. Depending on where you live, you may request access, correction, deletion, restriction, portability, or object to processing. Accounting, fraud-prevention and legal records may need to be retained even after an affiliate account closes. You may also complain to your local data-protection authority; UK users can contact the Information Commissioner's Office.
StatsBin applies encrypted transport, least-privilege services, access controls, rate limiting, verified backups, and security monitoring. No internet service can guarantee absolute security. Last updated: 22 August 2026.
