Technical documentation

Overview

The application runs as a modern web app. Real-time game state and persistence are provided by a hosted backend service; optional in-app purchases are processed by Stripe (payment UI may include cards and wallet methods such as Apple Pay or Google Pay where available). The player-facing interface is in Ukrainian; legal pages are Ukrainian; this overview is English-only by design.

Identity & sessions

• There are no user accounts or passwords.
• Your browser keeps a random anonymous identifier so the service can recognise your seat in a room across page loads. Clearing site data creates a new identity.
• Creating or joining a room requires confirming that you are at least 18 years old and accept the Terms and Privacy Policy (checkbox on the relevant screens).

Main pages

• Landing — introduction and entry into the game.
• Play — create a room or join by code; may list public rooms you can pick from; may redirect if you are already seated elsewhere.
• Room — lobby, optional chat, and the game board for a specific room code.
• Terms of Use and Privacy Policy — legal text.
• This technical overview.

Game flow

• One player per round acts as the judge (“Card Bro”): reads the black prompt; others answer with white cards (or optional custom text where unlocked). The judge picks a winner; scores update; another round can follow after a short on-screen pause.
• New players can join only while the table is still in the lobby; once the match has started, joining is blocked.
• During judging, non-judge players typically see all answers as anonymous variants; your own submission may be highlighted for you.
• The match can end when prompts or playable cards run out under the rules; the UI then shows final standings, including ties where applicable.
• If someone leaves mid-game, remaining players may see a notice; under some conditions the game returns to the lobby. Behaviour depends on how many people remain and the current phase.

Optional paid features

The base game does not require payment. Optional extras may appear after enough rounds have been played:

• Custom answer — send your own text instead of a white card from your hand (subject to unlock and cooldown rules shown in the room). One-time paid use may be offered when free uses are not available.
• Refresh hand — replace your whole white hand with new cards from the deck when allowed; one free refresh per match may be available after a minimum number of rounds, then paid refresh if offered. Not possible when the deck cannot supply new cards or after you have already submitted for the round, as explained in the UI.

Data handling (summary)

The service processes only what is needed to run a session: display names you choose, game state for the room, optional chat content for that room, and technical data required for reliability and optional payments. Payment card numbers are not stored by this application; they are handled by the payment provider’s flow. For detail, read the Privacy Policy.

Rooms & retention

• The host may close a room; guests may then see that the room is no longer available.
• If everyone leaves, the room may be removed.
• Idle rooms and finished sessions are cleaned up automatically after reasonable delays so storage does not grow indefinitely. Exact timings may evolve with product updates.

Payments

• Optional purchases are completed inside the site via the payment provider’s embedded flow.
• Successful payment unlocks the corresponding in-game permission for that session, subject to the rules shown before you pay.
• For billing disputes, refunds, and card data practices, see the Terms of Use and Privacy Policy.

Changelog

A product changelog may be published with releases. It describes user-visible behaviour and operator-facing notes, not internal architecture.