Historical gameplay records and their limits

Why earlier figures were withdrawn, what historical events meant, and how they differ from current room state and optional analytics.

Status as of September 30, 2026

Separate server-side game-start and game-completion analysis events are no longer collected by the current implementation. This page explains the earlier records; it is not a report of current gameplay totals. The original URL is retained for continuity, not as a claim that 1,500 games have been verified.

What the historical events meant

A game_started record described a round being created and words assigned. A game_completed record described a voting result. In Deep Cover, a voting result could be intermediate, with no final winner. Room IDs, round numbers, player counts and modes described rounds, not unique people or independent groups.

Why the figures were withdrawn

Earlier totals and averages are withdrawn because this page does not provide reproducible source records, dates, filters and calculations. They should not be used as evidence of popularity, typical duration or winning strategies. No replacement numerical estimate is published here.

How a future analysis would need to work

Match starts and results by room and round within a stated collection window. Explain missing results, duplicate records, internal tests and interrupted games. A duration from round start to a vote excludes setup and may exclude later Deep Cover votes. Unmatched start and completion totals cannot establish abandonment, and repeated rounds cannot establish unique visitors.

What the game still needs to store

Operational room and round state supports play and reconnecting. That state is distinct from the discontinued analysis events. Older analysis records may remain subject to retention and backups; stopping collection is not proof that historical records have been deleted.

Optional browser analytics today

With analytics permission, the browser can send a player-session event containing return-visit information and load Google Analytics. Rejecting optional analytics prevents those browser requests. Session events, room counts and weekly visitors are different measures and should not be added together or described as unique monthly people.

See the privacy policy for current data use and controls.