Privacy and security settings

Where your data is stored

Fleet data is stored on your devices, in your own iCloud (on Apple devices), and on the host device you choose to pair with, and it never passes through our servers. The Android version doesn’t use iCloud; data is stored on the device. The app contains no ads and no third-party analytics or tracking SDKs. For details, see the FleetDispatch Privacy Policy.

App Lock

After you turn on App Lock in Settings, you need to verify your identity when you return to the app: Apple devices use Face ID, Touch ID, Optic ID, or the device passcode, and Android uses your fingerprint, face unlock, or screen lock. In Appearance & Layout, you can set how long you can be away before you need to verify again (immediately, 1 minute, 5 minutes, or 15 minutes). While App Lock is on, the screen content is hidden in the App Switcher (the Recents screen on Android).

Route recording (optional)

• The app records location only when you turn on Record this trip’s route at dispatch, and only during the trip (including in the background). Recording stops automatically when you return. The first time you turn it on, the app explains what it’s for and asks for your consent. Later dispatches keep this choice, and you can turn it off in Location Reporting under Settings.
• iPhone and iPad: When the system asks for location permission, we recommend choosing Always Allow, so recording can resume automatically even if the system closes the app.
• Android: While a route is being recorded, the notification bar keeps showing Recording Route. The app records the route with a foreground service and doesn’t ask for background location permission.
• Route data is used for route playback and driving behavior scoring and is stored with that trip’s record. It’s deleted when you delete the trip record.
• On clients in multi-user setups, the real-time location during the trip is also sent to the host you paired with, to help with dispatching.
• Mac doesn’t record routes.

System permissions

You can turn off permissions such as location, Bluetooth, and notifications at any time in your device’s Settings. On Android, the app uses these permissions:

Permission	What it’s used for
Location	Recording routes during trips
Nearby devices	Connecting to an OBD-II Bluetooth adapter (Android 12 and later)
Notifications	Reminders for due dates, maintenance, and approvals, plus the ongoing trip notification (must be allowed on Android 13 and later)

External services the app connects to

The app connects to the following services only when needed, and nothing it sends includes your fleet data:

• Maps (OpenFreeMap): When you open a screen with a map (such as trip routes, route playback, or live locations), the app downloads OpenStreetMap map tiles from OpenFreeMap (tiles.openfreemap.org).
• Help Center (instw.org): The app gets help articles from the public docs API on the INSTW official website. When you search in the Help Center, the search terms you enter are sent. When you’re offline, the app uses its built-in offline copy.
• Version check: Apple devices check the App Store for the latest version; Android checks the public API on instw.org.
• Navigation: When you choose to navigate, the destination is handed to the maps app you choose.

For details, see the FleetDispatch Privacy Policy.

Security in multi-user setups

• Data is encrypted with TLS over the local network, and both sides compare a security code when pairing.
• Role-based permissions: admins, drivers, and viewers each have different permissions, and the host checks every change against the role (see Multi-user sync).