Skip to content
Data & Security

Your fleet. Your data. Stated plainly.

Dispatch runs on sensitive data: where your riders are and where your customers live. Here is exactly what is used, why, and how it is protected.

What is used

Four kinds of data, each with one job.

Order data

Pickup and drop locations, promised delivery window, order size and status. Used to assign the order and calculate its ETA.

Rider location

Live position during active shifts only. Used for assignment, ETA prediction and rerouting, and nothing else.

Rider status

Availability, current load and shift. Used to decide who can take the next order without hurting other ETAs.

Road conditions

Traffic and obstruction signals on the routes in use. Used to predict and correct arrival times.

How decisions are derived

Every assignment and ETA can be explained.

Aschhigo does not make opaque calls. Each assignment records the riders considered and why one was chosen. Each ETA change and reroute records the condition that caused it.

Decision record
DecisionRider R-07 assigned
ConsideredR-03, R-07, R-09, R-12
Deciding factorsCapacity available, drop on current route
ETA basisLive traffic, remaining distance, one stacked drop
Later changeRerouted: closure on planned road

Data ownership

Your fleet and delivery data stays yours. Orders, rider history, ETA records and reports can be exported at any time in CSV, and through the API. We do not sell it, and we do not use it to serve any other business.

Rider location, used for one purpose

Rider location data is used only for dispatch and ETA purposes: assigning orders, predicting arrival and rerouting. It is collected during active shifts, and access is restricted by role.

Practices

How the platform is protected.

Encryption in transit and at rest

Traffic between apps, integrations and the platform uses TLS. Stored order and location data is encrypted at rest.

Role-based access

Access is granted by role and hub. A hub manager sees their hub; rider location is visible only to roles that dispatch.

Audit trail

Assignments, overrides, reroutes and access to rider data are logged with who, what and when.

Least-privilege internally

Our own staff access customer data only to deliver support you request, and that access is logged.

Next on the board

Your fleet is the next dispatch.

Connect your riders and order feed, and every delivery promise you make starts correcting itself the moment the road changes.

OrderStatusETA
Grocery basket, Sector 4On time06 min
Pharmacy refill, Link RoadRerouted18 min
Parcel batch of 3, Hub EastAssigned24 min
Your fleetReady to dispatch