Privacy Policy

Effective October 27, 2026 · Version 2026-10-27

This policy describes the data practices of the current Bojiboji application owned by Olamide Olatayo Bello. It distinguishes the game's own behavior from services a hosting operator may configure separately.

What the game processes

• Player and room data: the nickname and avatar you choose, a room code, an unguessable session token, readiness, movement and throwing inputs, ball possession, match results, hits, and throws.
• Optional hiding profiles: a name, description, manually entered location label, field coordinates, and an optional picture. Picture files selected in your browser are resized and re-encoded before the resulting image is sent when you save online.
• Browser saves: your nickname, avatar, language choice, arena theme, reduced-effects preference, personal games/wins/hits, and the latest five match summaries. These use local storage on your device.
• Connection information: the hosting infrastructure receives your IP address and ordinary HTTP connection information to deliver the service. Reverse-proxy and server diagnostics may record connection, request, and error information, depending on the hosting configuration.

Why data is used

Room data synchronizes gameplay, authenticates your room session, applies the rules, and displays the lobby and scoreboard. Optional profile content describes your hiding spot to other players. Browser saves remember your settings and personal results. The application does not request GPS access, payment-card details, an email account, or a password.

What other players see

Room members receive nicknames, avatars, readiness, player positions, gameplay state, match statistics, and saved hiding-profile descriptions, pictures, labels, and field positions. A room code is an invitation, not a guarantee of confidentiality. Do not share sensitive information. Other participants can retain screenshots or copies that the operator cannot retrieve from their devices.

Your session token is used for room access and is not included in invite links or the shared player roster. The event-stream URL contains this temporary credential. The supplied deployment snippet disables access logging for that endpoint; other hosting configurations may log request URLs. Protect the token as you would a temporary credential. A person with access to your device or an insecure connection may be able to access your session.

Storage and retention

The application keeps rooms and hiding profiles in server memory, without a game database or an application upload directory. Rooms disappear when the server restarts or the last member leaves. Sessions without activity expire after about 45 seconds. Deleting your hiding profile, leaving the room, or session expiry removes your shared profile from the current room state. Basic match information, including a departed player's nickname, can remain until the next match or room deletion.

Browser saves remain until you clear them or your browser removes site data. The Clear saved game data control removes the game's stored preferences and personal statistics from this browser, including the saved language choice (the default then returns to Nigerian Pidgin). Future play or preference changes can create new saves. Server restart does not erase infrastructure logs; their retention is managed separately by the hosting operator.

Sharing and third-party services

The current application includes no advertising network, marketing tracker, third-party analytics script, or sale-of-data feature. It sends shared game data to room participants and relies on the hosting provider and network infrastructure to deliver the game. If you use your device's share function, the destination you choose receives the invitation link. No external font or image service is needed for the included game artwork.

The hosting operator may need to access operational data to maintain the service, investigate abuse, or respond to a valid legal requirement. Any additional analytics or integrations introduced by a hosting operator should be disclosed before use; they are not part of the application described here.

Your controls

• Use a nickname and a general place label; skip the optional picture.
• Use Delete hiding profile to remove your shared description, location label, and image. Removing a selected picture alone changes your draft; save it to update an existing online profile.
• Use Leave room to end your room membership and remove your shared profile.
• Use Clear saved game data below or your browser's site-data settings to erase local preferences and personal statistics. This does not end an active online session or delete infrastructure logs.

Clear saved game data

Young players

Parents and guardians should supervise young players, help them choose nicknames, and review any picture or location label before it is shared. Do not upload a child's private address, school details, or other sensitive identifying information. This build does not collect dates of birth or offer a parental-consent workflow.

Security, requests, and updates

Use the game over HTTPS on a trusted installation. No online system can guarantee absolute security. For a privacy question or request concerning data handled by this installation, ask the person who shared your room invite for the operator's contact information. Include the room code and nickname if relevant; never provide your session token. Requests about infrastructure logs must be handled by that hosting operator.

Material changes will be identified with a revised effective date and any additional notice required by applicable law. This page does not claim compliance with every jurisdiction's privacy requirements.