Pool Online Privacy Policy

Browser Storage and App Caches

AI and local two-player games store positions, shot logs, rules, AI difficulty, break order, aim and strike-point settings in the current browser. Theme, sound and panel state also use browser storage. There is no account-based cross-device sync.

Online mode stores a random browser identifier, recent and current rooms, host credentials, invite credentials and seat-recovery identifiers. Some values are written to both localStorage and sessionStorage for room management, reconnection after a refresh and seat recovery. These are not accounts, but access credentials must be kept private.

AI shot calculations run on your device; the local game need not be sent to a cloud AI engine. The page can still make network requests for resources, analytics and online features.

Adding the site to your home screen or Dock may retain icons, app information and static caches in the browser or operating system. Caches reduce repeated loading; they are not permanent saves and do not guarantee every page works offline. Whether uninstalling clears site data depends on the browser and system.

Online Rooms and Access Credentials

Online play sends room requests, rules, break order, credentials, game state, aim, power, strike point and ball-in-hand placement through room APIs and WebSocket. The server uses these to rule on shots, sync play, manage seats, handle resignations or draws, and track room creation and activity times.

Players and spectators in a room can see the game, turns, score, generic player labels and connection status. The public lobby lists public room codes, status, break settings, player labels and occupancy. Private rooms are unlisted, but a person who obtains a valid room link may still join or watch.

Room codes, invite credentials, seat-recovery credentials and host credentials grant different access. Use the invite feature rather than copying an active address-bar URL that contains your seat credentials. Someone with recovery credentials may reclaim that seat. Redact credentials from screenshots too.

To limit repeated room creation, the server processes hashed IP identifiers and request counts. Public-room management also uses a hash of the random browser identifier. Hashing distinguishes rate-limit records; it does not make them fully anonymous. Hosting services may still process the original IP address needed for requests.

Analytics, Hosting and Advertising

The production site uses Google Analytics 4 (measurement ID: G-8EWY47HNXY) to understand page visits and usage. Data may include page URLs, referrals, device and browser details, approximate region and analytics identifiers, and may use analytics cookies.

The measurement ID is shared with other Ply Yard game sites. Visits from the same browser across related subdomains may be associated. Analytics storage is currently enabled by default; ad storage, ad user data and ad personalization are set to denied. Denying advertising does not also disable analytics cookies.

Room codes, invites or seat parameters in page URLs may be processed by automatic page analytics or technical requests. Do not publish full URLs containing those credentials. Clearing a local save does not withdraw analytics data already sent.

Cloudflare provides hosting, online infrastructure and security. It may process IP addresses, request times, page URLs, browser headers and operational logs to deliver content, prevent abuse and investigate faults. Providers' processing and retention also depend on their configurations and privacy policies.

Ad scripts are currently disabled and the site has no in-page analytics switch. Browser privacy settings or content blockers can limit analytics requests. Blocking only analytics does not stop core play; disabling site storage or all scripts can affect saves, shots or reconnection.

Support Email and Children

If you email contact@plyyard.com , we receive your sender address, email headers, text, screenshots, attachments and device details you include. We use them to check reports, reproduce issues, reply and handle privacy requests, not to build a marketing list.

Send only relevant information. Redact private details and room credentials. Do not send passwords, payment details, identity documents or someone else's sensitive information.

The site does not request ages or provide age verification. Guardians should help children avoid publishing private-room links or including names, schools, contact details or other identifying information in reports and screenshots.

Retention and Clearing Data

Browser settings, storage and the relevant scripts determine how long local progress, preferences and analytics cookies remain. New game replaces the current rack, not all preferences, room credentials or analytics data.

Rooms expire according to state and activity. These are the current defaults, not deletion deadlines for all data. New activity, state changes or service configuration can alter the expiry time.

Closing or expiring a room clears its game, seat information and access credentials on the server and removes it from the lobby. Closed-room records still retain details such as the room code, rules and times. An old link cannot restore the game from that record.

Room-creation limits use a 10-minute window. Public-room occupancy records are released according to room state; an unreleased abnormal record expires after a 3-hour window. Expired records are cleaned during later operations, not necessarily deleted at the exact expiry time.

Technical logs, analytics and email do not use room expiry limits. There is no single promised automatic-deletion period for them. Contact us about retention or to request access, correction or deletion.

To clear local data, find this site's domain in your browser's site-data or storage settings and clear the relevant storage, cookies and caches. Options vary. Deleting browsing history or uninstalling the app may not remove saves.

Local clearing does not delete server records, emails, browsing history, bookmarks or shared links. Reopening an old URL with valid recovery credentials may still restore a seat. To invalidate room credentials, the host must close the room or let it expire.

Policy Updates and Privacy Contact

Material changes to storage, room services, analytics or advertising will be reflected here with an updated date. This policy covers this site only; check the policies of external sites you visit.

For a privacy question or data request, include the domain, data category, relevant time range and action requested. We assess requests against identifiable records and applicable requirements; we cannot guarantee matching every third-party analytics record to you.

Privacy contact: contact@plyyard.com