🛡️ Privacy at a Glance
- No accounts, no registration, no phone number required
- All messages are end-to-end encrypted (ChaCha20-Poly1305)
- We do NOT collect, store, or transmit your personal data to any server
- No analytics, no tracking, no advertisements
- All data stays on YOUR device only
- Open mesh protocol — no central server dependency
Introduction
FireMesh ("တော်လှန်ဆီမီး", "the App", "we", "our") is an offline-first hybrid messaging
application developed by Wolf Systems (package: com.wolfsystems.firemesh).
The App enables peer-to-peer communication through Bluetooth Low Energy (BLE), LoRa Radio,
Wi-Fi Direct, and optional Internet relay — all without requiring centralized servers or user accounts.
This Privacy Policy explains how the App handles data. In short: your data stays on your device, and we have no ability to access it.
Information We Do NOT Collect
FireMesh is designed with a zero-knowledge architecture. We do not collect, process, or have access to:
- Your name, email address, phone number, or any personal identifiers
- The content of your messages (encrypted end-to-end)
- Your contacts or address book
- Your browsing history or app usage patterns
- Device identifiers (IMEI, advertising ID, etc.)
- Your precise or approximate location data
- Photos, media files, or documents on your device
🔒 No Server = No Data Collection. FireMesh operates primarily through direct device-to-device communication. There is no central server that processes or stores your messages.
Data Stored on Your Device
The following data is created and stored locally on your device only:
| Data Type | Purpose | Stored Where |
|---|---|---|
| Cryptographic Identity (Ed25519 keypair) | Authenticate you to other peers without passwords | Device Only |
| Message History | Display your conversations | Device Only |
| Peer Contact List | Remember discovered mesh peers | Device Only |
| Encryption Keys (per-peer shared secrets) | End-to-end encrypted messaging | Device Only |
| App Preferences (theme, settings) | User experience customization | Device Only |
This data is stored in a local SQLite database and shared preferences on your device. It is never transmitted to us or any third party.
Permissions & Why We Need Them
FireMesh requests the following Android permissions, each essential for its core mesh networking functionality:
| Permission | Why It's Needed | Data Sent to Server? |
|---|---|---|
| Bluetooth / BLE | Scan for and connect to nearby FireMesh devices for peer-to-peer messaging | No |
| Location | Required by Android to perform BLE scanning (we do NOT track your location) | No |
| Wi-Fi State | Wi-Fi Direct peer-to-peer connections (no internet required) | No |
| Internet | Optional Nostr relay fallback transport (user-initiated only) | Encrypted Only |
| Foreground Service | Keep mesh networking active in the background so messages can be relayed | No |
| Boot Completed | Restart mesh service after device reboot | No |
📍 About Location Permission: Android requires Location permission for Bluetooth Low Energy scanning.
FireMesh uses BLE only to discover nearby mesh peers — we do not track, store, or transmit your location.
The BLE scan flag neverForLocation is set in our manifest.
End-to-End Encryption
All messages in FireMesh are protected with military-grade end-to-end encryption:
- Ed25519 — Digital signatures for identity verification
- X25519 — Elliptic Curve Diffie-Hellman key exchange
- ChaCha20-Poly1305 — Authenticated encryption for all messages
- Argon2id — Memory-hard key derivation for private key protection
- Double Ratchet Protocol — Perfect Forward Secrecy (same protocol as Signal)
This means that even if a message is intercepted during BLE or LoRa transmission, it cannot be read by anyone other than the intended recipient. We, as the developers, also have no ability to decrypt your messages.
Internet Usage (Optional)
FireMesh is designed to work completely offline using BLE, LoRa, and Wi-Fi Direct. However, an optional Internet transport is available via Nostr protocol relays.
When Internet Is Used:
- Only when you explicitly enable the Internet transport in Settings
- Messages sent over Internet are end-to-end encrypted before transmission
- Nostr relays see only encrypted payloads — they cannot read message content
- The relay servers used are third-party public Nostr relays; FireMesh operates no servers
When Internet Is NOT Used:
- All BLE mesh communication (phone-to-phone)
- All LoRa radio communication (phone-to-ESP32-to-phone)
- All Wi-Fi Direct communication
- The App requires no internet connection to function
SOS Emergency Feature
FireMesh includes an SOS emergency broadcast feature. When activated, the App may include your GPS coordinates in the SOS alert to help responders locate you.
- SOS location data is broadcast only when you manually trigger the SOS button
- Location is shared only via peer-to-peer transports (BLE, LoRa) to nearby devices
- Location data is never sent to any server
- You can send SOS alerts without location data
Third-Party Services
FireMesh does not integrate any of the following:
- ❌ Google Analytics or Firebase Analytics
- ❌ Facebook SDK or any social media tracker
- ❌ Advertisement networks (AdMob, etc.)
- ❌ Crash reporting services (Crashlytics, Sentry, etc.)
- ❌ User behavior tracking tools
The only optional third-party connection is to public Nostr relay servers, which only receive end-to-end encrypted data when the Internet transport is enabled by the user.
Data Sharing
We do not share, sell, rent, or trade any user data with any third party. Since we do not collect any data, there is nothing to share.
Data Retention & Deletion
All data is stored locally on your device:
- To delete all data: Uninstall the App or clear App Data from Android Settings
- To delete individual conversations: Use the delete option within the App
- No server-side data exists — uninstalling the App removes all traces
Children's Privacy
FireMesh is not directed at children under the age of 13. We do not knowingly collect personal information from children. Since the App does not collect any personal information from any users, this policy applies universally.
Security
We take the security of your communications seriously:
- All cryptographic operations use industry-standard algorithms
- Private keys are encrypted with Argon2id before local storage
- The Double Ratchet protocol ensures Perfect Forward Secrecy — compromising one message key does not compromise past or future messages
- Message signatures prevent impersonation and tampering
- BLE communication uses custom GATT services to prevent spoofing
Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated "Effective Date". We encourage you to review this page periodically. Continued use of the App after changes constitutes acceptance of the revised Privacy Policy.
Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us: