micronav

Privacy policy

Last updated 10 November 2026.

Driver app

While a trip is running, the micronav Fleet app records the phone's location about once a second, plus motion-sensor samples when precise tracking is enabled and fuel entries the driver types in. It records only between Start and Stop, shows a notification the whole time, and sends trips to the fleet's micronav server. Location is used only to show trips, distance, driving events and fuel efficiency to the driver's fleet operator.

Driver sign-in

An operator can create a driver login using an email address and password. Passwords are stored as salted hashes on the server and are not saved in the app. Session credentials are encrypted on the phone; operators can reset or revoke driver access.

Dispatch

Fleet shows pickup and drop-off addresses, customer phone numbers and instructions assigned by your operator. Customer details are available to the operator and assigned driver. Tapping Call opens the phone dialer; it does not place a call automatically. Opening a stop in Google Maps or a browser shares that stop with the selected provider. Job status updates are sent to the server, and your last job list is kept on the phone so it remains readable offline.

Maps app

Maps uses location to show your position and generate directions. Search text, route endpoints and API requests are sent to the Micronav server. Routing outside the local region may use an external routing service, which receives the route endpoints. Submitted online searches may use Photon’s public service, which receives the search text and a rounded location bias when supplied. Local autocomplete does not call that provider. Results are cached on the Micronav server. Motion and direction sensors help orient the map on the device.

Demo requests

The website stores the name, contact details, company, interest and message you submit so we can respond. The server records an IP address to limit spam. Contact us to request deletion.

Hosting

The current pilot is hosted on an AWS server in Sydney, Australia. Fleet operators should explain this deployment and its access arrangements to participating drivers.

Who sees the data

The fleet operator who invited the driver, and micronav to run the service. We do not sell data or use it for advertising.

Storage and deletion

Data is stored on our servers and kept while the fleet's account is active. Drivers and operators can ask for deletion at any time by email.

Map API

Trips sent to the reconstruction API are processed and not stored. We keep a count of calls per API key.

Contact

daanish1sharma@gmail.com