Effective Date: August 20, 2026
Last Updated: August 20, 2026
Algorithm LLC ("we," "us," or "our") operates the ExonMesh mobile application (the "App").
This Privacy Policy explains how information is handled when you use ExonMesh.
ExonMesh is designed to operate without a developer-operated messaging server. We do not require user accounts, and text messages or voice notes transmitted through the App are not sent to or stored on our servers.
ExonMesh communicates directly with nearby compatible devices using Bluetooth Low Energy (BLE).
ExonMesh stores certain information locally on your device in order to provide its functionality. This information is not stored on a developer-operated messaging server.
Depending on how you use the App, locally stored information may include:
Callsign / nickname — a display name used to identify you to nearby ExonMesh users.
Peer identifier — a locally generated identifier used to distinguish your device during nearby communication.
Room PIN / channel information — information used to join and communicate within selected rooms or channels.
Text messages — messages sent and received through the App.
Voice notes — audio recordings created when you use the voice-note feature.
Nearby peer information — information required to discover and communicate with nearby ExonMesh devices.
App preferences — settings and configuration choices used by the App.
Local information can generally be removed by clearing the App's storage or uninstalling the App.
ExonMesh is a peer-to-peer communication tool.
When you communicate with nearby users, information required for that communication is transmitted directly from your device to nearby ExonMesh devices using Bluetooth Low Energy (BLE).
This information is not routed through a developer-operated messaging server.
Information transmitted to nearby devices may include:
your callsign or nickname;
your locally generated peer identifier;
text messages you choose to send;
voice notes you choose to record and send;
room or channel information;
connection and message information required to provide nearby communication.
Messages and voice notes are transmitted as part of communication functionality initiated through the App.
Information that you send to another user may remain on that user's device after you delete it from your own device. We do not control information stored on another user's device.
ExonMesh uses Bluetooth and Nearby Devices permissions to discover compatible devices, advertise the presence of your device, establish nearby connections, and exchange information between devices.
Microphone access is used to record voice notes when you actively use the microphone control.
ExonMesh does not use the microphone for advertising or analytics purposes.
Some older versions of Android may require location permission for Bluetooth device discovery.
ExonMesh does not use this permission to determine or track your geographic location for advertising, analytics, maps, or navigation.
The App does not transmit GPS coordinates to a developer-operated server.
For clarity, the current version of ExonMesh:
does not operate a messaging server that receives your chats or voice notes;
does not require user registration, email addresses, or phone numbers;
does not include advertising SDKs;
does not include third-party analytics or tracking SDKs;
does not include Firebase Analytics or similar analytics services;
does not use your information for advertising or marketing profiling;
does not collect your geographic location for tracking purposes;
does not access your contacts for messaging;
does not sell, rent, or trade your personal information.
If these practices change in a future version of ExonMesh, this Privacy Policy will be updated accordingly.
ExonMesh supports encryption for nearby peer-to-peer communication.
The App uses AES-256-GCM for encrypted payloads. When a shared Room PIN or channel is used, compatible devices can derive a matching encryption key locally.
Voice-note payloads are encrypted before transmission.
Text-message encryption can be enabled or disabled in the App. When text encryption is disabled, text-message content may be transmitted without application-level payload encryption.
Some information required for nearby communication, such as device/peer identifiers, callsigns, room/channel information, or message metadata, may not be protected by the same payload encryption.
A shared Room PIN should not be considered equivalent to independently verified public-key identity authentication. Users should choose an uncommon PIN and communicate only with nearby users they trust.
No security mechanism can guarantee protection against every possible attack or unauthorized participant.
We do not operate a cloud messaging service that stores your ExonMesh conversations.
Messages, peer information, settings, and voice-note files may be stored locally on your device as required by App functionality.
You can remove locally stored information by using available deletion features in the App, clearing ExonMesh's application storage through Android settings, or uninstalling the App.
Because ExonMesh communicates directly with other users, information you have already sent may remain on the receiving user's device. We cannot remotely delete information from another user's device.
The current version of ExonMesh does not include advertising networks, third-party analytics providers, social-media tracking SDKs, or third-party crash-reporting services.
Core messaging functionality is designed to operate directly between nearby devices without a developer-operated messaging backend.
Your Android operating system and device manufacturer may independently process information necessary to provide Bluetooth, permissions, backups, and other system services. Their handling of information is governed by their respective privacy policies.
Text messages and voice notes transmitted through ExonMesh are created by users and exchanged directly between nearby devices.
Because we do not operate the messaging server, we do not receive, host, monitor, review, or moderate the content of peer-to-peer conversations.
Users are responsible for the content they transmit through ExonMesh and should not use the App to transmit unlawful, abusive, threatening, obscene, or otherwise prohibited content.
If you receive unwanted communication, stop communicating with that participant and leave or change the applicable room/channel.
ExonMesh is not directed to children under the age of 13 or the applicable minimum age in the user's jurisdiction.
We do not knowingly operate a server that collects personal information from children through ExonMesh.
Parents and guardians should supervise minors when using communication features.
You can control information stored and used by ExonMesh by:
choosing or changing your callsign;
choosing a Room PIN or channel;
controlling available encryption settings;
controlling microphone and Bluetooth permissions through Android settings;
deleting locally stored information where the App provides that functionality;
clearing the App's storage; or
uninstalling ExonMesh.
Revoking Bluetooth or microphone permissions may prevent some App features from functioning.
ExonMesh relies on short-range Bluetooth communication.
Connection availability and reliability may vary depending on distance, physical obstacles, interference, Android system restrictions, battery conditions, and device hardware.
ExonMesh is not a substitute for emergency communication services, a cellular telephone, or a licensed two-way radio and should not be relied upon for emergency, medical, life-safety, or other critical communications.
We may update this Privacy Policy when ExonMesh features or privacy practices change.
When we make changes, we will update the "Last Updated" date shown at the top of this page.
If you have questions or concerns about this Privacy Policy, contact:
Algorithm LLC
Email: support_algorithm@proton.me