Skip to main content

Emergency-Use Limitations and Safety Disclaimers for Allo

Understand what Allo guarantees and does not guarantee, and why you must always maintain a backup communication plan alongside Allo.

Allo is designed to provide reliable off-grid communication when conventional networks are unavailable. It is built for emergency responders, municipalities, and safety regions operating in the field under challenging conditions. However, like all radio-based systems, Allo operates on a best-effort basis: delivery depends on physical conditions, hardware state, and network topology that no software system can fully control. Understanding these limitations is essential for safe operational use.

Allo must not be used as the sole means of emergency communication. Always maintain a backup communication plan — such as PMR radio, a phone bridge, or in-person relay — that does not depend on Allo. In a genuine emergency, no single communications system should be a single point of failure.

What Allo provides​

Allo is a best-effort radio mesh messaging system. When all components are functioning and within range, it delivers text messages reliably across a local mesh network without requiring internet or cellular connectivity. Specifically, Allo:

  • Transmits messages hop-by-hop across the radio mesh formed by active client devices and repeaters
  • Provides delivery confirmation when a message reaches its destination device
  • Operates fully off-grid — no internet connection, mobile data, or Wi-Fi is required for message transmission
  • Allows administrators to review message delivery logs in the web dashboard after an incident or exercise

What Allo does NOT guarantee​

Allo cannot guarantee that every message will be delivered to every recipient. Delivery depends on:

  • The recipient's device being powered on and within radio range of the mesh
  • The recipient's phone maintaining an active Bluetooth connection to their Allo device
  • Sufficient mesh density — if there are no devices or repeaters between sender and recipient, the message cannot be relayed
  • Physical radio propagation conditions, which vary with terrain, building materials, weather, and interference

A delivery confirmation in the app indicates that the message reached the recipient's device. The absence of a confirmation does not prove the message was not sent — it means delivery to that device could not be confirmed at that time.

Responsibilities of the operator​

Organisations deploying Allo accept responsibility for:

  • Training users on the correct operation of the app and client device
  • Establishing and communicating a backup communication plan before any exercise or operational deployment
  • Ensuring devices are charged and properly provisioned before use
  • Reviewing delivery logs after exercises and taking corrective action where gaps are identified
  • Not representing Allo to end users as a guaranteed emergency communication system

Allo is intended to supplement existing emergency communications infrastructure, not replace it. The system is most effective when used alongside established protocols and backup channels, not in place of them.

Before any exercise or operational deployment using Allo, ensure the following are in place:

  • A designated fallback communication channel (for example traditional PMR/TETRA radio, a mobile phone bridge, or a predetermined in-person rally point)
  • All participants aware of the fallback channel and trained in its use
  • A clear trigger condition that tells participants when to switch to the fallback channel (for example: "if you have not received a response to a message within five minutes")
  • The fallback channel tested and confirmed operational before the exercise begins

How Allo fits into your communications framework​

Allo is a supplementary communications tool intended for operational use by trained personnel within a defined organisation. It is not a certified emergency alerting system, and it does not replace the primary communication infrastructure that your organisation already has in place.

Before deploying Allo in any operational or exercise context, confirm with your safety region coordinator, municipal security officer, or equivalent authority how Allo should sit alongside your existing communications protocols.

If you have questions about these limitations or need guidance on how Allo fits into your specific operational context, contact the Allo team directly. See Privacy for contact details.