MeshGames · DataXad
Privacy Policy
Effective date: August 9, 2026
Summary
DataXad is the developer and publisher of the MeshGames apps covered below. Covered apps operate without accounts, advertising, third-party analytics or tracking SDKs, or a developer-operated gameplay backend unless the table lists an explicit app-specific exception. DataXad does not receive gameplay information from the apps automatically.
Covered Apps
This policy applies to every app in this table. A future MeshGames title can be added by adding a row. If an app handles data differently, that difference must be stated in its exception cell before the behavior is released.
| App | Package ID | App-specific privacy exception |
|---|---|---|
| MeshGames Backgammon | com.dataxad.meshgames.backgammon | None |
| MeshGames Checkers | com.dataxad.meshgames.checkers | None |
| MeshGames Poker - Offline | com.dataxad.meshgames.poker | None |
| MeshGames Sudoku | com.dataxad.meshgames.sudoku | Current Android v1.0.5 declares Bluetooth scan/connect/advertise, legacy Bluetooth/location permissions on Android 11 and earlier, and RECORD_AUDIO for nearby race, chat, and voice paths; it does not declare INTERNET. Nearby data remains device-to-device. |
Data We Collect
The covered apps do not automatically collect data for DataXad.
- No MeshGames account or sign-in is required or offered.
- No advertising, third-party analytics, or tracking SDKs are included.
- No automatic gameplay upload or developer-operated gameplay backend is used.
- Local operational telemetry and diagnostics used by the current candidates remain on the device and are not uploaded automatically.
-
The current Android MeshGames Sudoku candidate, versionCode 5
and versionName 1.0.5, does not request the
INTERNETpermission. Its packaged manifest does request Bluetooth scan, connect, and advertise permissions; legacy Bluetooth andACCESS_FINE_LOCATIONpermissions on Android 11 and earlier; andRECORD_AUDIOfor the current nearby race, chat, and voice paths. This is the app-specific exception shown above.
Data Stored On Your Device
App settings, game saves, statistics, local operational telemetry, and rating-prompt state stay on your device. For MeshGames Sudoku, puzzle definitions, current puzzle state and progress, settings, and local statistics remain on the device. A covered app may also store a local display profile, including a chosen display name, a built-in avatar or profile picture, and a profile color. MeshGames Poker stores per-game local-table history and a device-local ranking keyed to that local profile. This is not a global or online leaderboard. The apps do not upload this local data to DataXad.
Where the app offers a local profile reset, using it removes that profile and its associated local history and ranking. Clearing the app's storage or uninstalling the app removes all locally stored app data, subject to the normal behavior of your device and operating system. There is no DataXad account or cloud record to delete. Because this data is not held on a DataXad server, DataXad cannot restore it after removal.
Direct Nearby Bluetooth Play
When you choose nearby Bluetooth play, the app connects directly to the selected nearby peer or peers. Your chosen display identity—including your display name, built-in avatar or profile picture, and profile color—and the current game state are transmitted directly to participating devices for the current nearby session. For MeshGames Poker, private hole cards are sent only to the seat that owns them; other seats receive face-down or redacted card state. This information is not uploaded to DataXad and does not pass through a DataXad gameplay server.
Bluetooth permissions are used to discover nearby devices, make and maintain the direct connection, and allow a device to advertise a nearby game where supported. You control whether to grant these permissions and whether to start nearby play.
For MeshGames Sudoku, the current Android candidate includes a nearby two-player race path. If you choose it, the display name, puzzle seed and difficulty, live solving progress, and finish result are sent over the nearby connection to the participating device. Text chat is kept in memory for the current session and travels over that connection only. Push-to-talk voice uses the microphone only while you hold the control; audio is not recorded, saved, or uploaded.
Android Bluetooth Permissions
On Android 11 and earlier, Android may require
ACCESS_FINE_LOCATION
for Bluetooth discovery. MeshGames does not read, store, or transmit
your GPS or physical location.
On Android 12 and later, nearby play may use Bluetooth scan,
connect, and advertise permissions. Bluetooth scanning is declared
with the
neverForLocation
posture: scanning is for nearby-device discovery, not to derive physical
location.
MeshGames Sudoku is the current covered-app exception to a
no-Bluetooth/location-permission posture: its Android v1.0.5
candidate declares the Bluetooth permissions above and
ACCESS_FINE_LOCATION with a maximum SDK of 30. It does not use that permission to read
or transmit GPS location.
Gameplay Haptics
Where a covered app offers haptic feedback, vibration permission is used only to provide gameplay haptics, such as tactile feedback for an interaction or game event. It is not a data-collection permission.
Optional Feedback
Choosing Send Feedback opens a draft in your own email application. Nothing is sent until you review the draft and choose to send it through your email account. The default draft may include the app version and basic device information needed to identify the build and device type. It excludes gameplay statistics and diagnostic logs by default. You can edit or delete any draft content before sending.
DataXad receives only the email and information you actively choose to send. If you sent feedback and want that email deleted, contact us at the address below.
Data Sharing And Children's Privacy
DataXad does not share app data with third parties because the covered apps do not upload app data to DataXad. The apps do not knowingly collect personal information from anyone, including children. Nearby participants directly receive the display identity and game state required for a session only when nearby play is chosen.
Contact
For privacy questions, support, or deletion requests concerning feedback email you sent, contact meshgames+feedback@dataxad.com.
Changes To This Policy
DataXad may update this policy when a covered app, permission, or data practice changes. We will update the effective date on this page and add any necessary app-specific exception before the changed behavior is released.
Related: MeshGames Terms of Service