Privacy Policy
BitBoard — Last updated: November 2026
Summary
BitBoard does not collect or share any data with the developer or anyone else. The app has no internet permission, so it cannot send anything over the internet. Your games, boards, photos, settings, and what the computer opponent has learned stay on your device, and in the standard Android system backup if you use it.
If you choose to play with other phones over Bluetooth, the game goes directly to those nearby phones and nowhere else. The section on playing over Bluetooth below says exactly what is sent and what each phone keeps.
Data Collection
BitBoard collects no data whatsoever. No personal information, no analytics, no telemetry, no crash reports, no advertising identifiers, no location data. There is no account system, no server, and no cloud component operated by the developer. Nothing sent between phones over Bluetooth passes through the developer.
Data Storage
The app keeps the following in its private storage on your device: your games in progress and your game history, your Bit Board boards and the photos you chose for them, your appearance and display settings, what the computer opponent has learned from your games against it, and a random number made on your device that is used only to help shuffle dice rolls. The app never sends the computer’s learning anywhere, and “Reset computer’s memory” in a game’s menu deletes it.
If you play over Bluetooth, it also keeps the name you entered, so it is filled in next time, and a random player code made on your device (see below).
Deleting a board removes it at once. Photos that only that board used are removed the next time the board list is opened. Uninstalling the app deletes all of this local data.
Playing With Other Phones Over Bluetooth
BitBoard can link phones in the same room over Bluetooth: two phones for a game of chess, checkers, go or backgammon, and up to eight phones sharing one Bit Board. This happens only when you choose Host or Join.
What is sent. Only to the phones taking part, directly over Bluetooth: the moves of the game, or the board and every change to it, including the photos and background the board uses, each dice roll with the name of who rolled, the name you enter, and a random player code made on your phone, which lets the host’s phone tell players apart and give a returning player their place back. The code is made at random and is not linked to your identity, your phone’s hardware, or any account.
Who can connect. Only phones you have paired yourself in Bluetooth settings, where both phones show a code to confirm. The app never scans for nearby devices and never makes your phone discoverable. The link is the secure, encrypted kind of Bluetooth connection.
What each phone keeps. The phone that hosts a Bit Board keeps, with that board, the names and player codes of the players who joined and whether each may edit, so they keep their place and their rights next time. A phone that joins a board keeps nothing once the board is closed, and holds its photos only while the board is open, unless the host turns on “Players can save a copy” and that player chooses to save one: then the board and its photos are kept on that player’s phone like any board of their own. After a game of chess, checkers, go or backgammon, each phone keeps the game in its own history with the side that phone played.
Once something is on another person’s phone, it is in their keeping, under their own phone’s settings and backup.
Photos You Choose
Bit Board lets you pick a photo from your device to use as a token or as a board background. You choose it through the Android system photo picker, or the system file picker on older versions of Android, so BitBoard never has access to your photo library, only to the single image you pick.
The app keeps its own copy of that image, reduced in size if it is large, and saved without the original file’s metadata, such as location. The app never uploads it anywhere. If you host a Bit Board over Bluetooth, the board’s photos are sent to the phones that join it, as described above.
Backups
Your games, game history, boards, the photos you chose, your settings, your Bluetooth name and player code, the list of players kept with a hosted board, and what the computer opponent has learned may be included in the standard Android system backup and device-to-device transfer, so they can be restored on a new phone. The dice number is left out. This backup is operated by Android and your Google account, not by the developer, and is covered by Google’s own privacy policy.
Security
There is no server, account, or database to breach: nothing is collected, so there is nothing held anywhere for an attacker to reach. On your device, your data is written to the app’s private storage, which the Android application sandbox keeps readable only by BitBoard itself. Between phones, BitBoard uses only encrypted Bluetooth connections with phones you have paired, and the host’s phone checks every request before acting on it.
Network Access and Permissions
BitBoard does not request the internet permission, so it cannot make network requests of any kind. It requests no location, camera, microphone, contacts, or storage permissions.
For playing over Bluetooth, it asks for the Nearby devices permission (on Android 12 and newer) the first time you choose Host or Join, and uses it only to list the phones you have paired and to connect to the one you pick. On Android 11 and older, the equivalent Bluetooth permissions are granted when the app is installed. It does not ask for the permissions that scan for devices or make the phone discoverable. Its only other permission entry is a private signature permission, added automatically by an AndroidX library, which keeps the app’s own internal components from being triggered by other apps. It grants no access to your data or to any device feature.
There are no ads, no in-app purchases, and no subscriptions.
Contact
Questions about this policy or your data can be sent to N8Codes at n8codesandcreates@gmail.com.
Changes
If this policy changes, the updated version will be posted at this URL with a new date.