Skip to content

Observer data and privacy

Treat anything heard by an observer as public. An observer does not decrypt private messages, but it can forward packet details and status information. Do not put private names, locations, credentials, or other sensitive information in MeshCore messages.

ObserverSends packet data and status from the radio settings it uses.
CoreScopeCan show observer, packet, and map data publicly.
BrokerDirect subscriptions are restricted, but data shown in CoreScope is still public.

Policy summary

Question Answer
Who manages this? MeshCore Canada infrastructure administrators
Where can I ask questions? MeshCore Canada forum
How long is data kept? A public retention period has not yet been published

Do not assume data will be deleted after a certain time. Ask the infrastructure team if you need a retention or deletion timeline.

Data flow

  1. Radio packettransmitted on the configured mesh
  2. Observerhears and forwards telemetry
  3. Infrastructurereceives and may store it
  4. CoreScopemay display it publicly

Changing the radio preset changes what the observer can hear. Public and private channel choices do not make the surrounding packet telemetry private.

Collection, access, and retention

Data Why it is used Where it may appear Who can access it Retention
Observer status Show whether an observer is online CoreScope Public viewers; infrastructure operators Not publicly specified
Heard packet telemetry Show mesh activity and help diagnose coverage CoreScope packet views and maps Public viewers; approved subscribers; infrastructure operators Not publicly specified
Location code Group an observer near a known place Observer lists, topics, maps Public viewers and broker users Follows observer/packet retention
Optional owner details Help identify a service Integration-dependent status data May reach infrastructure and CoreScope Not publicly specified
Broker credentials Authenticate the observer Should remain only in the local integration Local operator and authentication service Never include in public diagnostics

MeshCore Canada does not offer general direct broker subscriptions. Direct access is limited to CoreScope, local mesh administrators, and people approved by the infrastructure administrators.

Where it appears

CoreScope shows observer, packet, and map information. Other approved MeshCore Canada services may use the same feed.

Broker access controls do not make information private once CoreScope displays it.

Before you operate an observer

  • [ ] Tell people using the local mesh that an observer is active.
  • [ ] Use a broad observer name, not a home address or person's name.
  • [ ] Leave optional owner email fields blank unless they are operationally needed.
  • [ ] Never paste Wi-Fi passwords, MQTT tokens, private keys, or unredacted logs into support messages.
  • [ ] Read the method's verification and recovery steps before making changes.

Return to Choose an observer setup, or see what to remove before asking for help.