Chester is a card game with local-network and optional hosted multiplayer modes. It has no user accounts, advertising, analytics, in-app purchases or real-money wagering. This policy explains the limited information Chester handles, where it goes and how long it remains.
The short version. Local Wi-Fi play sends room data only between devices on the same network. Optional hosted play processes room data through Cloudflare Workers and D1. Chester also remembers a few preferences and reconnection details on your device.
1. Who we are
Chester is published by ClickBit Digital, Dhaka, Bangladesh. Our website is clickbitdigital.com. Contact details appear at the end of this policy.
2. What Chester does not do
- Chester does not require an account, sign-in, email address or phone number.
- The current app contains no advertising, advertising SDK, analytics, crash-reporting or attribution SDK.
- There are no purchases, paid currency, prizes or real-money wagering.
- The app does not request access to contacts, photos, files, camera, microphone or location.
- The Android app declares one permission:
android.permission.INTERNET. This is needed for local Wi-Fi and optional hosted network play; the same Android permission covers both local and internet traffic.
3. Information stored on your device
Chester uses app storage to keep preferences and help reconnect to a room. In a browser these values use local storage. In the Android app, language and nickname are also kept in Capacitor Preferences, the app's native preference store.
| Stored item | Purpose | Retention |
|---|---|---|
| Sound and music settings | Remember your audio choices | Until changed, browser site data is cleared, or the app is uninstalled/app data is cleared |
| Language choice | Open Chester in English or Bangla | Until changed or removed with browser/app data; the Android native preference can survive clearing only the WebView's browsing data |
| Nickname | Prefill the player-name field | Until changed or removed with browser/app data; on Android it is also held in the native preference store |
| Last Wi-Fi host address | Avoid retyping a local host address | Until changed, removed, browser site data is cleared, or the app is uninstalled/app data is cleared |
| Current room code and random room-access token | Reconnect after a reload or app restart | Removed when you leave, when reconnection finds the room invalid or expired, or when browser/app data is cleared |
A room-access token is a random credential for one room. Do not share it. It is not an advertising identifier, account ID or permanent device ID.
4. Nicknames and local room discovery
You choose the nickname shown to other people in the room. It does not have to be your real name. Chester remembers that nickname on your device as described above.
When an Android device hosts a local Wi-Fi room, it repeatedly broadcasts a discovery message across that local network. The message contains the host's nickname and six-digit room code, plus the current player count, seat count, whether the match has started and the host port. Any device on the same network may be able to receive this broadcast even if it never joins the room. The broadcast stops when hosting or discovery stops.
5. Local Wi-Fi and LAN games
In local mode, one phone or a computer running the included LAN server acts as the host. Other players communicate directly with that host over the same local network. ClickBit Digital does not receive the room traffic in this mode.
The host processes the room code, seat list, player nicknames, game state and actions, cards, and a random access token for each player. Other players receive the public room state needed to play, including participant nicknames. Network devices also process local IP addresses as needed to route traffic.
Local room API traffic uses plain HTTP, and discovery uses UDP broadcast. It is not encrypted on the local network. Use Chester only on a network you trust. A short room code is not a password; anyone on that network who discovers or knows an open room code may try to join.
The host keeps room state in memory. A room is deleted when the last active player leaves or the host stops. It becomes invalid 24 hours after creation; an expired in-memory record is removed on the next room-list or room-access cleanup, or when the host stops.
6. Optional hosted multiplayer
If you use Chester through a hosted public web version, room requests are handled by Cloudflare Workers and room state is stored in Cloudflare D1 instead of only on a nearby player's device. The stored room state includes the room code, seat configuration, nicknames, game state and actions, cards, and random room-access tokens. Chester does not ask for an account or contact details.
A hosted room expires no later than 24 hours after creation and is deleted earlier when the last active player leaves. Expired rows are deleted when the service processes room access or its room-list cleanup. The Chester application code does not save IP addresses in the D1 room record.
Cloudflare necessarily processes request information such as IP address, request headers and timestamps to deliver, secure and operate the service. Its handling and infrastructure retention are governed by Cloudflare's privacy policy. Browser-to-Cloudflare traffic on the public hosted URL uses HTTPS.
7. Who receives information
- Local room host and participants: receive the room information needed for local play; the host nickname and room code are also broadcast for discovery as described in section 4.
- Cloudflare: processes hosted-mode room data and network request information as our infrastructure provider.
ClickBit Digital does not sell Chester information and does not use it for advertising or behavioral profiling.
8. Children
Chester is a general-audience card game and is not directed to children under 13. It has no chat, purchases or advertising. A parent or guardian should supervise a child's network play and should use a nickname that does not reveal the child's real identity.
9. Purchases, prizes and wagering
Chester is played only for in-game points. It has no in-app purchases, purchasable currency, cash-out, prizes, betting or real-money element.
10. Your choices and requests
- Change your language, nickname, sound settings or host address in the app where available.
- Leave a room to remove your active seat and invalidate that room token. If the leave request cannot reach the host, the room still expires within 24 hours.
- Clear the browser's site data, or clear/uninstall the Android app, to remove Chester's local data from that device. Android native preferences are removed when app data is cleared or the app is uninstalled.
Hosted rooms are short-lived and are not tied to a verified account, so we may not be able to identify a particular record as yours. You may still contact us with a privacy question or request using the details below.
11. Security
Chester limits room lifetime, uses random per-player room tokens, and does not include advertising or analytics SDKs. No system is risk-free. Local LAN traffic is unencrypted, and anyone with access to a room token could act as that player until the room closes or the token is invalidated.
12. Changes to this policy
We will update this policy if Chester's data handling changes. The date at the top identifies the current version. Material changes will be reflected here before or when the relevant feature is released.
13. Contact
ClickBit Digital
Dhaka, Bangladesh
clickbitdigital@gmail.com
clickbitdigital.com/contact.html