What WagerDB stores and what it does not: no accounts, no third-party analytics, no advertising cookies. One localStorage key, and it is only for the admin panel.
No user accounts, no newsletter, no advertising network and no third-party analytics. We set no tracking cookies and build no profiles.
One key, wagerdb_admin_token, and only if someone logs into the admin panel. Uploads to the P&L analyser are parsed in the browser and never leave your device.
Ordinary web server logs — IP, timestamp, path, user agent — kept to keep the site up and to enforce the per-IP rate limits that stop bulk scraping. Not joined to anything else, not used for advertising.
Our data comes from public blockchains and public operator feeds. Player names in bet feeds are the display names operators broadcast publicly and already mask; accounts that hide their bets never appear here. We do not correlate handles across operators. Removal requests go to [email protected].
Pages that embed a provider’s free demo load that iframe from the demo host’s own domain, so that host sees the request. Nothing else on the site loads third-party scripts.
Some demo hosts fund their free catalogues by injecting their own casino promotions into the game frame. We do not embed those: such a demo opens in a new tab on the host’s own site, so no other operator’s advertising is ever rendered on a WagerDB page. We take no commission on anything shown there and it is not an endorsement. Demos we do embed are sandboxed — the frame cannot open tabs or navigate you away from this site. If you see a third-party advert inside a page here, that is a bug: report it to [email protected].
WagerDB is built on a strict privacy-first foundation. We believe that financial calculations, betting models, seed verifications, and gambling analytics must remain completely private to the user.
Unlike conventional casino affiliate sites that deploy aggressive third-party trackers, retargeting pixels, and tracking cookies, WagerDB operates with zero user tracking and zero third-party advertising scripts.
All mathematical tools — including the P&L CSV Analyzer, Wagering Requirement EV Calculator, Kelly Sizer, and Provably Fair Hash Verifiers — execute 100% locally in your browser memory via WebAssembly and JavaScript.
When you upload transaction CSVs or paste private client seeds, that data is processed entirely on your local machine. No file contents, stake amounts, or calculations are ever transmitted to or logged on our servers.
WagerDB does not use tracking cookies, browser fingerprinting, or marketing analytics suites (e.g. Google Analytics, Facebook Pixel). Local storage is utilized strictly for basic client preferences (such as dark theme or simulator sound settings).
No. The P&L Analyzer parses your CSV file strictly in browser RAM. When you close or refresh the tab, the parsed data is immediately purged from memory.
No. We do not collect personal data, email addresses, or gambling histories, making it impossible to sell or share user data with third parties.