Data we collect
Merchant, driver, and delivery records may include names, phone numbers, addresses, drop-off pins, delivery notes, permit metadata, proof records, COD values, and admin activity.
Pilot privacy policy
Privacy policy.
This page records the TriniDrop MVP privacy posture for pilot data and operations.
How we use it
Data is used to approve pilot accounts, dispatch parcels, verify proof of delivery, reconcile COD, prepare finance statements, and support operational disputes.
Sharing limits
Customer tracking links expose only delivery context needed for that delivery. Pilot staff, assigned drivers, and approved merchants see only the records required for their role.
Retention
Delivery, COD, finance, and audit records are retained during the pilot so the owner can investigate disputes, pay drivers, invoice merchants, and validate the operating model.
Security
Admin pages require authentication, mobile API calls are role scoped, proof files use object storage, and production secrets must be managed outside source control.
Contact
Pilot users should contact the TriniDrop owner directly to correct account, address, driver, delivery, or COD information captured during operations.
Access control
Merchants see their own deliveries, drivers see assigned or available jobs according to dispatch rules, customers see only token-scoped tracking details, and admin users handle operations.
Production handling
Production deployments must use explicit secrets, TLS, object storage, backup procedures, and role-based access controls before real pilot users are onboarded.