How a phone knows a crash happened
Modern phones carry accelerometers and gyroscopes sensitive enough to feel the physics of a collision: a violent deceleration spike, a direction change no normal driving produces, often followed by sudden stillness. FamilyTracking watches for that signature whenever it detects you're driving — and combines motion data with speed and GPS context to filter out dropped phones and hard braking.
Detection runs on-device. Your motion data isn't streamed anywhere; only a confirmed event leaves the phone.
The countdown: a chance to say 'I'm fine'
When a possible crash is detected, the phone sounds a loud alarm and shows a full-screen countdown — 60 seconds to tap 'I'm OK'. Fender-bender, dramatic pothole, phone launched off the dashboard: one tap, nothing happens, nobody is alarmed.
If the countdown expires with no response, the Circle receives a maximum-priority alert — 'Possible crash · Dad · Hwy 280' — with the precise location and a live trail, the same unmissable delivery as a manual SOS.
Honest limits you should know
No phone-based system detects every crash. Low-speed collisions may not produce a clear sensor signature; a phone in a padded bag reads the world dimly; and detection requires the phone to survive the impact and have signal to send the alert. Independent testing across the industry shows phone-based detection is good and improving — and imperfect.
We'd rather you know that than trust it blindly. Crash detection is a safety net under your seatbelt, airbags and good driving — never a substitute, and not a guarantee.
Designed alongside teen driving tools
Crash detection pairs naturally with driving reports and speed alerts: the reports help build safer habits over months; detection covers the moment habits aren't enough. For parents of new drivers, the combination addresses both the chronic worry and the acute one.
It also matters at the other end of life — adult children enable it for parents in their seventies who still drive, where a minor crash can have major consequences and self-reporting is least reliable.
Who turns it on
- Parents of new drivers. The first two years behind the wheel are statistically the riskiest of a driving life.
- Long solo commutes. Rural highways late at night are exactly where an automatic alert earns its keep.
- Older drivers. Adult children enable it for parents still driving in their seventies and eighties.
- Motorcyclists in the family. Higher stakes, lower visibility — and a rider who can't always reach a phone.
- Road-trip season. Many families switch it on for the holiday drive even if it's off the rest of the year.
Stronger together: pairings worth enabling
No FamilyTracking feature lives alone — this one gets noticeably better next to the right neighbors:
- Driving safety reports. Reports build the habits that prevent crashes; detection covers the day habits aren't enough. One Premium bundle, both layers.
- Speed alerts. The same trip-detection engine powers both — enabling one makes the other free in battery terms.
- SOS emergency button. A conscious driver after a minor crash can skip the countdown and fire SOS directly — the manual and automatic paths converge on the same family alert.
The bottom line
Crash detection is insurance in the truest sense: you pay a little (Premium, a sliver of battery), hope it stays unused, and value it entirely for the one day it isn't. Enable it for the drivers whose worst-case scenario keeps you up — the new teen driver, the long commuter, the parent in their late seventies — and respect its honest limits: it supplements seatbelts and judgment, never replaces them. The 60-second countdown means false alarms cost a tap, which removes the only good argument against leaving it on for every driver in the Circle.