What the network sees
- Path metrics: latency, jitter, packet loss, reachability of probe targets. That is the measurement; the node never inspects traffic on your LAN.
- Your node's readings if you publish them (own sensors are private unless you make them public).
- Metadata of LoRa frames (which node or gateway a frame was for, when, from which listener) — never the content.
What stays with you
- Identity: a secp256k1 key pair generated on the board. Ownership: your wallet address. There is no user table, no e-mail, no account.
- The tunnel key: written by your phone onto the node over your Wi-Fi. The server cannot open a tunnel into your LAN.
- LoRa keys: the key phrase for your sensors lives on the node (and the sensors) — or, for frames addressed to your paired LoRaWAN gateway, in your own Home Assistant, which decrypts them itself. The server routes encrypted frames blind.
- Your exact position: used once for attestation; the public map shows a position shifted by 200–800 m. Ghost mode removes the node from the map entirely (it keeps earning, less).
The Android app
The app has no account and no e-mail. What it sends to sensmos.com and why:
- Your wallet address — it is how a node knows its owner. The private key never leaves the phone.
- Your phone's location, once, when you add a node — to confirm the board is physically where it says it is. It is optional: without it the node works and earns less. The exact position stays private; the public map shows a blurred one, and ghost mode hides the node entirely.
- A notification token (Firebase Cloud Messaging) — so the app can tell you, for example, that your node went offline. Google's servers deliver it, so they see the short notification text; your nodes' data is not sent there.
- Communicator messages — encrypted on your phone before they leave it. The server only relays the encrypted frames (kept up to 48 hours for delivery) and never has the keys, group names or content.
The app uses Bluetooth only to talk to your own boards, and the camera only to scan QR codes on the phone itself. There are no ads, no analytics SDKs and no crash reporting.
Open by default
The firmware is public; the node's local page (its LAN IP) shows what it is sending right now. Web analytics on this site are cookie-less and do not store IPs.