Test Report

What the field demos showed.

A public summary of how the Mysafehub demo performed across mesh relay, verification, offline navigation, and reunification — with the limitations stated plainly. Last updated September 2026.

< 250 B

Maximum emergency payload size

2

Radio paths per device (BLE + Wi-Fi Direct)

3

Identity verification tiers

0

Internet or towers required

Mesh relay & delivery

Passing in field demos

Structured SOS payloads relayed device-to-device over Bluetooth Low Energy and Wi-Fi Direct. Store-and-forward queues held payloads on relay devices when no responder was in range, and delivered them once a path appeared — with no cellular or internet connection involved.

  • ✓Payloads capped at 250 bytes: category, coarse location, timestamp, verification level.
  • ✓Dual radio paths (BLE for proximity, Wi-Fi Direct for longer hops) operated interchangeably.
  • ✓Encrypted queues on relay devices could not be read by the relaying user.

Citizen SOS flow

Passing in field demos

One-touch SOS presented a structured emergency grid — trapped structure, medical, fire, water, food, threat — so a citizen could file a complete, responder-ready alert in seconds, without typing.

  • ✓Structured categories removed free-text entry from the critical path.
  • ✓Hands-free sentry mode was reachable directly from the SOS screen.
  • ✓Identity verification was offered inline without blocking the alert.

Three-tier identity verification

Passing in field demos

The verification sheet presented all three tiers — Anonymous, Biometric Liveness Verified, and Official First Responder — and enforced their distinct trust levels across the interface.

  • ✓Tier 0 alerts displayed an “Unverified Sender” warning to responders.
  • ✓Tier 1 liveness checks ran on-device; only the secure-enclave signature left the phone.
  • ✓Tier 2 activation required a pre-authorized organization code; unverified attempts were rejected.

Offline navigation & resources

Passing in field demos

With connectivity fully disabled, the compass view pointed to the nearest safe haven with distance and direction, and the offline map rendered shelter, water, medical, and hazard points from the preloaded city pack.

  • ✓Compass gave bearing, distance, and estimated capacity for the nearest haven.
  • ✓Triage filters (safe zone, medical, water, food) worked entirely offline.
  • ✓Hazard markers such as debris and collapsed structures rendered on the vector map.

Reunification & evidence

Passing in field demos

Family reunification search and “I'm alive” check-ins functioned over the mesh, and the encrypted incident log's decoy-PIN duress protection behaved as designed.

  • ✓Check-ins propagated device-to-device without a central server.
  • ✓Decoy PIN opened a sanitized view; the real log remained sealed and unprovable.

Known limitations

  • ▲Delivery time depends on device density — sparse areas rely on store-and-forward rather than instant relay.
  • ▲Figures here are from controlled field demos, not yet a live city-scale incident.
  • ▲Responder board scoring (proximity, access roads, urgency, elapsed time) is validated against simulated incidents; live-incident calibration is part of upcoming pilots.

Questions about the methodology?

We are happy to walk evaluators, funders, and partner organizations through the demo setup in detail.

Contact the team