Privacy and browser storage

Accounts, activity and requests

When you use account features, the service processes the account information you provide and activity such as picks, profile settings, community posts and paper-tracking records. Public posts and leaderboard information may be visible to other visitors. Do not post sensitive personal details or credentials in public discussion.

Web requests can include network information such as IP address, browser headers, requested URL and time. The service and hosting infrastructure use request information to deliver pages, diagnose failures and protect operation. This notice does not claim a retention period that has not been verified.

Browser storage used by the application

The application uses localStorage and sessionStorage for features including authentication tokens, cached account/lock information, game views, paper-slip selections, preferences and the storage-notice choice. These are browser storage mechanisms, not all cookies. Clearing them can sign you out or remove local preferences; it does not automatically delete server-side account records.

Signing out removes the stored authentication state through the app’s sign-out action. Your browser’s site-data controls can clear other local records. Do not share a device while leaving an authenticated session or an API key saved in that browser.

Optional AI and provider keys

Basic player profiles do not require AI. Explicit optional AI requests can send the requested analytical inputs to Groq. If you enter a personal Groq API key in the profile interface, the current implementation stores it in this browser’s localStorage and includes it in the relevant request header. Do not enter a key on a shared or untrusted device.

An AI explanation is separate from verified source statistics and can be wrong. Do not include private account information in analytical prompts. Provider services have their own terms and privacy practices; see Groq’s privacy policy and its Cloud Services Agreement / Data Processing Addendum before using that optional feature.

Advertising is currently paused

The Google ad-serving script is not loaded in the current review release. The site retains its publisher verification meta tag and ads.txt record, which do not themselves run advertising JavaScript. The storage notice is not represented as a Google-certified consent management platform, and its acknowledgement does not authorize a new ad integration.

If advertising is enabled in a future release, its eligible pages, data flows and appropriate consent controls need to be configured and disclosed first. Google explains how its advertising products use data at How Google uses information from sites or apps that use its services. No statement here promises approval or legal compliance.

External links and source media

Player images, team marks and linked reporting may come from third-party sources. Loading externally hosted media can send a normal web request to that provider. Following an external link takes you to a service with its own privacy practices. The site does not claim affiliation or endorsement by those providers.

Private requests and unresolved contact gap

A verified private support email has not yet been configured. The former support address was not confirmed as a working inbox and is no longer published. The contact page describes a public-community route for non-sensitive corrections, but public posts are not a suitable channel for private account or privacy requests.

The operator needs to provide a verified private route and review applicable request-handling duties. Do not post your password, API keys, identity documents or private account details in public. This disclosed gap should be resolved before declaring the site fully ready for another advertising review.