Security & privacy

This page describes what the product supports today: role-based access across organizations and routes, and what data is stored to enable delivery operations and proof of delivery.

Role-based access
  • Organization roles: admin / driver / viewer.
  • Route roles: admin / viewer.
  • Platform admin roles: stored on users (e.g. “admin”) to access the `/admin` area.
Data stored
  • Routes and route destinations (lat/lng, settings, directions metadata).
  • Organization destinations (address book contacts and locations).
  • Zones as polygon geometry + driver-zone assignments.
  • Rides (state and timestamps) and stop-level completion history.
  • Signature proof for signature-required destinations (stored as PNG bytes).
  • Ride track points (lat/lng samples recorded during rides).
Operational integrity
  • Stop-level timestamps and notes for auditability.
  • Idempotent external billing transaction/event tracking (where applicable).
  • Clear destination/ride state history for reliable reporting.
Have security questions?
We can walk through roles, stored data, and operational auditability for your workflow.
Contact usSee features