Guides · Crash detection
Crash detection explained simply
Crash detection tries to notice a sudden, severe impact using the same motion sensors that detect screen rotation and step counting. It is a helpful backup when a person cannot press SOS after a collision—but it is not a substitute for seatbelts, safe driving, or emergency services.
What the phone can sense
Modern phones measure acceleration in multiple directions. A vehicle collision often creates a sharp spike in g-force followed by stillness. Zone Tick looks for that pattern and can factor recent speed context when available. Everyday drops, sports, or putting a phone on a hard table can also create spikes, which is why sensitivity and confirmation logic matter.
Why false alarms happen
- Dropping the phone onto concrete or tiles
- Aggressive braking that is not a crash
- Rough roads combined with a loose phone mount
- Sports impacts or accidental high-force motion
A good system reduces false alarms by requiring stronger peaks for low-speed moments and by waiting briefly to see whether the phone (and likely the vehicle) becomes still. Even then, no consumer phone algorithm is perfect.
How to use crash detection wisely
- Enable it when you regularly drive or ride with the phone on you.
- Tell your circle that automatic alerts exist, so a surprise notification is not confusing.
- If you get a false alert, cancel quickly and adjust sensitivity if the app offers it.
- Keep SOS available as the primary manual tool—crash detection is a safety net, not the only net.
What recipients should do
Treat an automatic crash alert like a real SOS until you know otherwise: try calling, check location if shared, and contact emergency services if the situation looks serious and there is no response. After a false alarm, a short message in the family chat resets everyone’s nerves.
Privacy note
Sensor data is used to decide whether to raise an alert. Zone Tick is not designed to sell your motion history. See the Privacy Policy for retention details.