Terms of Service

Last updated: August 21, 2026

1. Acceptance of these terms

By downloading, installing, or using Incident Detection (the "app"), you agree to these Terms of Service. If you do not agree, do not use the app. These terms apply alongside the Privacy Policy, which governs how the app handles data.

2. What the app does

Incident Detection is an Android app that:

• Tracks an activity you choose (cycling, motorcycle riding, running, walking, hiking, driving, or a water activity) and attempts to detect a possible crash or fall from your phone's accelerometer, gyroscope, GPS, and — if you pair one — a heart-rate sensor or bike radar (currently only the iGPSport SR Mini).
• Offers Check-in mode (periodic "are you OK?" prompts) and Gym mode (a self-confirmed timer) as alternatives that don't track a route or motion.
• Offers Guardian mode, letting two app users pair phones over Bluetooth so one can tell whether the other is nearby, with an alert if contact is lost. A separate, opt-in remote location beacon extends this over the internet — via a developer-operated relay and Google/Firebase Cloud Messaging — for when the two phones are out of Bluetooth range.
• If a possible crash, an unanswered check-in/self-check, a lost Guardian pairing, or an unresolved close pass from a paired bike radar is detected, attempts to send a text message (and, if you enable it, a phone call and/or photos) to emergency contacts you configure.
• Optionally exports or uploads session data (GPX/FIT files, or directly to Strava if you connect an account).

Full detail on what data this involves is in the Privacy Policy.

3. Not a safety device — no guarantee of detection

The app's crash- and incident-detection features are best-effort software running on consumer hardware, not a certified safety or medical device, and they do not guarantee that a crash, fall, or other emergency will be detected. Detection depends on sensor readings, GPS availability, phone placement, battery state, network/carrier conditions, and the operating system's own scheduling of background work — any of which can prevent detection or delay/prevent an alert from being sent, entirely outside the app's control. A crash or emergency can occur without being detected. Do not rely on this app as your only means of getting help in an emergency.

In particular, and without limiting the above, reliable detection is not guaranteed because the developer has no control over your specific device, including:

• Sensor hardware and quality, which varies between phone manufacturers and models — accelerometer/gyroscope precision, sampling rate, and noise characteristics differ from device to device, and detection thresholds tuned for one phone may behave differently on another.
• The device manufacturer's own software restrictions, such as OEM battery managers (some manufacturers are known to be particularly aggressive about this) that can throttle, suspend, or kill the app's background process independently of standard Android behavior, even when you have granted every permission the app requests and enabled the battery-optimization exemption the app offers. The app can request these exemptions but cannot force the manufacturer's software to honor them.
• Operating system version and configuration differences across devices, which can change how and when background work, notifications, or sensor access are permitted.

Reliable delivery of an alert once triggered is equally not guaranteed, because the app has no backend or server-side infrastructure of its own to assist with alerting — every alert depends entirely on your phone's own connection to its mobile carrier at that moment, with no fallback delivery path if that connection isn't available. In particular:

• Local carrier or regulatory restrictions on SMS/MMS, which vary by country and carrier and can block, delay, or filter messages the app sends, entirely outside the app's or the developer's control.
• Roaming, which can restrict or change how SMS, MMS, calls, and data/internet access behave, including cases where a roaming connection doesn't support one or more of these channels at all.
• Partial or total lack of cellular signal — including areas with weak or no coverage (rural areas, mountains, forests, indoors, tunnels, or simply between cell towers) — which is, above all, the single most likely reason an alert could fail to send at all, since the app has no way to deliver SMS, MMS, or a phone call without at least some carrier signal, and no alternative channel (e.g. satellite or Wi-Fi-based messaging) to fall back on.

If you turn on the remote location beacon (an optional tier of Guardian mode, see the Privacy Policy §9a), a Guardian's receipt of your location while you're out of Bluetooth range depends additionally on your device's internet connectivity, the availability of the developer's relay server, and Google/Firebase Cloud Messaging as the push-delivery transport — none of which are guaranteed either. This is a separate mechanism from the emergency-contact alert described above.

If you pair a compatible Bluetooth bike radar (currently only the iGPSport SR Mini) and turn on radar alerts, the same lack of guarantee applies to its close-pass detection as to crash detection above: the radar's communication protocol was reverse-engineered rather than built against an official specification, is not an officially supported iGPSport integration, and has only been field-tested against the SR Mini — readings can be inaccurate, drop out, or fail to trigger an alert for a real close pass.

4. Not a substitute for calling emergency services yourself

This app is not a substitute for contacting emergency services (e.g. calling 112/911/999) directly whenever you are able to do so. Its emergency-contact notification is a supplementary channel to the people you personally choose — it does not contact police, ambulance, fire services, or any emergency dispatch service on your behalf, and your emergency contacts are under no obligation to respond and are not guaranteed to be reachable, awake, or in a position to help. If you are conscious and able, always call emergency services yourself first.

5. Use at your own risk

You use the app, and engage in the physical activities it tracks (cycling, running, driving, and so on), entirely at your own risk. The app does not make any activity safer by itself — it is, at most, a supplementary notification tool for after something has already gone wrong. You remain solely responsible for your own safety, judgment, and compliance with any applicable laws (e.g. traffic laws, phone-use-while-driving restrictions) while using the app.

6. "As is" — no warranty

The app is provided "as is" and "as available," without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, accuracy, reliability, or non-infringement. The developer does not warrant that the app will be uninterrupted, error-free, secure, or free of defects, that detection will be accurate or timely, that alerts will successfully reach emergency contacts, or that third-party services the app depends on (mobile carrier SMS/MMS/call delivery, GPS/location services, Google Maps, Bluetooth sensor connections, Strava's API, the developer's own remote-beacon relay, or Google/Firebase Cloud Messaging) will be available or function correctly at any given moment.

7. Limitation of liability

To the maximum extent permitted by applicable law, the developer (Jan Komadowski / LoSoft) is not liable for any direct, indirect, incidental, special, consequential, or punitive damages — including but not limited to personal injury, death, property damage, or loss of data — arising from or related to your use of, or inability to use, the app, including a failure to detect an incident or a failure of any notification channel (SMS, call, MMS, or Guardian alert) to reach an emergency contact in time or at all.

8. Your responsibilities

Using the app's safety features effectively depends on you to:

• Keep emergency contact information accurate and up to date.
• Keep the app installed, its required permissions granted, and background/battery-optimization exemptions in place, since the app cannot detect or alert if the OS has been allowed to suspend it.
• Understand that GPS-free modes (Check-in, Gym, or GPS-free Walk/Car sessions) intentionally trade off continuous location tracking, which changes what the app can detect and how.
• Test the app's behavior yourself (e.g. the debug "Simulate crash" flow) and understand its limitations before relying on it in a real activity.

9. Third-party services

The app depends on services the developer does not control and is not responsible for: your mobile carrier (SMS/MMS/call delivery), Google Maps Platform, GPS/location providers, Bluetooth sensor manufacturers' hardware, and — only if you connect an account — Strava, Inc. Each is subject to its own terms, and their availability, accuracy, or interruption is outside the developer's control.

If you turn on the remote location beacon, delivery of a location update to your Guardian additionally depends on a relay server the developer operates and on Google/Firebase Cloud Messaging as the push-delivery transport. The relay is provided on a best-effort basis with no uptime guarantee, and Firebase Cloud Messaging is itself a third-party service outside the developer's control, subject to its own terms.

10. Changes to the app and these terms

Features may be added, changed, or removed over time. These terms may be updated to reflect that, published on this page with an updated "last updated" date above; continued use of the app after an update constitutes acceptance of the revised terms.

11. Termination

You may stop using the app at any time by uninstalling it, which removes its data from your device as described in the Privacy Policy. The developer may discontinue the app or any of its features at any time.

12. Governing law

These terms are governed by the laws applicable to the developer's place of business, without regard to conflict-of-law principles. This section is being finalized following legal review.

13. Contact

For questions about these terms: support@incident-detection.com