Incident Detection
Privacy Policy — ID Tools
Last updated: October 4, 2026
1. Data controller
Jan Komadowski (LoSoft). Contact: support@incident-detection.com.
2. What data the app processes
ID Tools is a standalone Android app for navigation, compass, GNSS, and map-based trip tools, route planning, and a Location simulator for developers and testers. It does not require an account and it does not use a developer-operated backend for core features. Most data stays on the device.
The app may process:
| Data category | Specifics | Involves a third party |
|---|---|---|
| Location data | Current GPS position, route waypoints, route start point, navigation target, distance and bearing calculations, Plus Codes, and coordinates entered by the user | No — processed for the user's own use |
| Compass / motion data | Heading, orientation, and sensor accuracy used by the compass and navigation screens | No — processed on device |
| GNSS data | Fix quality, satellite information, altitude, and related satellite-view details shown in the GNSS screen | No — processed on device |
| Saved routes | Route names, waypoint lists, route metadata, timestamps, and navigation state stored for later reuse | No — stored locally on the device |
| Settings and preferences | Units, UI preferences, and other app settings | No — stored locally on the device |
| Map tile requests | When a map is shown, the app requests map tiles and map styles from the selected map provider, which sees the device's IP address and the area being viewed | Yes — the selected map provider (see section 4) |
| Location simulator | A GPX track the user imports or plans is replayed as mock location, which requires the user to choose this app as the mock location app in Developer options. While it runs, a foreground service keeps it going and an optional floating control panel can be shown over other apps (the user grants "Display over other apps" in Android settings). Simulator options are remembered locally | No — processed on device; the track is not uploaded |
| Road data lookups (optional, off by default) | If the user turns on OpenStreetMap data in the Location simulator, the outline of the imported GPX track (simplified to a few hundred coordinates) and one coordinate from the middle of the track (to find which country it is in) are sent to the Overpass API to find traffic lights, stop signs, crossings, roundabouts, road classes and speed limits along it. The result is kept on the device with the imported file | Yes — the Overpass API, a public OpenStreetMap service |
| Route planning (optional) | When the user taps "Calculate route" in the route planner, the start and destination coordinates (the start can be the device's current location), any stops, and the chosen way of travelling are sent to the public Valhalla routing service. The route found is returned and can be sent to Incident Detection as a GPX file | Yes — the Valhalla routing service run for OpenStreetMap (FOSSGIS) |
| Share / copy content | Coordinates, Plus Codes, or location text copied to the clipboard or shared through Android's share sheet | Yes — only the app or service the user explicitly chooses |
3. How the app uses data
ID Tools uses the data above to:
- render compass, GNSS, map, and navigation screens,
- calculate bearings, distances, and route progress,
- save and restore routes and app preferences,
- let the user copy or share location information,
- replay a GPX track as mock location in the Location simulator, on the device only,
- plan routes and, optionally, look up road data along an imported track,
- fetch and display map tiles when map view is used.
The app does not use this data for advertising, profiling, or selling to data brokers.
4. Third parties and transfers
The app's core data is stored locally on the device.
External services are used only when needed for app functionality:
- The map provider selected in Settings is contacted to load map tiles and styles: OpenFreeMap (tiles.openfreemap.org), MapTiler (api.maptiler.com, with the app's API key), MapToolKit (styles.maptoolkit.org), or the OpenStreetMap and CyclOSM tile servers (tile.openstreetmap.org, tile-cyclosm.openstreetmap.fr). Each provider receives the device's IP address and the tiles requested, and handles them under its own policy.
- If the user turns on OpenStreetMap data in the Location simulator, the Overpass API (a public OpenStreetMap service, e.g. overpass-api.de) receives the outline of the imported track, one coordinate from the middle of the track (to find the country, so that legal default speed limits can be assumed where a road has none tagged), and the app's identification (name, version and support address) in order to answer. This is off by default and happens only for that file, once; the result is kept on the device. Map data comes from OpenStreetMap contributors under the ODbL licence.
- If the user plans a route, the Valhalla routing service (e.g. valhalla1.openstreetmap.de) receives the start and destination coordinates, any stops, the way of travelling, and the app's identification (name, version and support address) in order to answer. This happens only when the user taps "Calculate route". A route sent to Incident Detection stays on the device; it is handed over as a GPX file to that app only.
- Google Play services location may process location information on supported Android devices to provide GPS and GNSS-related functionality.
- If the user copies or shares text, the data is sent only to the app or service the user explicitly selects.
The app does not send data to a developer-operated backend.
5. Data retention
Data stored locally in the app remains on the device until the user deletes it, clears app storage, or uninstalls the app.
Map tiles may also be cached locally by the app or platform for performance.
Data handled by external services is retained according to those services' own policies.
6. Your choices
You can:
- deny location permission, which limits compass and navigation features,
- clear saved routes and app data from within the app or from Android settings,
- uninstall the app to remove local data,
- choose whether to share or copy location text,
- leave OpenStreetMap data in the Location simulator off, so that nothing is sent to Overpass,
- decline "Display over other apps" or the mock location app setting, which only turns off the Location simulator's panel or the simulator itself.
7. Changes to this policy
This policy may change as ID Tools gains new features or external integrations. The published version should be updated whenever the app's data handling changes.
8. Contact
For privacy-related inquiries: support@incident-detection.com