Privacy and analytics choices

Data needed to play

Room discovery and signaling use Cloudflare infrastructure. Public room names, capacity and availability are visible in the directory. Nicknames, chat and match state are shared with the relevant room participants. Direct peer connections can expose network addresses to peers.

Security and admission services process connection information to operate rooms and limit abuse. This technical processing is separate from optional usage analytics. Do not put personal or sensitive information in room names, nicknames or chat.

Optional accounts

Accounts use Supabase authentication with email and password, Google or GitHub. Google and GitHub share the identity and email information needed for sign-in; Ball2D does not request access to repositories or files. Resend delivers email verification and password recovery messages through auth.ball2d.com. The account service stores the profile and email information needed for sign-in, team membership and SDK API key management. Anonymous browser play does not require an account.

SDK API keys authorize native room admission and session quotas. Account credentials, email addresses and API keys are not sent through gameplay analytics or the match simulation.

Your device and files

The browser can remember your nickname and settings locally. Stadiums and replay exports are downloaded to your device; replay imports are opened locally. A replay may contain player names and match activity, so review it before sharing.

Your analytics choice is stored locally for up to 180 days. If browser storage is unavailable, Ball2D leaves analytics off. Clearing site data removes local preferences and may cause the choice to be requested again.

Optional usage analytics

Only after you choose Allow analytics does Ball2D load Google Analytics. It measures public guide views and bounded gameplay events, such as room searches, join attempts, successful connections, practice starts, match participation, replay actions and session durations.

Analytics excludes room IDs, invite codes, passwords, host tokens, nicknames, chat, search text, custom stadium source, replay files and raw error messages. Page addresses are reduced to known public paths without query strings or fragments. Referrers are reduced to their origin. Google can still process network and device information when a request reaches its service.

Analytics is disabled when Global Privacy Control or Do Not Track is enabled. Advertising storage, advertising user data and advertising personalization remain denied. Declining analytics does not prevent play. Optional analytics counts consenting browsers, not every person who visits.

Change your choice

Use Analytics choices in the footer to allow or decline collection at any time. Declining disables subsequent measurement and clears this site’s Google Analytics cookies. Data already received by Google is not retroactively deleted by changing a browser preference.