Normal local calculation
Selecting cards and calculating does not call a Poker Odds Calculator application API, and the calculation panel is masked from Clarity.
This policy describes the current static site behavior. Browser calculation keeps cards, ranges, bankroll values, and results off an application server. Google Analytics and Microsoft Clarity load by default to measure site use and usability, while a share URL contains calculation state only when you explicitly create one.
How the result is built
Card and numeric inputs are validated and calculated locally. Larger supported jobs move to a same-origin Web Worker, then render back into the page.
Hole cards, boards, ranges, amounts, payouts, iterations, seeds, and results remain in browser memory during ordinary use. High-load work moves only to a same-origin Web Worker. Calculator panels are marked for Microsoft Clarity content masking so their fields and displayed results are not uploaded as recording content.
Theme and similar non-sensitive local settings may be stored in LocalStorage. A language switch may use same-origin SessionStorage for a one-time equity draft handoff lasting no more than 30 seconds. Clicking Share writes the minimum restorable state into the visible URL. Anyone who receives that URL—and Microsoft Clarity when active—may see its query parameters; the Google Analytics page location is sent without the query.
Google Analytics loads by default and records pseudonymous usage such as page visits, session statistics, approximate location, browser, and device information. The implementation sends a query-free page location and keeps advertising storage, advertising user data, and ad personalization denied. Google may use first-party Analytics cookies to distinguish visitors and sessions.
Microsoft Clarity loads by default and measures page rendering and interactions such as clicks, pointer movement, and scrolling to identify usability problems. Clarity may use cookies for session continuity and can create masked session replays or heatmaps. Calculator content remains inside the masked boundary described above.
The two analytics tags load automatically, without an on-site permission popup or stored analytics choice. Browser content-blocking settings can prevent third-party scripts or cookies from loading, and browser site-data controls can remove vendor cookies after a visit.
Analytics data is processed under Google’s and Microsoft’s policies and retention settings. Static hosting and network providers may keep ordinary security and delivery logs under their own policies. The contact link opens your email client; the sender’s provider and monitored recipient mailbox handle that message.
Selecting cards and calculating does not call a Poker Odds Calculator application API, and the calculation panel is masked from Clarity.
Analytics loads on a normal visit. If you open a share URL, its visible parameters can be seen by Microsoft Clarity as well as anyone who receives the link; Google Analytics receives a query-free page location.
Yes. Google Analytics and Microsoft Clarity load automatically on site pages.
Non-sensitive preferences such as theme; calculation history is not stored there.
Yes. Its visible query parameters can be seen by recipients, browser history, hosting logs, and Microsoft Clarity.
Calculator fields and displayed results are inside a Clarity masking boundary.
No. The site has no account or calculation database, and ordinary calculations stay in the browser.