Questions, answered.

Two independent paths. Your phone's motion sensors detect a high-impact event on the device itself — force, rotation and post-impact stillness all have to agree before anything escalates, because a dropped phone hits harder than a real crash does. Separately, your wearable streams heart rate, blood oxygen and heart-rate variability to our risk engine, which scores them against your own baseline rather than a textbook average. Either path opens a countdown you can cancel.

Your alert moves through a clear sequence: armed → cancel countdown → dispatched → a live view of who's coming → stand-down once you're safe. You always see what state you're in, and every one of those transitions is recorded.

Yes — photograph a prescription, lab report or discharge summary and it is read automatically and filed as a dated entry: what the document says, and when. Because it is machine-read from a photo of paper, we show you exactly what was understood and ask you to check it — you can confirm an entry, or mark it wrong so it stops being used. Entries we could not read confidently are flagged as such rather than presented as fact, and a document with no printed date is labelled with the date it was uploaded instead, so a prescription photographed months later is never filed as if it were issued today. Your assistant uses this history when it is relevant, and a hospital treating you sees it on arrival.

No. DashResQ runs on devices you already wear or carry — for example an Apple Watch and your phone. There's no dongle to install. A dedicated in-vehicle unit is in development for vehicles that are shared, unattended or used by fleets.

We're rolling out across major smartphones and popular wearables in India first, starting with iPhone and Apple Watch. Support expands continuously — check back or ask us about your specific device.

Crash detection runs on your device. Vitals are streamed to our backend so they can be scored against your personal baseline over time. Either way, your medical profile is only released at the moment of a real emergency — to the responders actually assigned to it and to the contacts you chose — and responders see only what their role needs, so a driver sees allergies while a hospital clinician sees full medication detail. Every release is recorded in an audit log. See our Privacy Policy for details.

You, and a hospital treating you. Nothing is shared with responders in the field beyond what their role needs. You can switch off routine sharing with hospitals at any time in the app — but a hospital that is actually treating you can still access your record in an emergency, and that access is flagged and logged separately so you can see it happened. We'd rather tell you that plainly than offer a switch that quietly doesn't hold when it matters. See our Privacy Policy for details.

Volunteers need a minimum first-aid certification and admin approval. Clinical responders are always dispatched ahead of volunteers.

Every escalation opens a 15-second cancel countdown — "I'm OK, cancel". Nobody is notified until that window expires, so a false alarm costs you a single tap. If your phone dies mid-countdown, our server escalates on your behalf rather than letting the alert disappear.

Crash detection runs on your device, so it works with no signal at all. Readings and events are queued on the device — your watch holds them on disk and retries with backoff — and they forward automatically once you're back in range. Reaching responders and emergency services still needs connectivity.

No. Emergency features are supplementary and do not replace professional emergency services or medical care. Our assistant explains and escalates — it never diagnoses a condition and never recommends medication.

The life-saving core is free — crash and vitals detection, automatic emergency-contact alerts, responder dispatch, and one-tap calling for 108 and 112 with your location ready to read out. Advanced and partner features may be offered as paid plans.