Updated September 23, 2026.
Ommesh is the mobile version of Meshnet, a companion for MeshCore radios maintained by cm4ker and the Meshnet project. This policy describes the data handled by the app. No Ommesh account is required.
The app stores conversations, message drafts, radio contacts (not your phone's address book), public node identifiers, routes, positions supplied by radios, telemetry history, connection addresses and preferences locally. Map and elevation tiles are cached for reuse offline. Message history is separate for each radio.
When you choose to remember a node password, mobile builds use the platform's secure storage; desktop builds use the system credential store. Browser builds use the browser's local storage. Conversation history and cached map data are not separately encrypted by the app. The Android app excludes its private data from Android cloud backup and device-transfer backup.
Connecting sends companion-protocol commands to the radio you select over Bluetooth or Wi-Fi/TCP. Messages, channel settings, node names, passwords for remote administration and positions you set can be transmitted to that radio to perform the actions you request. The radio may forward messages, advertisements, positions and telemetry to other radios according to its settings. Anyone with access to a channel may be able to read that channel's messages.
Wi-Fi/TCP connections to companion radios do not use TLS. Use a network you trust. Radio encryption depends on the firmware, message type and channel keys; this app does not promise that all radio traffic is encrypted or that it can erase data received by other people.
Opening the map or a terrain profile can request images from OpenStreetMap tile services and the public elevation-tiles-prod dataset hosted on Amazon Web Services. Those services receive your IP address, request time, client information and the coordinates of the requested map tiles. A viewed area may reveal an area of interest or a radio's location. These HTTPS requests do not include your conversations, node passwords or radio contact list. Provider logs and retention are governed by the providers' policies.
You can change permissions in your device settings. Denying Bluetooth access prevents Bluetooth connections; demo mode does not require a radio.
The app contains no advertising SDK, analytics SDK or automatic crash-reporting service. The project does not operate an account or message-storage server. Google Play may process installation and diagnostic information according to Google's settings and policies. Desktop builds can also contact GitHub for update checks and downloads; these requests expose the IP address and normal request information to GitHub. Android updates are distributed by the store.
Local history remains until you delete it or clear the app's storage. In the app, use Radio → Reboot, reset, erase → Delete the history on this device to remove the selected radio's conversation history. Saved node passwords can be forgotten in the node's sign-in controls. On Android, Settings → Apps → Ommesh → Storage → Clear storage removes the app's local history, settings, cached tiles and remembered passwords. Uninstalling also removes its app data.
Deleting local history does not delete data stored on a radio, copies held by recipients, or logs retained by map providers. Manage the radio's data separately. No app account needs to be deleted because the app does not create one.
For privacy questions, email support@it-adapt.ru. You can also reach the maintainer through the Meshnet project support page. GitHub issues are public: do not post passwords, private messages or precise private locations there. The date above changes when this policy is updated.