Configure privacy for emergency radio
Make your MeshCore communications as private as you need them. Encryption, identity control, and location settings explained.
Why privacy matters during emergencies
Emergency situations can involve sensitive information: your location, your plans, your family's movements. MeshCore provides robust privacy features, but they work best when configured thoughtfully.
This guide walks through encryption options, identity management, and location controls. Configure once and communicate confidently when it matters most.
Encryption in MeshCore explained
🔐 Private message protection
Private messages are encrypted. In the current MeshCore implementation this uses AES-128 plus a MAC. That is useful protection, but it should be described more carefully than broad AES-256 or military-grade claims.
📻 Open channels are open
Public channel messages have no encryption. Anyone with a compatible radio can read them. Reserve channels for non-sensitive coordination.
🔑 Password-protected channels
Create channels with shared passwords for group privacy. Members with the correct key can read; others cannot. Suitable for family groups or response teams.
⚠️ Visible metadata
Your username, message timing, and location (if broadcast) remain visible. Only private message content is encrypted.
Privacy configuration steps
1. Select an appropriate username
When anonymity matters, avoid recognisable identifiers. "Radio_4721" discloses less than "Tom Sheffield". Consider your threat model.
2. Control location broadcasting
Location sharing is optional. Disable automatic broadcasting: Settings → Position → Disable. Share manually only when necessary.
3. Confirm encryption status
Private messages should encrypt automatically. Verify: Settings → Security → Encryption = Enabled.
4. Use robust channel passwords
When creating private channels, choose long random passwords. Avoid predictable choices. Minimum twelve characters with varied types.
5. Reduce visible device details
Configure how much others learn about your hardware. Less information equals greater privacy. Settings → Device → Minimise details.
6. Audit your contacts periodically
Review who has access to your private channels. Remove unfamiliar or obsolete entries. Maintain awareness of your communication circle.
Practical privacy habits
Reserve sensitive information
Avoid sharing addresses, detailed plans, or personal identifiers on public channels. Assume others may be monitoring.
Change passwords when circumstances change
Rotate channel passwords after disputes or departures. A password shared with someone who left may no longer be secure.
Share location intentionally
Broadcast position only to trusted recipients for specific purposes. Default to location sharing disabled.
Consider pseudonymous operation
For heightened sensitivity, operate under an alias. Change identifiers periodically if warranted.
Disable unnecessary telemetry
Turn off automatic status broadcasts if privacy is paramount. Minimise passive information disclosure.
Find your balance
Maximum privacy can impede coordination. Calibrate settings to your actual circumstances rather than theoretical extremes.
Privacy configuration questions
How secure are private messages?
Private message content is encrypted, but metadata such as who, when and sometimes location can still be visible. For maximum protection, combine encrypted messaging with pseudonymous operation and careful location sharing.
Can relay nodes read my messages?
No. Relay nodes forward encrypted packets they cannot decrypt. Only public channel messages are readable by relay nodes.
Could someone intercept my communications?
Radio Signals are technically capturable. But private messages are encrypted – without your keys, captured traffic is meaningless. Public channels are readable.
How do I maximise anonymity?
Use a random username, disable location sharing, change identifiers periodically, communicate only via private messages with trusted contacts.
Private messages versus private channels – what differs?
Private messages are direct encrypted conversations. Private channels are password-protected groups. Both can be protected, but shared channel keys mean all members with that key can read the same traffic.
Should I worry about privacy on MeshCore?
For emergency use, MeshCore offers substantially better privacy than CB radio, PMR446, or unencrypted alternatives. Configure thoughtfully and your communications are well protected.
Secure, private emergency communications
Proper privacy configuration makes MeshCore a secure platform for sensitive emergency communications. Encryption, identity control, and awareness form the foundation of private messaging.