GuardBand / WORKING NAME

A signal on your wrist.
A person on the other end.

An idea for intentional gesture SOS and contextual check-ins that would need careful evaluation. Hardware, firmware, apps and detection models are proposed future work; no product prototype is presented.

Illustrative wearable industrial designCONCEPT VISUAL · NOT A MANUFACTURED PRODUCT
START WITH WHAT MATTERS

Two signals.
Two different decisions.

01

“I am asking for help.”

A deliberately enrolled gesture or accessible manual SOS would take a priority route. A routine workout or a low heart rate must not suppress it.

02

“Something may need attention.”

Passive movement patterns are uncertain. Future sensor-quality checks and bounded check-ins could inform a response, but neither capability has been developed or validated for this idea.

Try the interaction ↗
THE PROPOSED SYSTEM

Proposed in layers.
To be tested together.

SENSE

Movement with context

Accelerometer and gyroscope data could describe acceleration and rotation. A compass adds heading; none alone gives reliable absolute position.

INTERPRET

Personal, with limits

On-device inference and opt-in personalization are research ideas. A 30-day learning period is not validated, and any adaptation would need safeguards against normalizing repeated distress.

CONNECT

Support with clarity

Phone-assisted location and communication are a candidate feasibility path. Standalone cellular operation would need separate hardware, network and power evaluation.

ONE CONCEPT, SEVERAL POSSIBILITIES

Explore the form it could take.

⌁
HARDWARE EXPLORATION

A dedicated safety band

A proposed wrist-worn device combining motion sensors, haptics and phone connectivity. Custom firmware or an embedded operating system would be selected after feasibility work.

Battery life, water resistance, sensing rate and enclosure design are unverified engineering targets.

LOCATION, ON YOUR TERMS

A location is useful
only with its context.

The idea proposes normal-use location intervals from 5 minutes to 2 hours, with a 15-minute default. An opt-in journey could request more frequent updates, route context and an ETA; an incident could request the freshest available location. None is implemented as a safety service here.

Every location must show timestamp, uncertainty and connectivity status. Indoor positioning, tunnels, network loss and battery limits can prevent fresh updates. Reaching a destination alone must not close an active incident.

What is—and isn’t—established

  • Concept requirements documented
  • Website interaction demonstration available
  • Sensor and hardware feasibility: planned
  • Heart rate and SpO₂: possible wellness features, not evidence of assault or a medical diagnosis
  • Apple, Samsung, Noise and boAt compatibility: not established
  • Police partnerships and patent filing: not verified
CAPABILITIES & DEPENDENCIES

What we are exploring. What it depends on.

CapabilityCurrent statusWhat must be established
Deliberate gesture SOSProposedGesture recognition, accidental-trigger tests and an accessible manual fallback.
Passive incident check-insResearch questionConsented data, target-event definitions and false-positive/false-negative validation.
Location and journey modeProposedSupported phone/GNSS permissions, route and ETA estimates, fix age, uncertainty and power budget. A route deviation or arrival must not establish danger or safety by itself.
Trusted-contact alertsProposedRecipient consent, notification delivery, acknowledgements and cancellation updates.
Police / responder consoleNot integratedAuthorized partnerships, jurisdiction routing and operating agreements.
Standalone cellular operationHardware optionModem, network support, antenna, subscription and runtime testing.
Wellness features and custom firmwareCandidate scopeHardware platform, sensor quality, feature scope and maintenance plan.
Existing watch integrationCompatibility unverifiedVendor APIs, permissions, background execution and supported-device testing.
User-controlled standbyProposed controlClear paused status, accessible confirmation and secure setting changes. Any explicit SOS path depends on powered, supported hardware and connectivity.
THREE PROPOSED APP ROLES

How each person might take part.

The wearer

A future wearer app could enrol a gesture, manage contacts and sharing, and offer safety confirmation. Accessibility, cancellation and anti-coercion controls would need dedicated evaluation.

The trusted contact

A future contact app could show a notification, location age and an acknowledgement option. No such app is available; acknowledgement would not establish safety or completed assistance.

An authorized responder

A future console could support case context and incident coordination. It requires a legitimate integration; no police app, dispatch or officer assignment exists today.

A PROPOSED FIRST-USE JOURNEY

A first-use idea to evaluate.

  1. 01

    Check compatibility

    Confirm the supported hardware, phone, permissions and connection requirements.

  2. 02

    Choose your circle

    Invite consenting contacts and agree what they should do when an alert arrives.

  3. 03

    Learn and rehearse

    Practice a supported SOS gesture and cancellation flow safely, without contacting emergency services.

  4. 04

    Review privacy

    Choose time-limited sharing and understand when location is available or stale.

  5. 05

    Check readiness

    Make battery, connectivity, sensor status and unacknowledged incidents visible.

Explore product FAQs →
WhatsApp