Fleet Hub map privacy and use
Updated October 4, 2026. These notices describe Fleet Hub’s mapping and route-research features.
Map privacy
Fleet Hub’s protected REI ARMOR research is limited to users with REI ARMOR permission. Opening the Google map sends requests from your browser to Google. Google receives your browser’s network information and the map area you view, and may process other information described in its Privacy Policy.
An explicit route comparison sends the reviewed pickup and destination coordinates from Fleet Hub’s server to Google Routes. Fleet Hub does not include driver names, bus numbers, booking identifiers, Coach Manager reports, or the REI observation series in that Routes request. No automatic whole-week Routes requests are enabled.
Original REI observations and Fleet Hub’s own research reports are retained in private Cloudflare storage. Google route geometry and comparison results are held temporarily in the signed-in page’s memory and are not archived in that history. Changing the selected run, clearing the comparison, or signing out clears that displayed comparison. The server retains opaque request hashes, random request claims and timestamps to enforce the pilot request allowance; it does not store Google route geometry or the key in those records.
Cloudflare processes Fleet Hub requests and enforces authenticated access. Google’s server key remains an encrypted server secret and is not supplied to the browser. The separately restricted Google Maps browser key is used only to load the interactive map. Ask your Fleet Hub administrator about access to, correction of, or retention of fleet records.
Map feature terms of use
Google Maps features are subject to the Google Maps/Google Earth Additional Terms of Service and Google Terms of Service. Google’s Privacy Policy explains Google’s processing of information.
Use these features only for authorized fleet research. Do not remove Google attribution, extract or redistribute Google map content, or use the research display as turn-by-turn navigation. Candidate routes are hypotheses, not verified records of the route a vehicle took. A driving route is not a certification that a road is suitable for a particular bus.
The pilot’s Google durations are current traffic-unaware references, not past traffic measurements. Raw observations, estimated route matches, and planned Coach Manager assignments remain distinct evidence. These research results do not change driver scores.
Mapped road speed limits
Road geometry and mapped speed limits are © OpenStreetMap contributors, available under the Open Database License (ODbL) 1.0. Download the complete Oʻahu road extract used by this release (JSON). Its metadata includes the source date. This extract was selected and compacted from the public Overpass API; no Google map content or fleet GPS is included.
The browser loads public, versioned road-area files from Fleet Hub on Cloudflare and compares them with the saved vehicle coordinates locally. No vehicle observation series is sent to OpenStreetMap, Overpass or GraphHopper. Normal Cloudflare request logs may include which road-area file was requested. This layer does not make paid speed-limit or routing API calls.
Mapped limits are informational, not sign-verified, historical proof, navigation instructions or driver-scoring evidence. Unknown roads, ambiguous matches, conditional limits and missing GPS remain unknown. A current map extract may not describe the limit on the date of an older trip. Road signs and applicable restrictions take precedence.
Users with REI ARMOR write permission may maintain separate, dated corrections with a source note. Corrections apply to the selected OSM road section and direction across vehicles; they do not rewrite GPS or telemetry. Corrections and their revision history are retained in protected Cloudflare storage and are separate from the public download. Changing the mapped road geometry requires re-review of any previous correction.