Privacy Policy

Summary

This policy describes data handling by the MeshGames apps listed below. The apps send nothing to DataXad automatically: they require no account, include no advertising, analytics, or tracking SDK, use no developer-operated gameplay server, and do not request Internet access. Visiting this web page is separate from using the apps and may create ordinary security and delivery logs at the website's hosting provider.

When you choose nearby play, the app sends only the information needed for that session directly to nearby players' devices over Bluetooth. It is not sent to DataXad or any online service. DataXad receives information only if you choose to send a feedback or player-report email from your own email app.

Google Play's Data safety form defines some optional off-device transfers as collection even when the developer never receives the data. Under that definition, the nearby display name, pseudonymous profile hash, voice, and text chat described below are collected for app functionality when you choose to use those features.

Covered Apps

This policy applies to the MeshGames Hub and all 13 standalone games in this table. The package anchors provide stable per-app links.

Data DataXad Receives

DataXad receives no app data automatically.

• No MeshGames account or sign-in is required or offered.
• No advertising, third-party analytics, or tracking SDK is included.
• No gameplay, telemetry, or diagnostics data is sent automatically to DataXad or an online service.
• The apps do not request the Android INTERNET permission.

The one exception is email you send yourself. If you use Send Feedback or Report player, the app prepares a draft in your own email app. If you send it, DataXad receives your email address, your message, and anything you chose to leave in the draft.

Data Stored On Your Device

The following can be saved locally. DataXad does not receive it automatically; the nearby-play section explains the limited fields sent directly to participating players.

• A display profile: the name you type and the profile colour and small icon you choose from the built-in set. There is no photo and no account.
• Local game saves, settings, game statistics, history, troubleshooting logs, and rating-prompt state where the app uses them.
• Your block list, if you block a nearby player: a non-reversible profile hash and display name, never message or voice content.
• Nearby opponent and match history, where a game uses it: the other player's display name and pseudonymous profile hash can remain on your device after the session.

You can remove local profile and game data with the app's local profile reset where that control is available. Clearing the app's storage or uninstalling it removes all locally stored app data, subject to your device and operating-system behavior. There is no DataXad account or cloud record to delete, and DataXad cannot restore local data after removal. Resetting or removing data on your device does not erase a display name or profile hash already retained in another player's local opponent or match history.

Optional Feedback You Choose To Send

If you tap Send Feedback or Report player, the app opens a pre-filled draft in your own email app. You decide whether to send it, and the whole draft is visible and editable first. Basic build and device information may be included. Some app feedback entry points also prefill locally stored game statistics or a diagnostics summary. You can edit or remove any draft content before sending. Nothing is transmitted automatically, and you choose whether to send the draft through your own email app. Diagnostics contain no voice or chat content.

If you send the email, DataXad uses it only to reply and improve the app. We do not sell it, use it for advertising, or share it outside DataXad except with the mail provider that carries it. We normally retain support email for no more than 24 months. You can ask us to delete it sooner at the contact address below.

Local Multiplayer Over Bluetooth

Each standalone MeshGames game offers optional nearby Bluetooth voice and text chat. Synchronized nearby gameplay is available only where the game supports it. The Hub provides nearby features inside the supported games it includes. Bluetooth connects participating devices directly; no MeshGames account, internet connection, cloud matchmaking, or DataXad gameplay server is involved.

What nearby play sends

During a nearby session, participating devices exchange only what the session needs:

• Your chosen display name, profile colour, and built-in icon, plus a stable pseudonymous, non-reversible local-profile hash and suffix used to distinguish players with the same name. No photo, email address, phone number, account, or device identifier is sent.
• App identity, game identity, protocol version, and whether voice and text chat are available, so compatible devices can agree on supported features.
• Where a game supports a synchronized nearby match, participating devices exchange the game state, actions, timing, and result needed to run that match. In Poker, private cards are sent only to the seat that owns them. In Sudoku races, devices exchange the puzzle seed and difficulty, player progress, mistakes, elapsed time, and the settled result; they never exchange grid entries or pencil notes.
• Text-chat messages you choose to send.
• Live voice only while you hold the push-to-talk control.

This information travels only between participating devices, is used for the nearby session, and is never sent to DataXad, an analytics provider, or a server.

For Google Play's Data safety form, the optional off-device nickname, profile hash, voice, and chat transfers are declared as collection for app functionality. They are not declared as sharing because you initiate the transfer to nearby participants. Voice is processed ephemerally. Text chat remains in session memory, and a display name and profile hash can remain in another participant's local opponent or match history. The app does not provide or promise app-layer end-to-end encryption for nearby transfers.

Push-to-talk voice

The microphone is active only while you hold the talk control. Live audio is compressed into short packets and sent over the existing nearby connection. Backgammon and the Hub use a selected-player voice surface; the other standalone games use session voice. The app creates no audio file, does not save voice, and does not add it to diagnostics. People who hear you can still listen, repeat, or record what you say using something else. Voice is not sent to DataXad or an online service.

Text chat

Text chat travels only over the current nearby connection. The app keeps up to the last 50 messages in memory for that session, stores none on disk, and sends none to DataXad or an online service. Players who join later do not receive earlier messages. Other players can still read, repeat, or screenshot what you type.

Muting, blocking, and reporting

You can mute a player for the session or block them persistently on your device. These controls apply only on your device: they stop that player's voice and messages from being presented to you. The local block list stores only a profile hash and display name. Reporting opens a draft in your own email app; nothing is sent unless you choose to send it.

Device Permissions

• Bluetooth — scan, connect, and advertise permissions support nearby discovery and the direct connection. On Android 12 and later, scanning is declared with neverForLocation.
• Location — on Android 11 and earlier, ACCESS_FINE_LOCATION is an operating-system requirement for Bluetooth discovery. The apps do not read, store, or transmit GPS or physical location.
• Microphone — used only while you hold the push-to-talk control.
• Vibrate — used only for gameplay and communication haptics; it does not collect data.

Sharing And Children's Privacy

We do not share app data with advertisers, analytics providers, or remote services. Information you deliberately share during nearby play goes only to participating nearby devices. Feedback or report email you send is handled as described above.

The apps are not directed at children under 13, and DataXad does not automatically receive personal information from app use. Nearby players receive the display identity, voice, and text chat you deliberately send. Nearby voice and text chat connect players who are physically near one another and are not remotely moderated by DataXad. A parent or guardian should decide whether those features are appropriate for a younger player. If you believe a child sent us personal information by email, contact us and we will delete it.

Data Deletion

Because DataXad receives no app data on a gameplay server, there is no app account or cloud gameplay record for us to delete. Use the local profile reset where available, clear app storage, or uninstall the app to remove local data from that device. This cannot remotely erase a display name or profile hash retained on another player's device. If you emailed feedback or a report and want that message deleted, ask us at the address below.

Contact

For privacy questions, support, or deletion of feedback or a report email you sent, contact meshgames+feedback@dataxad.com.

Changes To This Policy

We may update this policy when a covered app, permission, or data practice changes. Material changes appear here with an updated effective date.

September 14, 2026 update: This shared policy now names the MeshGames Hub and all 13 standalone packages, and describes their common local-data, voice, chat, device-local moderation, permissions, and user-initiated support email practices, plus game-state exchange where synchronized nearby gameplay is supported.

September 14, 2026 clarification: This policy distinguishes data received by DataXad from optional off-device nearby transfers that Google Play's Data safety form classifies as collection, and explains recipient-side retention, device-local deletion, and the absence of an end-to-end-encryption guarantee.

September 15, 2026 correction: This policy now reflects that some app feedback entry points prefill local statistics or diagnostics in the visible, editable email draft. Nothing is transmitted automatically, and the user chooses whether to send it.