FAQ

No, to both. It's best-effort software running on your phone's own sensors, not a certified safety or medical device, and it doesn't guarantee a crash or emergency will be detected. If you're conscious and able, always call emergency services (e.g. 112/911/999) yourself first — the app's alert is a supplementary channel to people you personally choose, not a dispatch service. Full detail in the Terms of Service.

A countdown appears (30 seconds by default) with an "I'm OK" button. If you don't tap it, the app texts every emergency contact you've configured with your location, optionally calls your primary contact and attaches photos (both off by default, toggled in Settings), and scans for nearby Bluetooth devices twice in the following couple of minutes. See the Help & Guide for the full flow.

The app has no server or alternate delivery path — an SMS, call, or MMS needs at least some carrier signal to send, the same as any other message from your phone. If you grant the optional Phone State permission, a live session shows a warning banner when there's no signal, so you at least know an alert wouldn't get through right now. If sending fails, it's retried automatically once signal returns.

Yes — Settings has a "Test notification system" button, no session needed first. It checks that everything a real alert depends on (emergency contacts, permissions) is actually in place, tells you if something's missing, and only sends anything once you confirm. The test itself is real, not a mock — it mirrors exactly what a real alert would do with your current settings: an actual SMS to your emergency contacts (clearly marked as a test), a real call to your primary contact if auto-call is on, and a real MMS photo if you've enabled that too. Worth running once so you know it actually works — just give your contacts a heads-up first.

Every emergency contact you've added gets the SMS. Only your primary contact — the first one in your list — also gets an automatic phone call, and only if you've turned that on in Settings.

No, by default — there's no server or backend at all. Everything (routes, sessions, contacts, settings) stays on your device until you delete it or uninstall the app. The one opt-in exception is connecting a Strava account, which uploads only the sessions you choose, directly from your device to Strava. Full detail in the Privacy Policy.

Location and SMS are required to start most sessions — the app blocks starting one and tells you exactly what's missing rather than fail later. Everything else (Camera, Phone calls, Bluetooth, notifications, physical activity, phone state) is optional and only gates the specific feature it's for — e.g. no Camera permission just means no incident photos, nothing else is affected. Table of every permission and its exact purpose in the Privacy Policy (§4).

No. The only thing exchanged between two paired phones is a short-range Bluetooth signal confirming proximity — no GPS location, contacts, or other app data ever crosses between the two devices. Each phone does record its own GPS route locally (if a standing pairing is active), but that route is never sent to the other phone or anywhere else.

Not silently. Turning off Guardian broadcasting, removing a pairing, or revoking access for everyone all require confirming it's you via your phone's own lock screen (fingerprint, face, PIN, or pattern) first. The app never sees that biometric data itself — it only gets a yes/no answer back from Android.

Check-in periodically asks "still OK?" on a timer you set, with no route or motion tracking at all. Gym is the same — no route or motion tracking — but self-confirmed: you tap "I'm OK" yourself any time, on a rolling 15-minute window, meant for workouts where your phone sits on a bench rather than on you. Guardian pairs your phone with someone else's so each of you can tell the other is nearby, alerting if contact is lost — unlike the other two, it does record your own GPS route locally while paired (to mark roughly where contact was last confirmed if it's lost), it just never shares that route with your paired partner. The regular activity types (Bike, Run, Car, etc.) track a full route the same way, visible to you in your own session history.

Yes — Run, Walk, Car, and Motorcycle sessions can all run GPS-free. For Run/Walk, distance and pace switch to your phone's step counter (or a paired Bluetooth treadmill's own readings, if you have one, which is more accurate). Car and Motorcycle have no step-counter or treadmill equivalent, so a GPS-free session there just tracks duration, with no distance or pace. Crash/fall detection itself still runs in every GPS-free mode, just from motion sensors alone.

A Tracked phone can be paired with more than one Guardian at once, each tracked independently, and a Guardian can watch more than one paired person by switching between them. True simultaneous tracking of several people within a single session isn't supported yet.

Every session can be exported as a GPX file (or FIT, for a GPS-free session) via your device's share sheet, to any app you choose — Strava, Garmin Connect, whatever. If you connect a Strava account in Settings, you can also upload directly, one session at a time or automatically. Connecting Strava is entirely optional and off by default.

Continuous GPS and motion-sensor tracking during a session does use meaningfully more battery than the phone idling — expected for any GPS tracking app. The app will ask to be exempted from your phone's battery optimization, which it needs for reliable detection while the screen is off; without that exemption, some phone manufacturers' aggressive battery managers can suspend the app mid-session.

No. Detection depends on your specific phone's sensor hardware, the manufacturer's own background-process restrictions (some are much more aggressive than stock Android, even with every permission granted), GPS/network availability, and more — all outside the app's control. See the Terms of Service for the full picture, and don't rely on this app as your only means of getting help in an emergency.

Most Bluetooth sensors — including heart rate straps and bike radars — only support one active Bluetooth connection at a time. The usual cause is a bike computer or GPS watch already holding a Bluetooth connection to the same sensor, sometimes alongside its own separate ANT+ connection — ANT+ and Bluetooth don't conflict with each other, so a sensor connected via ANT+ elsewhere can still connect to this app over Bluetooth at the same time. What blocks it is a second Bluetooth connection. Turn off the sensor's Bluetooth pairing on the other device (its ANT+ connection, if any, can stay on), then start your session — the app connects automatically once the Bluetooth slot is free. This can happen with any sensor shared between two devices, not just with this app.

The Sensors tab in Settings and an active session each open their own separate connection to the radar. Leaving Settings open on the radar entry while riding can compete with your session's own connection, so the session screen's bar can drop even though Settings still says "connected". Just don't linger on the Sensors tab once your ride has started, and it won't happen.

No — most affordable BLE bike radars only support one connected phone at a time; a second phone trying to pair just fights the first one for the connection. This is exactly why group radar sharing exists: pair the radar with one phone, and everyone riding together can see the same data over Bluetooth without each needing their own radar unit. This feature is currently experimental — reception on the other phones can be unstable, with occasional gaps or brief stale readings, while we keep improving it.

Make sure the sensor is powered on and close to your phone — most Bluetooth sensors only advertise for a limited time after waking up. Also check it isn't already connected to another device (see the first question above) — a sensor already paired elsewhere often won't show up in a scan at all. If a scan seems stuck, turning your phone's Bluetooth off and back on usually clears it.

A GPS-free Run or Walk session needs either the Activity Recognition permission (so the app can use your phone's step counter) or a paired Bluetooth treadmill to estimate distance and pace — without one of those, the app still tracks duration and detects a possible fall, just with no distance/pace numbers. GPS-free Car and Motorcycle sessions never show distance or pace, by design — driving has no step-counter or treadmill equivalent.