Role-based operational access
Portal access is separated by operational role, with protected product routes for fleet, driver, delivery partner and CourierBase Ops users.
Trust at CourierBase
Trust starts with clear controls and honest boundaries.
CourierBase handles operational records that affect people and payments. We explain how those records are used, who can act on them and where human review remains part of the process.
Pilot controls
Controls designed into the operating flow.
Human review for uncertain matches
Low-confidence identity results are presented for review rather than silently attached to a person or payment.
Auditable reconciliation events
Batches, exceptions and payment decisions are designed to leave a traceable operational history.
Protected payout details
Full bank payment instructions are encrypted at rest and hidden from routine product screens; drivers see only a masked account summary.
Data handling
Practical principles for sensitive operational records.
Our public commitments stay at the level we can maintain. Specific infrastructure, certification and legal claims are not used as marketing shortcuts.
Purpose-led collection
Collect the identity, roster, completed-work and payment information needed to run the agreed courier operation — not marketing data for its own sake.
Need-based access
Separate product portals and operational roles so users see the information required for their work.
Traceable decisions
Design reconciliation changes and payment decisions to retain who acted, what changed and when.
Incident response
Assess security and privacy incidents promptly, preserve evidence and follow the applicable Notifiable Data Breaches process when required.
Privacy details belong in the policy, not in a badge.
Read how CourierBase describes personal information, service providers, retention, access and complaints.