Hand CricketBack to game →

YOUR ACCOUNT & DATA

Privacy policy

Updated 27 September 2026

Hand Cricket at handcricket.site is a browser game where you play championship opponents or invite a friend. This page explains the information used to run the game. Contact support@handcricket.site with privacy questions or requests.

What we use

Google sign-in is for identifying your account and restoring progress. We do not request access to your Gmail, Drive, contacts or calendar, and we do not receive your Google password.

Who can see it

Your opponent can see your display name, equipped hand and match information. Number choices stay hidden from the other player until the game reveals them. Public rankings, when available, show display names and game statistics. Choose a nickname rather than sharing personal details in your player name.

We use Clerk for authentication, Supabase for the game database, Cloudflare for hosting and abuse protection, and our email provider for support. They process information needed to provide those services; processing may take place outside your country. We do not sell player information or use Google account information for advertising. Information may also be disclosed where required by law or to address fraud, abuse or security incidents.

Cookies and browser storage

The game uses browser storage to remember your guest session, preferences, progress and a match you can rejoin. Clerk uses cookies and browser storage for sign-in. Cloudflare Turnstile checks new guest sessions for abuse. Blocking these features can prevent sign-in or saved progress from working.

Usage analytics

We use Microsoft Clarity on eligible public game pages to understand clicks, scrolling, page performance and masked session replays. It starts automatically without a prompt on eligible visits, unless an earlier opt-out is saved in this browser or the browser sends Global Privacy Control. Our integration sends both analytics-storage and advertising-storage consent as denied; it does not grant permission for analytics or advertising cookies. Microsoft’s SDK may briefly set first-party cookies during startup before these settings take effect. Clarity receives technical information such as the page address, browser and device details, IP address and interaction timing. We do not send your player identifier, Google identity or custom account properties to Clarity.

The game masks page text, inputs and images before Clarity capture. We exclude invitation and sign-in callback URLs, and stop recording before account or support screens. This limits replay detail; masking and denied storage are not promises that all technical data is anonymous. Test sites and previews do not load Clarity or Heap.

We also use Heap on the same eligible public game pages to understand page visits and game interactions. Heap starts automatically under the same earlier opt-out and Global Privacy Control exclusions. Heap session replay is disabled. We disable text capture and redact page titles and sensitive element attributes; we do not send your player identifier, Google identity or custom account properties. Heap receives technical information such as the page address, browser and device details, IP address and interaction timing. It uses first-party cookies and browser storage for analytics identifiers and queued events. Opening account or support screens, following private links or an earlier opt-out arriving from another tab stops both analytics services for the current page.

There is no Analytics menu or consent prompt in the game. Earlier opt-outs saved in this browser remain honored, and browsers sending Global Privacy Control are excluded. Browser settings or extensions can enable Global Privacy Control. Clearing this site’s browser storage removes an earlier saved opt-out, so automatic analytics can start on a later eligible visit unless Global Privacy Control is enabled. A saved opt-out applies only in that browser; it does not delete data already sent.

Microsoft processes Clarity data under its privacy statement. Heap processes analytics under its privacy policy. Our hosting and security services still process the technical information needed to run the game, regardless of whether analytics is active.

TEST performance diagnostics

On our protected test site, we may enable first-party diagnostics for Championship play. They send numeric summaries of entry and reconnection times and eligible active 3D draw intervals, without names, player or match identifiers, page addresses, screenshots or replays. Requests use your current game session; our hosting services still process ordinary connection and authentication information. Daily aggregates are retained for seven days and are not sent to an analytics vendor. Diagnostics are off unless enabled for TEST, honor Global Privacy Control and earlier saved analytics opt-outs, and stop for that page when you open private account, support or purchase flows. Graphics choices do not grant diagnostics permission. Light uses still artwork; these summaries do not measure its frame rate.

Keeping and removing data

Game records are retained to keep your progress and match history. Guest access expires after 90 days without use; this does not automatically delete the underlying record. Clearing browser storage can remove your access to an unlinked guest profile, but does not delete server records.

You can change your display name in the game and sign out at any time. You can also remove Hand Cricket’s access from your Google account settings. To request a copy, correction or deletion of your account and game data, email support@handcricket.site. We may need to verify that the account is yours. Records needed for security or legal obligations may need to be retained; backup copies may remain until the relevant backup expires.

Purchases

Paid purchases are currently disabled. This policy will be updated before paid checkout becomes available.

Changes and questions

The date above identifies the latest version. If you have a concern about information belonging to you or a child in your care, contact us at the support address above.