HAEVEN X
Search the guide
↑↓ navigate Enter open Esc close

Crash Detection setup

How the multi-sensor pipeline decides a crash happened, what it does next, and how to test the alert.

5 min

HaevenX runs a continuous background analysis on every family member's phone, looking for the signature of a vehicle crash: a sharp impact spike, followed by sustained low-frequency vibration, followed by sudden stillness. When the pattern matches, the app fires a 10-second confirmation overlay (in case it's a false positive) and then dispatches help to two channels at once: the on-duty patrol in your neighborhood and you, the family master.

What the phone is actually watching for

  • Accelerometer spike above ~6 g (typical low-speed fender-bender) or ~10 g (highway impact).
  • Gyroscope rotation: the phone tumbles or rotates faster than 2 rad/s.
  • Activity classifier says "in vehicle" before the spike (filters out you dropping the phone).
  • Audio classifier (iOS only): Apple's SoundAnalysis framework flags a crash sound (collision, glass breaking, airbag deploy) within the same second.
  • Sustained stillness for at least 8 seconds afterward (filters out you tossing the phone in your bag).

All five signals together gives a strong-evidence trigger. Three of five gives a medium-evidence trigger that still fires the confirmation overlay but waits longer for response before escalating.

Setting it up

On the kid's phone:

  1. Open HaevenX, go to Settings → Crash Detection.
  2. Toggle Enabled on.
  3. Pick a sensitivity: Low (only highway-grade crashes), Medium (default, catches most real crashes with few false positives), or High (catches everything including possibly bumpy off-roading).
  4. Make sure Motion and Fitness is granted (iOS will prompt; if you missed it, re-grant in iOS Settings → HaevenX).
9:41 HAEVEN X ● ● ●

Crash Detection Settings

Crash Detection settings screen with sensitivity slider

Medium is the default and the right choice for almost everyone.

What happens when the phone thinks there's a crash

  1. The kid's phone vibrates aggressively and shows a full-screen overlay: "Crash detected. Tap I'm OK or hold for help."
  2. A 10-second countdown starts.
  3. If the kid taps I'm OK, the alert is canceled and a "false positive" event is logged so we can tune the model.
  4. If the kid does nothing for 10 seconds, the system fires emergency dispatch:
    • The on-duty patrol in their neighborhood gets a high-priority push with the kid's GPS, name, and (if you've filled it in) the medical info from your emergency plan.
    • You, the family master, get a push: "Crash detected for Sarah. Patrol dispatched."
    • If you have an emergency contact configured, they get a text within the same minute.

Testing it without crashing your car

From the Crash Detection settings screen, tap Send test alert. The kid's phone behaves exactly as it would for a real crash (overlay, countdown, dispatch) but the alert reaching the patrol and family master is clearly tagged TEST. Run this once when you set things up so everyone knows what to expect.

What it doesn't catch

  • Crashes where the phone wasn't physically in the vehicle (kid in another car).
  • Crashes where the phone is destroyed by the impact (rare but possible). For this case, the kid not responding to your normal Visible Check-In within 60 seconds is the next-best signal.
  • Pedestrian or cyclist accidents at low speed (the phone doesn't see the right impact signature). For cyclists we have an extended detector available; ask hello@haevenx.com.