Incident Detection

Help & Guide

A practical walkthrough of what the app does and how to set it up. Short on details? See the FAQ.

Before your first session

Two things are worth doing before you rely on the app for real:

Picking an activity

The Home screen's activity picker is where every session starts. Most entries — Bike, Motorcycle, Run, Walk, Hike, Car, and water activities (kayak/canoe) — track a real GPS route, speed, distance, and elevation, and watch your phone's motion sensors for a possible crash or fall. Three entries work differently:

How crash detection works

During a tracked session, the app watches the accelerometer and gyroscope for a sudden spike — the kind produced by a fall or impact — and cross-checks it against a sharp drop in GPS speed. When both line up, it shows a countdown (30 seconds by default) with a big I'm OK button. If you tap it, nothing else happens. If the countdown runs out, the app:

If a message doesn't seem to go through (no signal at the moment), it's retried automatically once you have signal again, at a resend interval you can adjust in Settings.

Sessions without GPS

Some activities happen where GPS doesn't work well or at all — a treadmill, an indoor track. Run and Walk sessions can turn off GPS tracking, switching distance/pace estimation to your phone's built-in step counter, using a stride length estimated from your height (set once in Settings). If you pair a Bluetooth treadmill instead, the app reads its actual speed/distance directly, which is more accurate than the step counter. Car and Motorcycle sessions can also run GPS-free, but without a step counter or treadmill equivalent to fall back on — they just track duration, with crash/fall detection from motion sensors alone and no distance or pace.

Crash/fall detection still runs in every GPS-free mode — it just relies on motion sensors alone, without the GPS-speed-drop cross-check used in a normal GPS session.

Pairing sensors

From Settings, you can pair Bluetooth accessories the app will reconnect to automatically on future sessions:

Guardian mode

Guardian mode pairs two phones over Bluetooth (a "Guardian" and the person being tracked) so each can tell the other is still nearby, without either phone sharing live GPS location with the other — the only thing exchanged is a short-range Bluetooth signal confirming proximity.

Full technical detail on exactly what's exchanged and when is in the Privacy Policy (§9).

Session history & export

Every finished session is saved to your history, with a warning icon on any where an incident alert was triggered. A session's summary screen shows its route (if it had one) and pace/heart-rate/cadence charts (if recorded), and lets you export it as a GPX file (or FIT, for a GPS-free session) to share to another app like Garmin Connect — or, if you've connected a Strava account in Settings, upload it directly.

Testing the alert flow

Settings has a "Test notification system" button — no need to start a session first. Tapping it checks that everything a real alert depends on is actually in place (emergency contacts, SMS/location permission, and so on); if something's missing, it tells you what before letting you continue.

Once everything checks out, it asks you to confirm before doing anything. The test itself is real, not a mock — it mirrors exactly what a real alert would do with your current settings: it sends an actual SMS to your emergency contacts (clearly marked as a test, not identical to a real alert), and if you've enabled auto-call, places a real call to your primary contact too, and if you've enabled MMS photos, attaches a real photo the same way a real alert would. It's worth running once so you know it actually works — just give your contacts a heads-up first.

If you see a warning banner

A live session shows a banner if something would stop an alert from working right now — most often no cellular signal (the app watches your phone's service state, if you've granted the optional Phone State permission), or a permission that's been revoked since the session started. Tap it for detail on what's wrong and, where there's actually something to fix (a permission), a shortcut to Settings.

Getting more help

Check the FAQ first — most specific questions (battery use, data handling, what a given permission is for) are answered there. Anything else: support@incident-detection.com.