This page explains what the Gomoku site uses to run games and, if enabled, show advertising.
Game data
Computer and same-screen games run in your browser. For online play on the hosted site, Supabase stores the room code, board moves, last connection times, and hashed random seat tokens. Raw seat tokens remain in your browser. A seat token is saved in your browser's session storage so you can return to the same room after refreshing. No email or password is required. Random matchmaking uses a unique nickname. A random player token is saved in local storage to recover your record and active match on later visits from this browser; the database stores only its hash. Your nickname, total wins/losses/draws, and streaks are stored in Supabase. Nicknames and scores may appear publicly on the leaderboard. Do not use your real name or other personal information as your nickname. Rooms survive server restarts and expire after three hours without activity. Expired rooms are deleted by an hourly cleanup. Completed game moves and results are kept for up to 30 days and then deleted by the same cleanup.
Hosting and game services
Render serves the static website and Supabase provides game storage and live updates. These providers process requests to deliver the service.
Community features and computer results
The daily puzzle, play streak, computer-game ranking and the bulletin board use a separate community service hosted on Vercel. When you use them, the browser sends your random player token or a random bulletin ID, the bulletin name you type, any message you post, and results such as finished computer games and daily puzzle answers. Bulletin posts and the names attached to them are public. A bulletin ID and name are also kept in this browser’s local storage, along with your chosen computer difficulty, a local chart of results and a note that you dismissed the cookie notice.
Basic server records
The public website is a static site hosted on Render and served through Cloudflare. Render's documentation says static sites do not emit application logs or HTTP request logs in the Render dashboard. This game does not keep its own database of page visits. Cloudflare may process connection details, such as IP address, request time, and browser information, to deliver the site and protect it. Those records stay with Cloudflare under Cloudflare's own settings. They are not copied into the Supabase game database described above.
Advertising and cookies
The site includes a Google AdSense publisher verification tag and an ads.txt file. At the time of the date above, no ad units are configured, so the pages do not load Google’s ad script and Google advertising cookies are not set by this site. Apart from Google Analytics (see below), the site itself does not use cookies for tracking.
If ads are turned on later, Google and its partners may use cookies or similar technologies to deliver, measure and personalise ads according to their policies and your consent choices where required. Learn more at Google's advertising technologies page and Google Ads Settings. Before ads are shown to visitors in regions that require consent, a certified consent platform will be set up and this notice updated.
Analytics
Since 1 November 2026 this site uses Google Analytics, a web analytics service provided by Google LLC. Google Analytics uses cookies and similar identifiers to collect usage data, such as the pages you view, how long you stay, the referring site, your device and browser type, and an approximate location derived from your IP address. Only the aggregated reports are used, to understand how the site is used. You can opt out with the Google Analytics opt-out browser add-on, or by blocking or deleting cookies in your browser settings.
Sharing and retention
Random matches are restricted to the two assigned players. Legacy private-room links can be used by anyone who receives them until both seats are occupied. Do not put personal information in a room link. The site does not sell game moves or seat tokens. Ranked matches are associated with your nickname profile. Aggregate records and the profile persist beyond individual game retention so your streak history remains available. Clearing browser data removes your local access token, not the stored profile or scores. Without that token, there is no email-based recovery. The optional local Python server uses temporary memory instead of Supabase.
Contact and updates
For privacy questions, use the contact page. The operator will update this notice when the hosting provider, advertising configuration, or data handling changes.
Last updated: 1 November 2026.