Language versions Versions in other languages are translations provided for reference only; in case of any discrepancy, the Traditional Chinese version prevails. Read the Traditional Chinese version

Last updated: October 31, 2026

This policy explains how the FleetDispatch app (iPhone, iPad, Mac, Apple Watch, and Android phones and tablets; the “App”) and the FleetDispatch product page on the official INSTW website (instw.org/fleetdispatch; the “Website”) handle your data. We (YucDu; “we” or “us”) do not operate any servers to store your fleet data; App data exists only on your devices, in your own iCloud (Apple devices), and on the host devices within your fleet that you choose to pair with.

1. Data in the App​

1.1 Where data is stored​

• Your devices: Data such as vehicles, drivers, trip records, fuel and expenses, maintenance, inspections, work orders, parts and vehicle requests is stored in a database on your device.
• Your iCloud (automatic sync): If your device is signed in to iCloud, the data above is automatically synced through Apple’s CloudKit to the private database of your Apple ID for use on your other devices. We cannot access your iCloud data. If you do not want it synced, turn off iCloud access for this App in Settings › Apple Account › iCloud on your device.
• Automatic iCloud backups: The App keeps the 7 most recent encrypted backups in your iCloud Drive (in space dedicated to this App); the encryption key is stored in your iCloud Keychain. You can also export password-encrypted backup files yourself.
• Apple Watch (version 8.0 and later): Data shown on your watch is sent directly from your paired iPhone; Apple Watch does not connect to iCloud on its own. Dispatches, returns, and approvals you make on the watch are carried out by the iPhone.

1.2 Multi-user edition (local network sync)​

• When the multi-user edition is enabled, data is synced directly between the host you pair with (iPad, Mac, or Android tablet) and client devices over the same local network, encrypted with TLS, without passing through our servers.
• Admins on the host can view and manage fleet data and the list of paired devices (device name, role and last connection time). Pairing information and connection credentials are stored in each device’s Keychain (on Android, the system keystore).

1.3 Location data (optional)​

• Only after you explicitly turn on “Route recording” in the App will the App record GPS location while a vehicle is out (including in the background), for route playback and driving behavior scoring; recording stops automatically when the vehicle is returned.
• Route data is stored together with the corresponding trip record on your device and in iCloud; on client devices in the multi-user edition, the real-time location during the trip is also sent to the host you paired with, for dispatching purposes.
• When you delete a trip record, that trip’s route data is deleted along with it. You can turn this off at any time in the App’s settings.
• On Android, an ongoing notification shows the trip in progress while recording. Android location services may be provided by Google Play services on your device and are handled according to your device settings and Google’s policies.

1.4 OBD-II vehicle diagnostics (optional)​

• When enabled, the App connects via Bluetooth to the OBD-II diagnostic adapter you choose and reads the vehicle identification number (VIN), speed, mileage, fuel level and trouble codes, which are used to identify the vehicle, fill in mileage and create inspection records. This data exists only on your device (and, on Apple devices, in your iCloud) and is not sent to us.

1.5 External services the App connects to​

• The App checks for the latest version number to notify you of updates: Apple devices query Apple’s App Store (sending only the App’s bundle identifier), and Android devices query the public API of the official INSTW website, instw.org (sending only the product and platform names).
• Maps (OpenFreeMap; version 8.0 and later): When you open a screen with a map (for example, a trip route or live locations), the App downloads map tiles from OpenFreeMap (tiles.openfreemap.org). The request contains the tile coordinates of the map area being shown and technical information that every connection carries, such as your IP address; it does not contain your fleet data. According to OpenFreeMap, its access logs do not contain IP addresses, and error logs may contain IP addresses and are deleted within 7 days; the service is delivered through Cloudflare’s content delivery network. Map data © OpenMapTiles © OpenStreetMap contributors.
• Help Center (instw.org; version 8.0 and later): The App’s Help Center retrieves help articles, the table of contents, and release information from the public documentation API of the official INSTW website (instw.org). Requests contain the language and article identifiers, and the search terms you enter in the Help Center, but not your fleet data. See the INSTW Website Privacy Policy for how they are handled. When you are offline, the App uses its built-in offline copy.
• Navigation: When you choose to navigate, the App passes the destination to the maps app you choose, and that app’s privacy policy applies from then on.
• The App may ask you to rate it through the system rating feature provided by Apple or Google; ratings are handled under that company’s policies.
• The App contains no ads and no third-party analytics or tracking SDKs.

1.6 Android version​

• Where data is stored: Data is stored in a database on the device. The Android version does not use iCloud.
• System backup: If you turn on Android backup on your device, App data may be backed up to your Google Account through Android’s backup service and is handled under Google’s policies.
• Backup files: You can export password-encrypted backup files, save them wherever you choose, and restore them on another Android device or on iPhone, iPad, or Mac.
• Notifications and widgets: Reminders, the ongoing trip notification, and home screen widgets are created on the device and do not go through a push server.

2. Data on the Website​

• The Website is part of the official INSTW website. It has no forms, accounts or comment features, does not use tracking cookies, and has no third-party analytics tools. For details on how the Website handles data, see the INSTW Website Privacy Policy.
• The former official website, fleetdispatch.instw.org, provided an issue report form. The website was shut down on October 30, 2026, and the data received through the form has been deleted from our online systems. We keep one offline backup that is used only to respond to your requests for access, correction, or deletion; if you submitted data through that form, you may email us.

3. What we do not do​

• We do not sell or rent your personal data.
• We do not use your data to serve ads or to build cross-app tracking profiles.
• We do not request permissions beyond what features require; permissions such as location, Bluetooth and notifications can be turned off at any time in your device settings.

4. Retention period and your rights​

• App data is managed by you: you can remove it by deleting the data in the App, or by deleting the App and deleting this App’s data in your iCloud settings. On Android, uninstalling the App deletes its data on the device (except backup files you saved elsewhere and Android system backups).
• For the retention periods of Website-related data, see the INSTW Website Privacy Policy. Issue report data from the former website was deleted from our online systems on October 30, 2026; the offline backup is deleted once your request has been handled and it is no longer needed. You may email us to request access to, correction of, or deletion of the data you provided.

5. Policy updates​

If this policy changes materially, we will update it on the Website and indicate the date of the update.

6. Contact us​

If you have any questions about this policy or your data, please email fleetdispatch@instw.org.