Privacy Policy & Terms
Last updated: September 9, 2026
Privacy
What PocketMic does NOT collect
- No personal data. PocketMic has no account system, no user registration, and no login.
- No telemetry. The app does not phone home, send analytics, or report usage to any server.
- No cloud. All audio stays on your private LAN. No audio data is sent to the internet.
- No tracking. No cookies, no fingerprinting, no ad identifiers.
What stays on your devices
- Pairing key: stored encrypted at rest on Android via the system Keystore (EncryptedSharedPreferences). Stored in the receiver's local settings file on Windows.
- Connection settings: IP address, port, capture mode, and gain โ stored locally on each device.
- Session diagnostics: packet counters and jitter stats are stored locally on the Windows receiver and can be exported as a Markdown report. Nothing is transmitted off-device.
Network
PocketMic communicates only over your local network (LAN). The Android app sends UDP packets to the IP address you specify. The Windows receiver listens on the port you configure. No data leaves your private network.
The marketing website (canopydigital.ca/sites/pocketmic-lan/) does not use cookies or tracking scripts. It loads one external script (Buy Me a Coffee button) from cdn.buymeacoffee.com.
Terms of Service
License
PocketMic LAN is released under the MIT License. You are free to use, modify, and distribute the software.
No warranty
The software is provided "as is", without warranty of any kind, express or implied. See the MIT License for full terms.
Intended use
PocketMic is designed for use on a trusted private LAN. It is not a hardened internet voice service. Do not port-forward the receiver to the public internet.
Security
Audio is encrypted with AES-256-GCM. The pairing key is derived via SHA-256. The control channel uses HMAC-SHA256 with domain separation. These measures protect packet contents and integrity on a trusted LAN; they do not make PocketMic suitable for adversarial network environments.
Contact
For questions about this policy, open an issue on GitHub.